Co-founded PLVI Studios and translated business needs into shipped digital products.
Prathamesh PatilProduct Designer · AI-native builder
PRODUCT DESIGNER, CODEX · INTERACTIVE PITCH
AN INTERACTIVE APPLICATION · PRODUCT DESIGNER, CODEX
I could tell you I’m an AI-native designer. I’d rather show you.
This is a role-specific product story built by Prathamesh Patil with Codex, grounded in real projects and designed to take about two minutes.
12 concise scenes4 working AI builds public-safe evidence
ready
WHAT YOU’LL SEE
Use ← → or space to navigate01 How I work with Codex
02 What I have designed and shipped
03 Why that maps to this role
01 · WHY THIS EXISTS
A résumé can tell you I work with Codex. This experience lets you see how.
I wanted the application itself to demonstrate the behavior I care about: turning context into a clear product story, making evidence inspectable, and using working software to communicate an idea.
Curated, not generated live. No private context or open-ended chatbot.
01 · SOURCEReal project evidenceDecisions, prototypes, failures, outcomes
scoped, not scraped
02 · PROCESSBuilt with CodexFrame, prototype, critique, debug
working software
03 · OUTPUTThe experience you are usingEvidence shaped into a product story
02 · WHO I AM
IT engineer turned product designer and AI-native builder.
For eight years, I have translated complex systems into products people can understand and use. Now I can also build the interaction far enough to learn from it.
ENGINEERINGUX + PRODUCTDESIGN LEADERSHIPAI BUILDER
8 years across productMaster’s from SCADMicrosoft · FINRA · Deloitte
01PRODUCT DESIGNERclarity · craft · systems
02TECHNICAL BUILDERprototype · code · debug
03AI NATIVEagents · trust · control
LIVE SYSTEM03 · WHY CODEX
Codex is changing who gets to build software. It is already changing how I design.
I use it to collapse the distance between an interaction idea and something people can actually experience, challenge, and improve.
THIS DECKdesigned and built with CodexDESKÉMONa physical companion for CodexDAILY WORKFLOWcontext, critique, code, recovery
ready
PAIRExplore and challenge
Turn ambiguity into testable product decisions.
BUILDMake the idea real
Move from interaction model to working software.
DECIDEKeep judgment human
Truth, scope, safety, and product quality stay owned.
04 · HOW I WORK WITH CODEX
Context is durable.
Judgment stays human.
My knowledge system carries verified project context into the build. Codex helps inspect, prototype, test, and debug. I own the product decisions and what becomes durable.
VERIFIED CONTEXT FLOW01 → 02 → 03 → DURABLE
01 · OWNED CONTEXTAlter Ego
Projects · decisions · evidence
VERIFIED SOURCES02 · WORKING ENVIRONMENTCodex
Inspect · build · test · debug
ACTIVE BUILD LOOP03 · PRODUCT JUDGMENTPrathamesh
Truth · boundaries · decisions
HUMAN CONTROL↳DURABLE OUTCOMESvalidated work returns to the system
scoped context
working output
reviewed + retained
Sanitized system view. No private context is exposed.
05 · THE FLAGSHIP BUILD
Deskémon gives the Codex pet a body, context, and a reason to ask first.
A phone becomes the physical face of the same companion at your desk. It notices a real-world commitment, checks digital context, and asks before taking action.
2:14● ● ●
listen
LISTENING
DESKÉMON · PHYSICAL COMPANION FOR CODEX“I’ll send the revised prototype by three.”
A meaningful commitment is detected.
06 · THE DESIGN PROBLEM BENEATH THE DEMO
For an agent, trust is not a disclaimer. It is the interaction model.
01
01Hear02Interpret03Check04Ask05Act
SYSTEM STATE
RATIONALE
HUMAN CONTROL
ACTIVE PRINCIPLEHearvisible · bounded · reversible
HOW THE AGENT EARNS TRUSTFive product moments from sensing to a reversible action · STEP 01 / 05
Hear
Capture one bounded moment without keeping an endless ambient recording.
07 · SELECTED BUILDS FOR CODEX
Four products.
Four signals for this role.
I selected these because together they show agentic interaction design, privacy, evaluation, human control, and the ability to turn an AI concept into working software.
ready
01 / 04 · Physical agent for Codex
Deskémon
Same companion. Same context. New senses.
Conversation becomes context; context becomes a proposal; action waits for permission.
multimodalagent stateshuman approval
08 · PROFESSIONAL RANGE
The builds are recent.
The judgment behind them is not.
My background spans engineering, product design, research, accessibility, design systems, team leadership, and client delivery.
75% faster research synthesis2× delivery efficiency25% higher completion11+ global clients
Built systems and led multidisciplinary delivery across enterprise products.
Microsoft, FINRA, Deloitte, AI research, accessibility, and strategic design.
Independent prototypes that join product craft with working code.
09 · WHY THIS MAPS TO CODEX
The role asks for a rare combination. That combination is my throughline.
Every requirement connects to evidence already shown in this experience.
ROLE SIGNAL PROJECT EVIDENCE
THE ROLE NEEDSTHE EVIDENCE I BRING
01Technical background + shipped code
IT engineering · Hukum · Deskémon · Synthesia
020→1 craft in ambiguity
Microsoft sprint · independent AI products
03AI-first interaction paradigms
Agent states · permissions · evaluation · recovery
04Research + systems thinking
SCAD Ask · FINRA · teacher-shaped Mind Gym
05Communication + design culture
Team leadership · executive narratives · this deck
10 · EXPLORE THE WORK
Choose the signal you want to inspect.
Seven recruiter questions. Seven concise, source-grounded answers. Curated from verified project material, not generated live.
PROJECT LENS 01 / 07
Designer × Builder × AI native
“Why is Prathamesh a strong fit for Codex?”
He designs the moment an AI system becomes understandable enough to trust, then builds far enough to test whether it actually works.
8 yrsproduct craft4working AI builds0→1default mode
Agentic UXTechnical prototypingEnterprise systems
ready
THANK YOU FOR THE TWO MINUTES
What would we build together?
I want to help make the magic of Codex understandable, trustworthy, and available to anyone with an idea, including people who do not already know how to build software.