Where the term comes up In Guillermo Rauch's conversation with Dan Shipper, product engineer appears as the name of an emerging role — one of the two titles Rauch predicts for the AI era, alongside design engineer. He introduces it at the end of a longer story about titles drifting away from keystrokes: The drift toward the product Rauch traces how the word coder has been fading for years — long before AI: formatting debates were erased by tools like Prettier, and roles evolved from coder toward developer, engineer, then product designer — each step moving away from implementation detail and toward the end goal. Product engineer is the next stop on that trajectory: an engineer defined not by writing code but by the product that ships. Why the role fits the AI era This connects to Rauch's broader claim that coding is becoming a specific, delegated skill — like mental math, a job machines tend to take over. As builders become full-stack product builders who use tools like v0 to handle design, data, and copywriting themselves, the value shifts to meta-skills: conceptual thinking, understanding symbolic systems, taste, and knowing what product to build. A product engineer is what that person is called. • Product engineer is an emerging role Rauch predicts for the AI era, alongside design engineer. • It caps a long drift: coder → developer → engineer → product designer — away from keystrokes, toward the end goal. • It matters because coding itself is becoming an AI-delegated, specific skill; durable value moves to product judgment, taste, and meta-skills.