Thought Needle Book a walkthrough
Thought Needle · FDE assessment

The hard part of the job isn't the code.

Forward deployed engineers get hired on GitHub profiles and coding tests, then come apart on the client call — the requirement nobody stated, the stakeholder who never asked for this, the constraint that lands on day nine. So we put candidates inside a company and watch what they actually do.

Book a walkthrough See the simulation

↳ Three hours in a company that doesn't exist — built from ones that did.

sim running env · meridian-freight · logistics
6 stakeholders · 2 with conflicting mandates 0 of them real
The gap

An FDE is closer to an early-stage founder than to a backend hire.

Find the pain nobody stated. Spot the gap technology can actually close. Prove it with something rough and fast, in front of a customer who isn't on your side yet. Nothing on a résumé, a GitHub profile, or a HackerRank score tells you whether someone can do that — so teams find out in month three, on a live account.

“Even 10x engineers freeze in a client conversation and aren't deployable as FDEs.”

— a services firm trying to scale its FDE bench
Blind spots

Three things a coding test
structurally cannot see.

01 — The unsaid

The requirement nobody wrote down

The brief says “fix the dispatch backlog.” The actual problem is a whiteboard that three people trust more than the software.

02 — The room

Incentives that don't line up

The COO wants it by Q3. The dispatch lead never asked for this and can kill it quietly. Both are in your first meeting.

03 — The late news

Constraints that arrive too late

No data leaves the building. The schema is from 2009. The vendor contract renews in May. None of it was in the brief.

How it works

Three hours inside a company
that doesn't exist.

Every candidate gets the same company, the same stakeholders, the same landmines. What differs is what they do with them.

Step 01

A brief, an inbox, and no orientation

The candidate lands at Meridian Freight on a Tuesday morning with one email from the COO and access to whatever the company runs on. No task list. No hint about who matters, who's threatened, or what's already been tried twice.

inbox · 1 of 12 unread08:04
From
Dev Mehta — COO
Subject
Re: dispatch backlog — Tuesday?

Rahul says you're the person who can sort this out. We're losing most of a shift a week to the dispatch backlog and the TMS people keep telling me it's configured correctly. Come in Tuesday, talk to whoever you need. I have twenty minutes at eleven.

org-chart-2019.pdf vendor-msa-signed.pdf
Step 02

Stakeholders who aren't trying to help

Each one is a simulated person with a role, a history, and something to protect. They contradict each other. They leave things out. They'll answer a question they weren't asked with the safe version of the truth. The candidates who dig are the ones who find out.

interview 02 · dispatch lead 04:12
CANDIDATE

Before I touch the backlog — how do loads actually get assigned today?

RENU K. · DISPATCH LEAD

Whiteboard. The TMS says one thing, the drivers say another. I go with the drivers.

CANDIDATE

So what happens at cutoff when the TMS and the whiteboard disagree?

RENU K. · DISPATCH LEAD

Then I'm on the phone until nine. Nobody upstairs knows that. Don't put it in a deck.

▲ unstated requirement found the COO's brief never mentioned the whiteboard
Step 03

A scope — and the nerve to cut

Then they write what they'd build and why, against the constraints they actually managed to surface. What a candidate refuses to build, and how they explain that to the person who asked for it, is half the signal.

proposal · draft 201:47 elapsed
Building
  • One-way sync: dispatch board → TMS, on a 5-min poll
  • Exception queue for the rows the drivers override
Not building
  • Live two-way sync — can't clear compliance in the window
  • Replacing the whiteboard — nobody asked, and Renu would route around it
no egress from the DC Oracle 11g 2 FTE to maintain vendor locked to May
Step 04

Then they build it, on someone else's stack

The implementation runs with coding agents against the org's real tech — the legacy schema, the deploy policy, the service nobody has touched since 2011. We watch how they steer the agent, how they verify what it hands back, and what they do the first time the environment says no.

agent run · tms-bridgemeridian/prod-mirror
$ agent run --repo tms-bridge --plan proposal-d2
▸ schema read — 214 tables, 11 without FK constraints
▸ plan — one-way sync, dispatch board to TMS
✗ blocked — outbound HTTPS denied by site policy
▸ revised — drop to shared volume, TMS polls the file
▸ candidate reverted 2 agent edits to dispatch_legacy
✓ 41 min · 0 policy violations · shift cutover clean
Step 05

One page your hiring team can act on

You get a rubric built for this role, not a percentile against strangers. Every score points back at the moment that produced it — the question they didn't ask, the constraint they caught late, the thing they shipped anyway.

See a full report
report · candidate 0417 · meridian-freight sample
Requirements discovery 4/5

Found the whiteboard workflow in interview 02, before proposing.

Stakeholder handling 3/5

Never spoke to Compliance until the build was underway.

Constraint adaptation 4/5

Dropped the cloud sync once the no-egress rule surfaced. Re-scoped in 20 min.

Scoping under pressure 5/5

Cut two of four asks and said why. Landed inside the window.

Execution with agents 4/5

Drove the run against a 2009 Oracle schema without breaking dispatch.

recommend · onsite every score links to the moment it came from
The environments

Built from companies
that actually existed.

A generic “Acme Corp” tests nothing — candidates can feel the cardboard. Ours are assembled from real material: codebases and inboxes from companies that shut down, interviews with the people who did those jobs, and org structures that behave the way real ones do. Slow, political, inconsistent.

Environment

Regional bank

A change-approval board that meets on Thursdays, a core system nobody is allowed to touch, and a head of risk who has seen four consultants come and go.

Environment

Hospital network

Clinical staff who won't change a workflow mid-shift, procurement that moves in quarters, and patient data that cannot leave the building under any argument.

Environment

Freight & logistics

A dispatch floor that runs on a whiteboard, a TMS vendor with a live contract, and a COO who has already been sold this project once before.

↳ Or bring your own — we build the environment from your stack and your customers' world, so the assessment looks like the account they'd be deployed on.

Hiring forward
deployed engineers?

We're working with a small number of teams to build the standard for this role. If you're screening FDEs today, we'd like to hear how — and show you what a run looks like.

[email protected]