Levels, Pay & How Cursor Decides
- See why Cursor posts only two engineering titles, and how your level still gets set
- Read the posted base bands next to 2026 levels.fyi totals, and know why they differ
- Know what a screen rewards: working code, an extensible part 2, very few slips
- Know what happens after the onsite, including backchannel checks before references
Cursor (Anysphere) doesn't publish a level ladder. Engineering postings carry one of two titles, Software Engineer or Sr. Software Engineer, and an older posting described the organization as "very flat." Your level still gets decided. It happens case by case, out of public view. The company has also changed hands. SpaceX closed its all-stock acquisition of Cursor in August 2026. The brand, the blog and the careers site still say Cursor, but current engineering postings open with SpaceXSI text about Grok and "Super Intelligence," and the pay bands on them are SpaceXSI bands. Most of the pay data you'll find online comes from before that date. Keep that in mind for every number below.
Cursor software engineer levels
There are two titles on the careers page and no published rungs between them. What separates them in practice is experience, and each posting sets its own floor. Every posting also carries the same line: "Your actual level and base salary will be determined on a case-by-case basis." So treat the title on the posting as a starting point. You'll see L3, L4, L5 and L6 next to Cursor pay on levels.fyi. Candidates type those tags in themselves, so read them as their own guess and not as Cursor's ladder.
New grad (hired in 2025)
Cursor hired new grads in 2025, and one report was tagged Entry Level, L3. The team told that candidate it was "still figuring out what new grad hiring even looks like." As of November 2026 no new-grad or intern roles are posted.
Software Engineer
The base title on current postings. Floors vary by team: Research Tooling asks for a degree or 2+ years of professional experience, Pretraining Data for at least 3 years.
Sr. Software Engineer
Senior postings on ML Platform and Pretraining Data ask for 5+ years. The ML Platform post pitches "a flat, high-ownership environment."
Anything above senior
Not posted. If a recruiter mentions staff or principal scope, ask how it maps to pay, because there is no public rung to point to.
Openings move fast, so take this as a snapshot. In mid-November 2026 the open engineering roles were mostly model, data and ML-infrastructure jobs in Palo Alto: ML Platform, Pretraining Data, Research Tooling and RL Data. The general Software Engineer, Product posting for San Francisco and New York was live in May 2026 and has since come down. You apply to a named role, and ML Platform says it places people across its four teams by background.
How much a Cursor software engineer makes
Before the acquisition, Cursor posted no pay ranges at all. Now every engineering posting shows a base band, and they look like this.
| Posted role (November 2026) | Base salary band |
|---|---|
| Software Engineer, ML Platform | $140,000 to $225,000 |
| Sr. Software Engineer, ML Platform | $180,000 to $330,000 |
| Software Engineer, Pretraining Data | $160,000 to $250,000 |
| Sr. Software Engineer, Pretraining Data | $220,000 to $357,000 |
| Software Engineer, Research Tooling | $140,000 to $225,000 |
| Model Engineer, RL Data | $160,000 to $250,000 |
| Sr. Model Engineer, RL Data | $220,000 to $357,000 |
Then there's levels.fyi, which tells a very different story. It holds 18 US software engineer submissions for Cursor, with a median total of $950K a year. The median package is $325K base and $625K a year in stock, and it lists no bonus. Visible rows run from May to August 2026. An L3 in New York reported $484K in May. In August came an L4 in New York at $800K, an "Early" full-stack engineer in New York at $880K and an L6 in San Francisco at $1.0M. Top of the range is $1.65M. Those are real self-reported packages, but they describe grants of private Anysphere stock, valued at grant time, and every visible row was submitted before the close or the day after it. A Cursor offer-holder said in June 2026 that offers were still being written at the pre-deal valuation. No engineering offer with numbers from after the close has surfaced. So nobody can say yet whether new hires get packages like those rows or something closer to the posted bands.
Two candidates, in late 2025 and early 2026, said asking a recruiter for the range got them told they weren't a fit. That was when nothing was posted. Now the band is on the page, so you can read it there and save the pay conversation for the offer.
How Cursor decides
Cursor doesn't publish a rubric or say how individual reads turn into an offer. What candidates describe is consistent enough to work from. The screens are short, live and practical, usually 45 to 60 minutes with an engineer, and the problem grows while you work. The one reported most is something like a Merkle tree over a set of files: hash it, then find what changed. A few things keep coming up. Working code beats clever code. Part 2 checks whether your part 1 can stretch: one passing January 2026 candidate turned a single rate limit into an interface with two concrete rule classes. And the bar is high: finishing every part is not always enough, as the second outcome below shows.
Passed: working first, then extended
The January 2026 rate limiter candidate got a working version, then generalized it to new rule types. They heard back within an hour, and they passed.
Rejected after finishing every part
A September 2026 Merkle tree candidate wrote their own tests and finished every part, with a small bug or two along the way, and was turned down. "Their bar is really high," they wrote.
Four or five screens, no onsite
Two 2026 candidates sat four and five screens and never got the onsite. One had been told three rounds and a one-day onsite. Treat every extra screen as seriously as the first.
Rejected with part 2 unfinished
In one 2026 notification rate limiter screen, the candidate failed because the extensible part never got done. A working core alone did not carry them.
The onsite is the last stage. Current postings say it happens "in our office, where you'll work on a small project, discuss ideas, and meet the team." In 2025 that meant one or two days in Cursor's real codebase, ending in a demo, with meals alongside the team. In 2026 the length varies: an August 2026 candidate was told to expect a one-day pair-working onsite. The CEO said in 2025 that it tests things like "Can they go end-to-end in the codebase?" and "What would they build if left in a vacuum without a team?" After the onsite come backchannel checks. A candidate in April and May 2026 said they happened "after the onsite interviews, and before they asked me for references," and warned that word may reach your current company. The same candidate said everything apart from the work trial felt like "normal big tech type interviews."
Tips a close call toward yes
- A working first version early, then the extension, so there is always something that runs.
- An interface built to grow: new rule types or file changes slot in without rewriting the core.
- Your own tests as you go, so the small bugs show up before the interviewer finds them.
- A clear answer to what you would build in Cursor, drawn from your own use of it.
What sinks a close call
- Chasing optimal complexity while the basic version still doesn't run.
- A part 1 that has to be torn up when part 2 arrives.
- Letting AI write the solution in a screen. Web search for syntax is fine.
- Easing off in screen four because the earlier ones went well.
What Cursor says it wants
Cursor has no numbered values list, so don't go looking for one to recite. It has a few lines it has published in its own words. The careers page says: "We obsess over talent to an unusual degree and are designing a company that's a haven for self-motivated individual contributors." A May 2026 engineering posting said: "Our mission is to automate coding." The same posting described the people Cursor likes.
The application form tests this in miniature. It has a field for "a short note on a project you're proud of." Treat that note as the first round, and pick a project you'd be happy to go deep on later, because it may come back in a deep dive.
Common questions
What are the software engineer levels at Cursor?
There's no public ladder. Postings use two titles, Software Engineer and Sr. Software Engineer, and Cursor sets your actual level case by case after the interviews. People submitting to levels.fyi type in the L3 to L6 tags themselves.
How much does a Cursor software engineer make?
Posted base bands for engineering roles run from $140,000 to $357,000, plus equity. Levels.fyi shows a median total of $950K a year across 18 US submissions dated May to August 2026, but those are pre-acquisition stock grants, and no post-close offer with numbers has surfaced.
Did the SpaceX acquisition change pay?
Yes, in one visible way. Cursor posted no pay bands before the close, and now every engineering posting has one. Postings now say equity is part of total rewards at SpaceXSI, but the grant type and vesting for new hires aren't published. Ask for both in writing before you weigh an offer.
What does Cursor look for in the coding screens?
Working code first, then a design that handles the extension in part 2, delivered with very few bugs. Candidates in 2026 describe a bar where finishing every part with a small slip still ended in a no.
Key Takeaways
- ✓Cursor posts two titles, Software Engineer and Sr. Software Engineer. Your real level gets set case by case after the interviews.
- ✓Posted base bands run $140,000 to $357,000. The $950K levels.fyi median reflects pre-acquisition stock grants.
- ✓Get working code first, then make part 2 slot in cleanly. Small slips can still cost you.
- ✓Expect backchannel checks after the onsite and before formal references.
Cursor interview guideKnow what Cursor asks before you walk in.
9 coding · 4 system design · 16 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.