2022–2026 Cursor, SpaceX and xAI New Grad OA / Interviews: 15 Experiences
- Company
- Cursor
- Reports
- 15 interview reports
- Level
- New Grad
- Stages
- Phone screen → Onsite
Cursor, SpaceX and xAI new grad reports
- Cursor (reports 01 and 02): one research scientist phone screen from July to September 2026, after the SpaceX deal announcement (posted under SpaceX and titled Cursor/SpaceXAI), and one software engineer loop from November 2025.
- SpaceX (reports 03 to 13): ten software engineer reports and one full-stack report, July 2022 to August 2026, across Starlink, Starshield, Falcon, flight software and teams the candidates didn't name.
- xAI (reports 14 and 15): two "Exceptional Software Engineer" loops, reported in January and July 2026.
- Cursor reports posted after the SpaceX acquisition announcement: seven experienced or level-not-reported reports from July to October 2026. Four of them had the same filesystem hash tree that shows up in report 02 below.
- SpaceX full-time reports: Part 1 and Part 2.
SpaceX announced its deal for Cursor in June 2026, and candidates now call the combined company SpaceXAI. This puts the new grad reports from all three teams side by side.
Coverage: Fifteen new grad candidates. Cursor: one research scientist (titled Cursor/SpaceXAI; PhD, phone screen, July to September 2026) and one software engineer (United States, November 2025). SpaceX: ten software engineers and one full-stack software engineer, reported from July 2022 to August 2026, including Starlink (Redmond), Starshield, Falcon, flight software and a Hawthorne loop. xAI: two software engineers on the Exceptional Software Engineer track, reported in January and July 2026. Stages run from recruiter calls and take-home assessments through phone screens, project presentations and onsite loops.
Cursor
Research scientist, new grad
What came up
The one report, which the candidate titled Cursor/SpaceXAI, is a phone screen with two parts: an hour of ML coding, where the task was speculative decoding, and an hour-long research chat.
Questions we found
ML Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Implement normal decoding and speculative decoding; speculative decoding must run faster | 1 report | Report date: 2026-09-02 |
1 detailed candidate timeline
01: Speculative decoding in an hour
Interview date: July to September 2026 · Report date: September 2, 2026 · Role: Research scientist, new grad (listed by the candidate as Cursor/SpaceXAI) · Experience: PhD · Process: Referral · Result: Waitlisted
ML coding (60 minutes)
- Write a normal decoding function, then a speculative decoding function.
- The given signature was
speculative_decoing(model, tokenizer, prompt, draft, max_tokens), spelled that way in the report. - The test case checked that speculative decoding produced its output faster than normal decoding.
Research chat (60 minutes)
- The report gives only the length.
Two other people replied that they were interviewing for the same role.
Software engineer, new grad
What came up
There was one set technical problem in the whole loop: a hash tree, written inside an existing repository. Everything else was a conversation about the candidate's own work and a long, open-ended build in Cursor's code.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Filesystem Hash Tree (in the report, a hash tree Cursor uses, built inside a repo) | 1 report | Report: November 2025 (interview month); Additional FastPrep history: 2026-09-22, 2026-09-18, 2026-08-21 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Walk me through your background and past experience | 1 report | Report: November 2025 (interview month) |
| Why Cursor, and what are your plans after this? | 1 report | Report: November 2025 (interview month) |
| When do you graduate, and what are your plans around school? | 1 report | Report: November 2025 (interview month) |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Explore part of Cursor's codebase, pick something worth building, build it alone, and present it at the end of the day | 1 report | Report: November 2025 (interview month) |
1 detailed candidate timeline
02: A repo-based hash tree, then a whole day inside Cursor's code
Interview date: November 2025 · Report date: April 13, 2026 · Role: Software engineer, new grad (entry level, L3) · Location: United States · Process: About 5 weeks · Result: Still waiting when the report was written
Hiring manager chat (45 minutes)
- The first call was with the hiring manager. No recruiter screen came before it.
- They went through the resume together. The candidate talked about past internships and projects, with most of the time on things they had built themselves.
- Then came why Cursor, what the candidate planned to do next, when they graduate and how school fit in.
- The manager was frank about the company: flat, growing fast and intense. The candidate said it felt unscripted and more about fit than a checklist.
Repo-based coding round (60 minutes)
- Implement a hash tree inside an existing repository. The candidate understood it to be one Cursor actually uses.
- Google, GPT and Cursor were allowed for targeted syntax help.
Final round (8 to 9 hours, remote)
- Cursor opened up part of its codebase and a Slack channel. The task was left open on purpose: learn the code, find something worth adding, and build it alone.
- The candidate worked in that channel all day and presented the feature at the end.
Cursor told the candidate it was still working out what new grad hiring should look like. Looking back, the candidate found the loop loose and not always clearly defined, but much closer to the real job than a typical interview.
SpaceX
Software engineer, new grad
What came up
Seven of the ten reports had a take-home or a four-hour assessment. Three of those, from July 2022 to August 2023, were the same Starlink Beam Planner exercise. Networking and other quick CS questions came up in three live rounds.
| Topic | Reports | Most recent report |
|---|---|---|
| Take-home or four-hour timed assessment | 7 of 10 | 2026-08-24 (report date) |
| Database design or database implementation questions | 2 of 10 | 2026-08-24 (report date) |
| System design or feature-logic design | 2 of 10 | 2026-08-24 (report date) |
| Networking, data structures or quick CS fundamentals questions | 3 of 10 | 2025-10-06 (report date) |
| Coding rounds after the first screen (virtual, onsite or whiteboard) | 3 of 10 | 2025-02 (report month) |
| Project deep dive or project presentation | 2 of 10 | 2025-02 (report month) |
| Starlink Beam Planner assessment | 3 of 10 | 2023-08-10 (report date) |
A candidate can appear in more than one row.
Questions we found
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Design the database for a parts supply chain | 1 report | Report date: 2026-08-24 |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why do you want to work at SpaceX? | 1 report | Report date: 2025-10-06 |
| Introduce yourself / tell me about your background | 2 reports | Report dates: 2023-12-14, August 2022 |
| What are you most interested in working on? | 1 report | Report date: August 2022 |
| Do you know what SpaceX does? | 1 report | Report date: August 2022 |
Project Presentation
| Question | Frequency | All last seen dates |
|---|---|---|
| Present and go deep on a project you worked on | 2 reports | Report dates: February 2025, April 2023 |
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Monster Registry (four-hour Python assessment) | 1 report | Report date: 2023-12-14; Additional FastPrep history: 2024-03-28 |
| Starlink Beam Planner (four-hour take-home) | 3 reports | Report dates: 2023-08-10, 2022-10-02, 2022-07-27; Additional FastPrep history: 2024-04-25, 2024-03-20, 2023-10-23 |
10 detailed candidate timelines, loops, and screens
03: A practical take-home and a supply chain database
Report date: August 24, 2026 · Role: Software engineer, new grad · Result: No offer
Recruiter call (30 minutes)
Take-home
- The candidate described it only as practical.
Phone interview with someone from the team
- A technical discussion on how they would design the database behind a supply chain for parts.
The candidate rated the experience negative.
04: Flight software, one odd question and a few quick ones
Report date: October 6, 2025 · Role: Software engineer, new grad (flight software) · Location: United States · Result: No offer
HR round
First technical round
- It opened with what the candidate called an "out of the box" technical question. The report doesn't describe the problem.
- The interviewers then let the candidate ask their own questions.
- It finished with three faster questions on data structures and networking.
The one question the candidate listed was: why do you want to work at SpaceX? Even without an offer, they called the experience positive.
05: A verbal offer, then the job went away
Report date: February 2025 · Role: Software engineer, new grad · Location: Hawthorne, California · Result: No offer; the position closed after a verbal offer
Brief HR call
Two virtual coding assessments
Onsite
- One coding round.
- A one-hour presentation that went deep into a project the candidate had worked on.
Another virtual coding round
Across the coding work the candidate saw one feature-logic design question, one system design question and one depth-first search problem, and said not all of them were LeetCode-style. The report doesn't say which round each came in.
A verbal offer and a background check followed. About a week later, the candidate got a call saying the position was no longer available. They thought the process was good apart from that ending, and said HR had been helpful.
06: A four-hour Python assessment for the Falcon team
Report date: December 14, 2023 · Role: Software engineer, new grad (Falcon team) · Result: Rejected after the assessment
HR call
- The candidate applied on the SpaceX careers site with no referral and heard back about a week later.
- HR asked for a self-introduction, then laid out the process: an online assessment, a team interview, then an onsite. No behavioral questions.
- HR described the Falcon team as writing rocket logic, mostly in Python.
Online assessment (4 hours, over a weekend)
- Python only. No camera, and looking up code documentation was allowed.
- The task was the Monster Registry. Given a CSV file and a monster name, print that monster's ID, the monsters it's strong against, the monsters it's weak against, and its evolution chain.
- Each CSV row holds a monster's name, ID, types, the types it's weak to, and the ID of the monster it evolves into next.
- SpaceX supplied several test files.
The candidate finished in a little over two hours and passed every test. They split the work into many small functions and tried not to scan the data more than needed. They expected to move on, but a rejection came about two weeks later. Their guess was that the team wanted someone stronger in Python.
07: Starshield's assessment, then a networking screen
Report date: August 10, 2023 · Role: Software engineer, new grad (Starshield) · Experience: Master's · Process: Online application · Result: Passed the assessment, rejected after the technical interview
Online assessment (4 hours)
- The task was the Starlink Beam Planner. Users and satellites come as two maps from ID to a 3D position. A satellite can serve a user only within 45 degrees of vertical, carries up to 32 beams, and two beams of the same one of four colors can't sit within 10 degrees of each other.
- No camera and no proctor. The candidate wrote C++; running make shows the test results and also counts as submitting.
- Reading the statement and starter code took about an hour. A somewhat clever brute force passed every test case, with room left for deeper optimization.
The next day the candidate noted that a Starlink report from a year earlier had exactly the same assessment.
Technical interview
- Nearly all of it was computer networking. The candidate had only touched networking in an embedded systems class and couldn't answer most of the questions.
- They later linked a systems study sheet and said roughly 80% of the questions were on it.
08: A hard live round with a lot of database material
Report date: August 2023 · Role: Software engineer, new grad · Result: No offer
Phone screen
- Basic questions about the candidate's experience and projects. They had found the job on LinkedIn and applied on the careers site.
Virtual technical interview
- The interviewer was friendly, but the questions were hard: the candidate summed them up as LeetCode-hard with database implementation mixed in.
- A lot of it was about databases.
- The candidate felt it went badly enough that the interviewer ended it early.
They had solved 275 LeetCode problems going in and said it felt as if they hadn't studied at all.
09: Ten rounds for Starlink, ending in an offer
Report date: April 2023 · Role: Software engineer, new grad (Starlink) · Location: Redmond, Washington · Result: Accepted offer
Round 1: Recruiter call (30 minutes)
- The recruiter was more technical than the candidate expected. Their takeaway: know the company and your own resume.
Round 2: Technical exam (4 hours)
- The scenario was built around the real Starlink platform and needed advanced algorithms rather than routine LeetCode problems. The report doesn't give the task.
- The candidate finished in under two hours.
Round 3: Technical deep dive with the hiring manager (45 minutes)
- Pick one thing from the resume, an internship or a personal project, and go deep on it.
- Partway through, a lightning round of CS concept questions.
Round 4: Onsite panel presentation (30 minutes plus 30 minutes of Q&A)
- Present a technical project the candidate led or built. Their panel had eight engineers.
Rounds 5 to 8: Onsite one-on-one or two-on-one interviews with managers (45 minutes each)
- Whiteboard coding and problem solving that drew on math, computer science and physics. The candidate called these very technical.
- The verbal offer came the day after the onsite.
Rounds 9 and 10: Informal talks with senior leadership
- Behavioral questions with some technical content. One leader spent the whole session on an unfinished personal project of the candidate's.
Executive sign-off and the written offer came the next day.
10: The satellite team's take-home, solved greedily
Report date: October 2, 2022 · Role: Software engineer, new grad (satellite team) · Experience: Bachelor's · Result: Passed the assessment
HR call
Take-home exam (4 hours)
- An email after the HR call. The candidate downloaded a bundle with curl: an HTML page explaining the problem, skeleton code and a makefile. Running make with every test passing submits automatically.
- The limit was four hours, but full credit needed a passing submission within two. After that first passing submission, the remaining time could go to improvements.
- The task was the Starlink Beam Planner. Working out the 45-degree angle took the candidate 40 minutes.
- A greedy assignment passed every test case. After submitting, the candidate saw others suggest a 3D dynamic programming approach but didn't see how it would apply.
11: A team-specific assessment, then silence
Report date: August 2022 · Role: Software engineer, new grad · Location: United States · Result: No offer
Recruiter call
- Questions: tell me about your background, what are you most interested in working on, and do you know what SpaceX does?
- The recruiter then placed the candidate with one of five teams.
Team-specific online assessment (4 hours)
- The candidate passed. The report doesn't describe the task.
Hiring manager interview
- This was the last step before an onsite in Seattle. The hiring manager ghosted the candidate, and they never heard from anyone again.
12: A Starlink assessment graded on coverage, speed and style
Report date: July 27, 2022 · Role: Software engineer, new grad (Starlink) · Experience: Master's · Result: Rejected
Online assessment (4 hours)
- The task was the Starlink Beam Planner. Users and satellites are 3D vectors around a spherical Earth centered at (0, 0, 0). Return user-to-satellite links, each with one of four frequencies, covering as many users as possible.
- A satellite must be within 45 degrees of the user's vertical and can serve at most 32 users. Two users on the same satellite whose beams are less than 10 degrees apart need different frequencies.
- Six test cases had to pass within the four hours. Grading looked at coverage, a 60-second runtime limit and coding style.
The candidate rated it hard.
Full-stack software engineer, new grad
What came up
The one report had a take-home and a phone round that mixed a project deep dive with a full-stack question about what happens after a user enters a URL.
Questions we found
Full-Stack
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain the front-end and back-end interaction after a user enters a URL | 1 report | Report date: 2025-04-06 |
1 detailed candidate timeline
13: Starlink full-stack, out after the phone round
Report date: April 6, 2025 · Role: Full-stack software engineer, new grad (Starlink) · Experience: Bachelor's · Process: Online application · Result: Rejected after the phone round
Recruiter call (about 30 minutes)
- A recruiter emailed one or two days after the application. The call covered the candidate's background.
- The take-home went out right after the call.
Take-home assessment (4.5 hours allowed)
- The candidate said it's best to finish within two hours. The problem came from SpaceX's own technical work and was about LeetCode medium in difficulty. The report doesn't give the task.
Technical phone interview (45 minutes)
- Booked one or two days after passing the take-home.
- It started with the project the candidate knew best and several in-depth follow-ups.
- The rest was full-stack questions, such as explaining the front-end and back-end interaction after a user enters a URL.
The next round would have been the final one, in person. The candidate also noted that space-related jobs need at least a green card.
xAI
Software engineer, new grad (Exceptional Software Engineer track)
What came up
Both loops leaned on building with AI help. One had a four-hour take-home that the candidate vibe coded (built mostly by prompting an AI tool) in two hours; the other had an onsite where the design was drawn without AI and then implemented with it. The reported technical screens were a URL shortener design and a LeetCode problem.
| Topic | Reports | Most recent report |
|---|---|---|
| Building with AI tools (take-home or onsite) | 2 of 2 | 2026-07-01 (report date) |
| System design | 1 of 2 | 2026-07-01 (report date) |
| Rate limiter | 1 of 2 | 2026-01-28 (report date) |
| Resume deep dive | 1 of 2 | 2026-01-28 (report date) |
| LeetCode-style coding | 1 of 2 | 2026-01-28 (report date) |
Questions we found
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Design a URL shortener | 1 report | Report date: 2026-07-01 |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Insight platform backend: an API rate limiter at 100 requests per second and a consumer rate limiter at 10 requests per second | 1 report | Report date: 2026-01-28 (interview October to December 2025) |
2 detailed candidate timelines
14: Design without AI, then build with it
Report date: July 1, 2026 · Role: Software engineer, new grad (Exceptional Software Engineer) · Experience: Master's · Result: Rejected at the onsite
Recruiter contact
- HR had been in touch since February, and the candidate said the hiring timing moved around the company's IPO plans.
Technical screen (30 minutes)
- System design only: a URL shortener.
Onsite
- 30 minutes of whiteboard design with no AI.
- About an hour and a half implementing that design with AI tools.
- A 30-minute wrap-up and demo.
The candidate said the detailed questions were under NDA. In their view the new grad pipeline centered on system design and had no hand-coding round. They were rejected on the spot, with a six-month cooldown.
15: A rate-limiter take-home, then a short coding round
Interview date: October to December 2025 · Report date: January 28, 2026 · Role: Software engineer, new grad (Exceptional Software Engineer) · Experience: Bachelor's · Process: Referral · Result: Rejected
Online assessment (4 hours)
- The candidate picked the insight platform backend option, which they said matched what others had reported. It came down to an API rate limiter at 100 requests per second and a consumer rate limiter at 10 requests per second.
- They spent about two hours vibe coding it.
HR screen (10 minutes)
- Lining up the rest of the process.
First round (1 hour)
- A 15-minute resume deep dive.
- 45 minutes of coding on a LeetCode problem, which the report names only by a coded nickname.
The candidate said they answered every question and were still rejected.
Patterns across the reports
-
SpaceX software engineers: four-hour windows, about two hours of work. The candidates in 06 and 09 finished their four-hour assessments in about two hours, and in 10 full credit needed a passing submission within two hours.
-
SpaceX software engineers: the same Starlink take-home again and again. Reports 07, 10 and 12, from July 2022 to August 2023, all got the Starlink Beam Planner. The Starshield candidate in 07 noticed it matched a Starlink report from the year before.
-
SpaceX software engineers: networking questions. The flight software screen in 04 ended with data structures and networking questions, and the Starshield interview in 07 was nearly all networking. Report 09 had a lightning round of CS concepts inside the hiring manager deep dive.
-
SpaceX software engineers: presenting your own project. Reports 05 and 09 both had a project presentation: an hour that went deep into one project in 05, and 30 minutes plus Q&A in front of eight engineers in 09.
-
xAI software engineers: building with AI tools. Both xAI loops had AI-assisted building. In 15 the candidate vibe coded the four-hour take-home in about two hours, and in 14 the onsite had a design drawn without AI, then about an hour and a half of implementing it with AI.
More interview reports
- Cursor, SpaceX and xAI new grad (current)
- Cursor reports posted after the SpaceX acquisition announcement
- Cursor, role and hiring level not reported
- SpaceX full-time, Part 1
- SpaceX full-time, Part 2
Comments
0No comments yet — be the first to share what you know.