Start here
Apply to AI-native product roles first
Job postings in AI engineering now describe two different jobs. The table compares them.
| AI-native product engineer | Staff AI platform engineer | |
|---|---|---|
| Typical employer | A company or studio that builds agents and workflow automation for clients. | An established software company that builds agent platforms and developer tools for its own engineers. |
| What they screen for | Things you built without being asked, a product that people use, heavy use of AI tools, and attention to the customer. | Many years of engineering experience, often 8 or more, including time as a technical lead. Deep skill in one backend language and one major cloud. Experience running agents in production. |
| How code gets written | Models write most or all of the code. You direct the agents and you own what you merge. | You get engineering teams to adopt coding agents and shared tool servers, and you build the agent platforms those teams use. |
| When you can apply | After Phase 3, around month 3 or 4, with a shipped AI product as your main evidence. | After Phase 11, around month 9 to 12, with visible leadership work. The tenure requirement still applies. |
Apply for the product roles early. A job on an AI-native team gives you production experience with agents faster than any side project, and the Staff role asks for exactly that experience.
Staff postings also ask for years of experience and for time spent leading teams. No curriculum can give you those. What the roadmap can do is make your leadership work visible: tools you got teams to adopt, standards you wrote, and incidents you ran. When you meet the tenure requirement, the rest of your case is already made.