Andrew Ambrosino, Product and Engineering Lead for the Codex app at OpenAI, shares profound insights into how AI is fundamentally reshaping product development and the nature of work itself. With Codex seeing exponential growth and nearly 100% internal adoption at OpenAI, Ambrosino's team is at the forefront of this transformation.
**The Inversion of Product Development**
Ambrosino argues that AI has "inverted" the traditional product development process. Historically, implementation was expensive, necessitating extensive research, ideation, and prototyping to de-risk before building. Now, with AI, implementation is cheap; "anybody can build anything" from scratch using powerful models. This leads to a proliferation of prototypes—Andrew jokes about "90 different uncoordinated teams" building variations of the same feature.
In this new paradigm, the challenge shifts from *building* to *curating*. The expensive part is no longer implementation, but "taste" – knowing what's good, what to combine, and how to frame and refine the myriad of explorations. Ambrosino clarifies that PRDs (Product Requirements Documents) are not dead; rather, the *medium* of communication must match the goal. A document might be best for clarifying a vague area, while a prototype serves to stress-test an interaction. The danger lies in mistaking a polished prototype for a production-ready feature, when it might still be an early exploration.
**The Nuance of "Taste" and AI's Design Challenge**
"Taste" for Ambrosino extends beyond aesthetics. It encompasses systems thinking, understanding how a feature fits into the broader product, and aligning with strategic goals. While AI models excel at code generation, they currently lag in design capabilities. This is partly because design is harder to grade (relying on human taste) and AI research initially prioritized areas that accelerate AI itself (like coding). More profoundly, AI struggles with design's need for novelty and its deep understanding of abstraction layers – how visual elements relate to underlying code structure. Humans remain crucial for creative leaps and understanding user psychology that drives truly impactful design.
**Evolving Roles and Team Structure**
OpenAI exhibits significant "role collapse," where designers write code, and product managers possess strong technical skills. Ambrosino sees more overlap, with roles defined by the *average* of one's work rather than strict boundaries. While welcoming the breakdown of "not your lane" mentalities, he cautions against eliminating roles entirely, as this risks discarding specialized knowledge and best practices that each discipline has cultivated. Product managers, for instance, now function in a "zone defense," curating chaos, guiding disparate efforts, and ensuring alignment across a highly "agentic" workforce. Hiring prioritizes "high agency, high taste" individuals capable of driving an idea from inception to completion.
**Product Strategy in an AI-First World**
Planning horizons have drastically shortened. Long-term plans must remain hazy because model capabilities evolve so rapidly that a precise 9-month plan would be "false precision." A key strategy is to build ambitious features that may not fully work *yet*, anticipating future model improvements. Ambrosino cites the example of an early Codex web version that failed due to insufficient model intelligence, while a later, identically shaped local version succeeded. The lesson: don't be stubborn; a feature might simply not be "ready yet" for the current model.
**Codex as Andrew's Personal Assistant and the Vision for the App**
Ambrosino actively uses Codex as his primary work tool, evolving his usage as his role shifts. Initially, it was a development tool for writing code. Now, it assists with product discovery, team coordination, and information synthesis, creating automated daily briefs from thousands of Slack channels and emails. He "coaches" the AI to refine these processes.
The vision for Codex (and its eventual combination with ChatGPT) is not a "super app" that replaces all others, but a "home base." It's a central hub where users start and end their work, automate tasks, and coordinate with specialized tools. Andrew shares a remarkable story of a videographer using Codex to edit videos, which then *built its own extension* for Adobe Premiere Pro to facilitate deeper interaction. This illustrates the goal: seamless interaction with existing tools, whether through direct integration, computer use, or custom extensions, making the AI a proactive partner across all knowledge work.
**Lessons from Failure**
Ambrosino candidly shares his past experiences as a startup founder, describing years of "constant failure" before reaching his current success. He emphasizes that resilience, continuous learning, and adapting one's process are crucial. OpenAI's culture of direct, often critical, internal feedback (like 2,000-message Slack threads calling an idea "stupid") is seen as a vital mechanism for refining products and accelerating progress.
Ultimately, the future of work, as seen from OpenAI, is one where human agency, taste, and the ability to adapt to ever-changing AI capabilities are paramount, fostering a dynamic environment where individuals drive product creation and automation across all domains.