2 min lesson
The loop at a glance
Describe what "And one of those rounds is a paid, full-day build inside a real codebase" changes in practice.
Step 1 of 3
Before you prep a single answer, hold the whole shape in your head. The Forward Deployed EngineerAn engineer who embeds inside a customer's own engineering org to scope ambiguous problems and ship production-grade Cursor workflows a senior engineer keeps using after they leave. Press Enter for the full definition. loop at Cursor runs the standard engineering stages and then bolts on three rounds built around customer-facing delivery - and one of those rounds is a paid, full-day build inside a real codebase.
Treat the loop as one continuous argument that you can walk into ambiguity, drive AI tooling with taste and ship a workflow a senior customer engineer will actually adopt. Every stage tests a slice of that claim. The screens are remote; senior final rounds may pull you onsite in New York or San Francisco.
Learn more
Full explanation
The Loop, Stage by Stage
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
Step through each round to see what it tests and how to walk in ready.
Total span runs roughly 3-6 weeks across 5-8 touch points. Plan your energy across that window. The paid onsite alone will eat a full working day, so don't schedule it on top of a deadline at your current job.
Learn more
Advanced table
Times are approximate
- Stage
- Recruiter screen
- Rough time
- ~30 min
- What it tests
- Motivation, AI-space fluency, intensity fit
- Stage
- Hiring-manager screen
- Rough time
- 45-60 min
- What it tests
- End-to-end ownership, measurable outcomes
- Stage
- Technical screens (x1-2)
- Rough time
- ~60 min each
- What it tests
- Applied-AI coding + judgment driving AI
- Stage
- Decomposition case
- Rough time
- 45-60 min
- What it tests
- Scoping ambiguity, stakeholders, metrics
- Stage
- System design
- Rough time
- ~60 min
- What it tests
- Production AI workflow under real constraints
- Stage
- Paid build onsite
- Rough time
- 8-9 hrs
- What it tests
- Autonomous shipping, AI authenticity, defense
- Stage
- Behavioral / values
- Rough time
- 45-60 min
- What it tests
- Truth-seeking, ownership, mission fit
| Stage | Rough time | What it tests |
|---|---|---|
| Recruiter screen | ~30 min | Motivation, AI-space fluency, intensity fit |
| Hiring-manager screen | 45-60 min | End-to-end ownership, measurable outcomes |
| Technical screens (x1-2) | ~60 min each | Applied-AI coding + judgment driving AI |
| Decomposition case | 45-60 min | Scoping ambiguity, stakeholders, metrics |
| System design | ~60 min | Production AI workflow under real constraints |
| Paid build onsite | 8-9 hrs | Autonomous shipping, AI authenticity, defense |
| Behavioral / values | 45-60 min | Truth-seeking, ownership, mission fit |
Times are approximate; the loop is calibrated to the SWE process plus FDE-specific rounds.
AI tools are allowed (expected) in technical rounds, which inverts the usual test - you're graded on judgment, not recall. And the decision round is a paid, codebase-based build with a live Slack channel rather than a whiteboard. The format is a direct simulation of the job.
QWhich round is the real decision round in Cursor's FDE loop and what makes its format distinctive?