Career Track~10 min readUpdated Jul 2026

The Reality

A day in the life of
an FDE

A composite built from the published first-hand accounts — Palantir, PostHog, Baseten — and from the split frontier labs put in their own job descriptions. Three day shapes, because the honest answer to “what is a typical day” is that there are three of them and you rarely choose which one you get.

Day shape 1 — on the customer site

Week three of a deployment. You are in their building. This is the day people imagine when they hear "forward deployed" — and it is roughly a third of the calendar.

Time	What happens	What is really going on
08:40	You arrive early and get pulled into a stand-up you were not invited to.	This is good. Being in the room is 80% of the trust-building, and you just learned that a system migration lands next month — which changes your integration plan.
09:20	Shadow an analyst doing the workflow by hand.	Discovery. She does two undocumented steps she never mentions in meetings because “everyone knows that”. One of them invalidates your data model.
10:30	Rework the mapping over coffee, on a laptop, in a corridor.	Ugly, hardcoded, correct on one real record. Speed over polish is not a slogan here; it is what keeps the loop tight.
11:00	The third source system returns 403 from inside their network.	Egress rules. Ninety minutes with their network team, most of it waiting. You use the waiting to write the eval that will define “working”.
13:00	Lunch with the champion. Not scheduled.	The highest-leverage hour of the week. You learn a VP is sceptical, and why. That reframes your next demo entirely.
14:00	Security questionnaire, 140 rows.	Nobody’s favourite. Doing it early instead of at the end is the difference between shipping and a great POC that IT vetoes in month four.
15:30	Demo the one-record prototype to three people.	Their reaction reshapes the scope. Five new “can it also…” requests, two of which reveal the actual problem.
17:00	Write it up: what changed, what you are not building, what you need by Friday.	The written trail is what makes the next scope conversation short instead of political.
20:30	Hotel. Fix the mapping properly, push, sleep.	The travel tax. Nabeel Qureshi’s account of four days a week on site for a year is the canonical version of this rhythm.¹⁴

Code written today: maybe two hours. If that number horrifies you, weigh it against the alternative: everything else on this list is what stops the two hours from being wasted on the wrong problem.

Day shape 2 — remote build day

The other two-thirds. Closer to a normal engineering day, with three interruptions that are not optional.

Time	What happens
09:00	Triage overnight messages from two customers in other timezones. Answer the one that unblocks someone; schedule the rest.
09:30	Real building block. The retrieval pipeline over their document store, or the agent’s tool definitions, or the eval harness. This is the block you protect.
12:00	Internal sync: what you are seeing at the customer that the product should absorb. Roughly a third of the job at a frontier lab is exactly this feedback loop.¹⁰
13:00	Second building block, usually the unglamorous half — retries, idempotency, the reconciliation job, the runbook.
15:00	Customer call. Weekly demo of whatever is working. Never skip it, even when there is little to show — the cadence is the trust.
16:00	Eval run against the golden set. Two regressions. One is a genuine bug, one is a labelling disagreement between their experts — which is a meeting, not a fix.
17:00	Write the generalisation note: what from this engagement should become a product capability. The rung-four habit that moves careers.

→ The load-bearing line in that day

16:00. “A regression that is actually a labelling disagreement” is the most FDE sentence there is: a technical signal whose resolution is a human negotiation. Handling that gracefully is the skill that separates senior from mid.

Day shape 3 — launch week

Two or three of these per engagement. Highest stress, highest payoff, and the day the previous six weeks get graded.