talk about how to transition from SDE/SWE into an FDE (Forward Deployed Engineer) role

been seeing this term pop up a lot lately and wanted to actually sit down and think through it, because honestly my first reaction was "isn't this just sales engineer with a new name." turns out not really.

closest way i can put it: company's got a product or some AI thing that looks amazing in the demo, then it hits an actual customer and their environment is just chaos. data's scattered across five old systems nobody documented properly, permissions are a mess, compliance has eighteen requirements nobody mentioned, and the business process looks nothing like the clean diagram in the sales deck. someone has to actually go in there and make the thing work. that's not writing features, and it's not really pre-sales either, it's somewhere in between.

SWE you're mostly heads down building stuff internally. FDE is more like you take the product out to the customer and fight to get it actually running there. and right now been looking into this FDE transition thing for a while now so figured i'd actually write down what i found instead of just guessing at it.

first thing i had to get past was assuming it's just sales engineer with a new name, it's not really. someone at a company has a product that works fine internally, then it hits an actual customer and their environment is a mess, data's scattered everywhere, permissions are unclear, compliance stuff nobody warned anyone about. FDE is the person who goes in and actually makes it work in that mess. palantir basically invented this over a decade ago and now most ai labs run their own version of it, openai, anthropic, sierra, decagon, sometimes under different names like solutions engineer or applied ai engineer or deployment engineer.

what actually seems to get people in the door is oncall ownership, being the one accountable when something breaks at 2am, which is honestly a lot easier to get at a smaller company where on-call isn't spread across twenty people. also your resume can't just list tasks, it needs to show an outcome. "built a microservice in python" doesn't say anything, but something like "integrated three systems, cut manual processing by 62%" is closer to what they're actually screening for.

interviews aren't leetcode-heavy from what i've read, more rate limiters, streaming data, distributed job queues, but the followups go deep into deployment tradeoffs and evals instead of just correctness. apparently anthropic's version of this role leans really hard on "how do you know your system is actually working," and hand-waving through that question tanks you fast. openai's process reportedly has you build something real on their api, a rag system or an agent or an eval harness, then defend your design choices afterward. customer facing experience gets weighted heavily too, even in the technical rounds, so if all you've got is internal tooling that's apparently a real gap interviewers poke at.

the part that stuck with me most though is less about learning new frameworks and more just redefining what "good engineering" even means day to day. as an SWE you get a ticket with expected behavior already scoped out for you. as an FDE your actual first job is figuring out what the smallest safe thing is that solves the customer's real problem, and a feature can be fully shipped and technically working and still be a failure if nobody trusts it or it doesn't fit how they actually work.

if you can't land it directly, the more realistic path seems to be staying in a normal SWE role but deliberately chasing the stuff that builds toward it, on-call ownership, customer-facing side projects, integration work, over like a year or so instead of hoping it happens on its own. Curious if anyone here has actually gone through this, what your interview actually looked like～