xAI interview, now SpaceXAI, and the statement before it.

Updated · Sources at the end

xAI is now SpaceXAI, a division of SpaceX since the all-stock merger of 2 February 2026, sitting alongside Starship and Starlink, and the Cursor code editor joined it when SpaceX closed its purchase of Anysphere on 14 August. A posting may carry any of the three names. The Grok loop below is the one candidates still describe; Cursor teams run their own, covered in the tracks.

xAI decides a lot about you before anyone speaks to you. The application asks for two things, a CV and a statement of exceptional work: a written account of your most technically complex, highest-impact project, and members of the technical team read it as part of the review rather than a recruiter. It is a technical document rather than a cover letter, and every claim in it is fair game later, because the deep-dive rounds are built on what you wrote. Candidates who describe what their team achieved, or who claim a level of seniority the detail does not support, report the process ending there. What follows is longer than most write-ups suggest: candidates describe five sequential rounds ending with an executive, and a flight to Memphis to meet the team if that one goes well.

Free · 2 minutes · no account

The questions for your exact xAI role and level.

See the questions xAI asks ↓Run a free mock interview →

Interviewing at xAI? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who xAI hires

xAI hires well beyond model research. Alongside the engineers building Grok, the consumer apps, the enterprise API and the X integration, it hires heavily for the data centres and the operations behind them, and it runs a large AI tutor programme including multilingual roles. The loops for these are not the same and are not close: candidates who have sat both describe the core onsite engineering rounds as much harder than the tutor ones. What the engineering side favours is people who have owned something hard end to end rather than people with the largest bank of memorised algorithm patterns, and the application format says so before the first call does. Since August 2026 the same division also hires for Cursor, the AI code editor, whose teams run a loop of their own.

Which loop you get depends on the kind of role rather than your level, and the four differ enough that preparing for the wrong one is wasted. Candidates also warn that the process changes between teams and between months, so treat any single account, including this one, as a shape rather than a schedule.

  • Track · Core

    Core engineering, onsite

    The deepest loop, and the one the statement of exceptional work matters most for. A recruiter screen, a manager conversation, a one-hour panel, a shorter technical round, then an executive interview, with a Memphis onsite to meet the team if the executive round goes well. Candidates who have done both say this is much harder than the tutor loop.

  • Track · Ops & DC

    Data centre and operations

    Scenario-driven rather than puzzle-driven. Candidates report questions across networking, Linux, operating systems, hardware, storage, GPUs, scripting and Kubernetes, framed as real incidents rather than theory: what would you do when this fails, in this order, and why.

  • Track · Tutor

    AI tutor and multilingual

    Includes a recorded step candidates name as Grok Recruiter: about five questions answered one at a time to camera, and for multilingual roles a split such as three in English and two in the other language, plus a translation of a supplied text at roughly B2 level. Lighter than the engineering loops, and the assessment is of language and teaching rather than code.

  • Track · Cursor

    Cursor, in the same division since August 2026

    A different loop from Grok's, with its own guide at /interview-prep/cursor-interview. Three to five rounds. One to three technical rounds of about an hour that lean toward applied AI systems and editor primitives, such as a syntax-aware edit operation, streaming model output, a file-tree diff or a context retrieval system, rather than pure algorithms. Then a work trial on site of up to two days on a frozen snapshot of the real codebase, with AI tools including Cursor itself allowed, followed by a review where you defend every line. Anysphere ran with no product managers and few management layers, so the bar is a generalist who owns a feature end to end, has used the product for real, and can say why this product rather than a hot company.

02

What is the xAI interview process?

Published accounts of xAI's process disagree more than most, loops vary by team, and candidates say the process changes often enough that someone else's experience may not describe yours. The stages below are the ones more than one account reports, and they are Grok's; Cursor roles run the separate loop described under the tracks. Timing is the least predictable part: replies range from hours to weeks, and one detailed account runs from an application in late June to an offer letter in late August, with the first interview ten days in and the second six weeks after that. Candidates also report interviewers running late across multiple rounds, and roles being withdrawn part-way through when hiring plans change.

01
Application, with a statement of exceptional work
A CV plus a written statement, short enough for a technical reviewer to scan

Name one project, the constraint that made it hard, whether that was scale, latency, correctness, reliability, research uncertainty or speed, the decisions you personally made, and what measurably changed. Separate your contribution from the team's. Engineers read this before a screen is scheduled, and the reported failures are generic motivation, team-level credit with no personal ownership, and claiming more seniority than the detail supports. Write it expecting to defend every line of it later.

02
Recruiter screen
About 30 minutes by video

Background, the statement, and which product area you want to build in. Candidates describe it as a straightforward walk through the CV rather than a technical filter: basics covered, no trick questions. Having no preference on product area reads as having applied to a logo.

03
Grok Recruiter, recorded
About five questions answered one at a time to camera

A recorded step with no interviewer present. For multilingual roles candidates report a split such as three questions in English and two in the other language, plus translating a supplied passage at roughly B2 level. The assessment is fluency, translation, and whether you can explain a grammar point simply, so speaking slowly and cleanly beats speaking fast.

AI tutor and multilingual roles
04
Hiring manager or associate manager
About 30 minutes

The first conversation with someone who would work with you. Your projects, your reasoning, and how you decide what to do when nobody has told you.

05
Technical panel
About one hour, several interviewers

The long round. For engineers, applied coding and design with the reasoning expected out loud. For operations and data centre roles, scenario-based problems across networking, Linux, hardware, storage, GPUs, scripting and Kubernetes, asked as real situations rather than definitions. Candidates say the point is how you think and operate rather than what you memorised.

06
Technical round
About 45 minutes

A shorter follow-up round, often a deep dive on the work in your statement. Architecture, the decisions you owned, and the numbers you claimed.

07
Executive interview
30 to 45 minutes

The last gate before an onsite. Candidates report a flight to Memphis to meet the team and the managers if this round goes well, which makes it the real decision point rather than a formality.

08
After the loop
No call. A wait of hours to weeks

Outcomes arrive on no fixed schedule: some candidates report an offer within days of the final round, others weeks of silence and then a rejection. Recruiters have told candidates they cannot give reasons for a rejection as a matter of company policy, so do not plan on feedback. A withdrawn role is also possible at this stage rather than a decision about you, and candidates have been told part-way through that the team stopped hiring for the position.

03

The Grok Recruiter interview: what it asks and how to pass

Reported problems and how to solve them

Grok Recruiter is the recorded step in xAI's AI tutor and multilingual loops: no interviewer, about five questions answered one at a time to camera, your audio transcribed and read afterwards. Candidates who sat it in 2026 report the shape below rather than the exact wording, which changes by role and language. It is not part of the engineering loop; core engineering candidates go from the recruiter screen to a hiring manager.

  • About five questions, one at a time, recorded: Each question appears, you answer to camera, and you move on; there is no follow-up and no chance to ask what was meant. Answer in full sentences with the point first, then one example, and stop. A minute to ninety seconds each; silence and restarts are transcribed too.
  • For multilingual roles, a split between languages: Reported as three questions in English and two in the other language. Do not switch mid-answer: the transcription is graded per language, and a sentence that drifts back to English in the other-language answer reads as a gap.
  • Translate a supplied passage: A short text at roughly B2 level, rendered into the other language. Accuracy over flourish: keep the sentence structure where the target language allows it, and do not paraphrase away a clause you are unsure of.
  • Explain a grammar point simply: The tutor test proper: pick a rule a learner gets wrong, state it in one sentence, give one correct and one incorrect example, and say why. A teacher's answer, not a linguist's.
  • It transcribes you, so speak for the transcript: Slower than feels natural, every word finished, no filler. Candidates who sat it say a clean slow answer scores better than a fast one that has to be untangled, because what is graded is the text of what you said.

If your posting is engineering, data centre or operations, none of this applies to you: those loops go straight from the recruiter screen to a person. The tutor loop is lighter than those, and candidates who have sat both say so.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at xAI.

Predict my xAI questions →
04

What xAI screens for

xAI puts most of its judgment into technical rounds and one piece of writing, so what it rewards is easiest to read from what it chose to ask for first.

  • Provable personal ownership. The statement asks what you did rather than what your team shipped, and the deep dive exists to check the answer
  • Difficulty over breadth. The prompt asks for your most complex work, so one hard project beats a list of competent ones
  • Evidence. Shipped systems, benchmarks, users, cost or reliability numbers carry the statement where adjectives do not
  • Operating rather than reciting. Candidates in the technical rounds describe scenarios rather than definitions, and the grading is on the order you would do things in and why
  • Adaptability. The process itself changes between teams and months, and candidates who arrived with a memorised script report it fitting badly
05

xAI interview questions

Candidate-reported themes

The behavioural ground at xAI is narrower than most, and almost all of it traces back to the statement you submitted. Prepare to defend that project rather than to assemble a broad story bank. The scenario questions below are the shape reported for operations and data centre loops.

Behavioural & motivation

  • Why xAI rather than another lab?Listening for: Specificity · Connection · Research
  • Walk me through the work in your statement and what you personally decided.Listening for: One hard project · Decisions that were yours · Numbers that hold
  • What was the hardest constraint in that project, and what did you do about it?Listening for: Names the constraint · What you did · Measured effect
  • How would the outcome have differed if you had taken the obvious approach instead?Listening for: The obvious path · Concrete difference · Honest limits
  • Which product area do you want to work in, and why that one?Listening for: Specific area · Reason tied to you · Knows the product
  • Tell me about something you delivered with almost no process around you.Listening for: Real situation · How you set direction · What shipped

Technical

  • Walk me through the architecture of the project in your statement, the decisions you owned, and how you measured the numbers you claimed.Project deep dive: The round built on your statement. Architecture, the decisions you owned, and every number you claimed in writingListening for: Clear architecture · Owned decisions · Numbers defended
  • Practice: Design a rate limiter for an API that serves model completions to many customers. Scope the problem first, then talk through the design.Applied coding and design: Coding with the reasoning expected out loud, and design questions where scoping the problem is part of the answerListening for: Scoped first · Sound design · Reasoning out loud
  • Practice: A GPU node in the cluster will not come back after a reboot. What do you check first, second and third, and what if the first answer is wrong?Infrastructure scenarios: Networking, Linux, operating systems, hardware, storage, GPUs, scripting and Kubernetes, asked as incidents to work through rather than topics to defineListening for: Sensible order · Concrete checks · Plan if wrong
  • Practice: Pick a grammar rule learners often get wrong. State it in one sentence, give one correct and one incorrect example, and say why.Language and teaching, for tutor roles: Fluency in both languages, translating a supplied passage at around B2, and explaining a grammar point or a correction simplyListening for: Rule stated simply · Examples given · Clear delivery

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my xAI questions →
06

Pay

Level 4$640K total

Levels.fyi for software engineers at xAI in the United States, read on 9 September 2026, where the Level 4 median is $640K made up of roughly $240K base and $400K a year in stock. Levels.fyi quotes $660K as the median in one place and $640K in another, and the highest reported package is $1.2M. The sample is small and concentrated at one level, so treat these as an order of magnitude rather than a band structure. Stock is the larger half of these numbers. The figures were reported before SpaceX listed on the Nasdaq in June 2026, so the equity behind newer offers is in a public company and priced daily, while what is vested and when still depends on the grant. Tutor, operations and data centre roles are paid on separate scales and are not covered by this figure.

07

How to prepare for an xAI interview

  1. Write the statement first and give it real time. It is read by engineers before any call, it decides whether there is a call, and it becomes the spine of the deep dive. One project, the hardest constraint in it, the decisions that were yours, and numbers.
  2. Cut team credit out of the statement. The reported failure is a strong project described in the first person plural, which leaves a reviewer unable to tell what you did.
  3. Do not overclaim your level. Reviewers compare the seniority you imply against the detail you give, and the mismatch is more damaging than a smaller claim would have been.
  4. Prepare to defend every line of it out loud. Rehearse the deep dive as an interview rather than rereading the document, because the questions come at the decisions rather than the description.
  5. For operations and data centre roles, rehearse incidents rather than topics. Take a network failure, a dead disk, a GPU node that will not come up, and talk through what you check first, second and third, and what you would do if the first answer were wrong.
  6. For the recorded tutor step, speak slowly and cleanly. It transcribes what you say, so a slower answer with no mistakes reads better than a fast one that has to be untangled.
  7. Expect the process to move oddly, and keep other applications alive. Late interviewers, gaps of weeks between rounds, and roles withdrawn mid-process are all reported often enough to plan around. A delay is not a decision, and a rejection will probably arrive without a reason, because recruiters cite company policy for not giving one.
  8. For a Cursor role, use the product for real before you apply, and prepare for the work trial as the round that decides: up to two days in the real codebase with the editor allowed, then a review where every line you kept has to be yours to explain.
  9. Read recent candidate threads before you commit weeks to this loop. Accounts of the experience are mixed and some are strongly negative about hours and culture, and a few describe abrupt interviewers. That is worth weighing against the pay rather than discovering at the offer stage, and it is a fair thing to ask about directly in the manager round.

This guide covers xAI's engineering loop in depth, and the statement of exceptional work and the later rounds apply to operations, data centre and tutor roles as well. Cursor roles, in the same SpaceXAI division since August 2026, have their own track above. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Anthropic, OpenAI or Google DeepMind? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run an xAI mock: spoken answers, coached on the spot. Your first mock is free.

Run an xAI mock →
08

FAQ & sources

What is xAI's interview process?

Published accounts of xAI's process disagree more than most, loops vary by team, and candidates say the process changes often enough that someone else's experience may not describe yours. The stages, in order: Application, with a statement of exceptional work; Recruiter screen; Grok Recruiter, recorded; Hiring manager or associate manager; Technical panel; Technical round; Executive interview; After the loop.

What does xAI look for in candidates?

xAI puts most of its judgment into technical rounds and one piece of writing, so what it rewards is easiest to read from what it chose to ask for first. Provable personal ownership; Difficulty over breadth; Evidence; Operating rather than reciting.

What questions does xAI ask in interviews?

The behavioural ground at xAI is narrower than most, and almost all of it traces back to the statement you submitted. Technical themes: Project deep dive; Applied coding and design; Infrastructure scenarios; Language and teaching, for tutor roles.

What is the Grok Recruiter interview at xAI?

Grok Recruiter is the recorded step in xAI's AI tutor and multilingual loops: no interviewer, about five questions answered one at a time to camera, your audio transcribed and read afterwards. Candidates who sat it in 2026 report the shape below rather than the exact wording, which changes by role and language. Covered on this page: About five questions, one at a time, recorded; For multilingual roles, a split between languages; Translate a supplied passage; Explain a grammar point simply; It transcribes you, so speak for the transcript.

How do I prepare for an xAI interview?

Write the statement first and give it real time. It is read by engineers before any call, it decides whether there is a call, and it becomes the spine of the deep dive. One project, the hardest constraint in it, the decisions that were yours, and numbers. Cut team credit out of the statement. The reported failure is a strong project described in the first person plural, which leaves a reviewer unable to tell what you did.

Prep for a real xAI role

Practise your xAI interview, out loud.

Paste a real xAI posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the xAI prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

xAI Interview, Now SpaceXAI: Statement, Loop, Pay — Calibrd