1 min lesson
The loop at a glance
Say what this means in practice: "A two-day on-site project where you build alongside the team and present at the end."
Step 1 of 2
Before you draft a single answer, hold the whole shape in your head. The Software Engineer, Infrastructure loop at Cursor runs the standard engineering stages, then ends on something most companies don't do at all: a two-day on-site project where you build alongside the team and present at the end.
Read the loop as one continuous claim that you can operate the foundation under a product serving 1M+ daily active users - cloud, networking, Kubernetes, edge and cost - as a functioning senior IC from week one. Each stage tests a slice of that claim. Two stages are unusual at Cursor: the first technical screens forbid AI beyond editor autocomplete and the final round is a real build with the team rather than a whiteboard.
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 stage to see what it tests and how to prep. Stage count and naming vary by level - confirm yours with the recruiter.
Cursor runs roughly a four-to-five stage loop, with the on-site project as the decisive round rather than a formality. Plan your energy across the full span. The two-day project alone is a serious time commitment, so don't stack it on top of a crunch at your current job.
Learn more
Advanced table
Times are approximate
- Stage
- Recruiter screen
- Rough time
- ~30 min
- What it tests
- Motivation, infra focus, Cursor knowledge
- Stage
- Technical phone screen
- Rough time
- ~60 min
- What it tests
- Raw coding fundamentals, no AI crutch
- Stage
- Take-home (senior)
- Rough time
- 4-8 hrs
- What it tests
- Realistic engineering, production habits
- Stage
- On-site technical
- Rough time
- Several hrs
- What it tests
- Coding, infra system design, past-work depth
- Stage
- Behavioral / HM
- Rough time
- 45-60 min
- What it tests
- Pace fit, craft, truth-seeking, judgment
- Stage
- 2-day on-site project
- Rough time
- ~2 days
- What it tests
- How you actually work; genuine passion
| Stage | Rough time | What it tests |
|---|---|---|
| Recruiter screen | ~30 min | Motivation, infra focus, Cursor knowledge |
| Technical phone screen | ~60 min | Raw coding fundamentals, no AI crutch |
| Take-home (senior) | 4-8 hrs | Realistic engineering, production habits |
| On-site technical | Several hrs | Coding, infra system design, past-work depth |
| Behavioral / HM | 45-60 min | Pace fit, craft, truth-seeking, judgment |
| 2-day on-site project | ~2 days | How you actually work; genuine passion |
Times are approximate; stage count and naming vary by level - confirm specifics with your recruiter.
The early technical screens ban AI beyond autocomplete, which inverts the modern norm and puts your unaided fundamentals on display. And the decision round is a two-day build with the team instead of a whiteboard. Both are deliberate filters: one for raw skill, one for whether you actually want this job.
Exact stage count and naming shift by level and recruiter. A staff candidate may get the take-home where a mid-level candidate skips it. Treat this as the modal path and confirm your specific schedule with your recruiter early, so you prepare for the rounds you'll actually face.
QWhich round actually decides the Infrastructure hire at Cursor and what makes its format distinctive?