Rejected for Writing TypeScript: A Forward Deployed Engineer Story

When a recruiter reaches out on behalf of a company whose search bar you've used fourteen times today, you take the call. Curiosity wins.

The role? Forward Deployed Engineer. The call was short and ended about there :

"What's your current stack?"
"TypeScript. My client runs KiloCode."
"Ah. We need Python. That's blocking."

I write Python too. Didn't matter. Box unticked, call over. 🙃

That's not screening. That's Ctrl+F.

What an FDE actually is

An FDE is an engineer embedded with the customer. You don't build from a distance. You sit inside their environment, with their legacy systems, their security rules and their politics, and you ship something real.

Their own job ad, quoted by The Pragmatic Engineer, calls it an "embedded builder who bridges the gap between frontier AI products and production-grade reality within customers." The same piece estimates the job at roughly a quarter coding, a quarter meetings, and half integration.

Integration with what? With whatever the customer already runs. That's the job.

You speak the client's language

I speak French. If I move to England, I don't force everyone to speak French. I speak English.

Same thing here. Client runs Java? You write Java. Client runs a TypeScript fork? You ship TypeScript. Data team lives in Python notebooks? You meet them there. Adapting to the client's stack isn't a red flag. It's the job description.

Right now I'm leading an AI coding platform rollout at a major French bank. We just passed 7,000 licensees. TypeScript was the easy part. The hard part was getting it through a regulated environment, wiring it to an internal AI gateway, and onboarding thousands of developers who never asked for it. In Python, TypeScript, YAML and two human languages.

What to screen for instead

If you can't read the code, you can't screen on the code. So stop trying, and screen on what you can hear in a 20-minute call:

• Range, not current stack. Which languages have they shipped to production?
• Hostile environments. Have they deployed behind a corporate proxy, through a security review, inside a bank?
• Listening. Half the job is understanding what the client actually needs. The interview is a great place to test that. (It works both ways.)

The language is the easy part

With coding agents in every IDE, switching from TypeScript to Python takes a weekend. Getting a bank's security team to sign off on your deployment does not.

FDE hiring is about to explode. The winners won't hire the best Python developers. They'll hire engineers who walk into any room, learn the local language, and ship.

And no, still not looking. But if you're hiring FDEs and want to talk about what the role really takes, you know where to find me.