# The Path — how to become a Forward Deployed Engineer You don't get hired for what you know. You get hired for systems that survived contact. This path takes you from strong engineer to deployed operator in six stages. It's not a course you pass; it's proof you build. ## The six stages **Stage 0 · Diagnose — Are you built for it?.** Find where you stand across production instinct, client nerve, deployment temperament and range. Returns your archetype and a personalized gap-map. **Stage 1 · Close gaps — The skills map.** The six pillars, and what “employable” looks like for each. Work your two weakest first. **Stage 2 · Build proof — Ship one real system.** An LLM doing real work, wired into a messy external system, in front of real users, with evals — kept alive 30 days. This artifact is your candidacy. **Stage 3 · Position — “I deploy AI in the real world.”.** A portfolio that leads with shipped systems, not certificates. A profile that reads like an operator, not a student. **Stage 4 · Interview — Test the intersection.** System design under real constraints, a client-facing case, eval-scoping, and three deployment war stories ready. **Stage 5 · Land it — Where the roles are.** Frontier labs, enterprises standing up their own teams, startups, and sovereign-AI programmes — from San Francisco and London to Bangalore and the Gulf. ## How long it takes, by starting point - **Senior full-stack engineer — 3–6 months.** You have the range and the production scars. What is missing is LLM depth in production and one deployment story you can defend. - **Backend or infra engineer — 6–9 months.** The systems instinct transfers directly. Budget the time for the client-facing half — that is the part that fails people, not the code. - **ML or research engineer — 6–12 months.** You know the models better than most FDEs. You will spend the time on shipping and on owning uptime, which research rarely demands. - **Two or three years in — 12–18 months.** The path works, but Stage 2 takes longer: one real deployed system is worth more than five side projects, and it takes a real user to make it real. ## Where candidates lose the year - **Collecting certificates.** No hiring desk has ever been moved by a course badge. One system in production, with its incident log, outranks any curriculum. - **Building demos, not deployments.** A notebook that works on clean data proves nothing. The signal is what happened when it met someone else's schema, someone else's auth, and a user who did not read the instructions. - **Skipping the client half.** Most candidates over-index on the technical pillars because they are the comfortable ones. The interview tests the intersection — and the room is where it breaks. - **Waiting to feel ready.** The role is defined by ambiguity. If you are waiting for the moment you feel qualified for it, you have misread what it is. ## Questions people actually ask ### How long does it take to become a Forward Deployed Engineer? Three to six months from a senior full-stack role, six to twelve from research or early-career engineering. The variable is rarely the learning — it is how long it takes to get one real system deployed in front of real users. ### Do I need to already work at a big tech company? No. What the desk looks for is evidence you have shipped something that survived contact with a real environment. A system you deployed for a small business can prove more than a ticket you closed inside a large one. ### Is the diagnostic just a lead magnet? It captures an email, and we are upfront about that. It also returns your archetype across four axes and the two you should work first — which is the actual starting point of Stage 1. Free, three minutes, no account. ### What if I fail Stage 4, the interview? Most people do, the first time. The interview tests system design under real constraints and a client-facing case simultaneously, which almost nothing else prepares you for. Treat it as a measurement, not a verdict. --- Source: https://forward-deployed-engineer.tech/become Publication: Forward Deployed — the publication of record for Forward Deployed Engineering. Editor: Pierre-Thomas Liger-Belair. This markdown mirrors the HTML page at the URL above. Content is written and edited, not generated in bulk.