What did candidates report about the SpaceX onsite interview?

A one-hour presentation on a past project, then one-on-one interviews. A 2024 Redmond candidate had a Starlink factory tour, a 15-20 slide presentation, lunch with the recruiter, and system design, behavioral and whiteboard coding interviews of 45 minutes each. A June 2026 Los Angeles candidate and an October 2025 Hawthorne candidate were sent home after the presentation stage.

How long is the SpaceX coding round?

Long. A Hawthorne software intern in 2025 had a coding round of about four hours, and a 2024 Redmond candidate had a 2-4 hour assessment on an optimization problem. An October 2025 Hawthorne engineer had a take-home instead.

How fast does SpaceX decide?

Often quickly. The 2025 Hawthorne intern heard back about two weeks after the interview, an April 2025 operations candidate said there is no drawn-out decision process, and some onsite candidates are told the same day to leave after the presentation. Others, such as the 2024 Redmond candidate, never received a final decision.

SpaceX Interview Experience 2026

SpaceX candidates describe a phone screen, a long coding assessment or take-home, a technical call with a detailed project review, and an onsite that starts with a one-hour presentation on their own project and continues with one-on-ones on system design, whiteboard coding and behavior. Candidates were asked about memory hierarchy, an optimization problem, op-amp circuits for a test role, and every decision in their presentation. Several were sent home right after the presentation, before the one-on-ones.

Of the reports below, the two interns received offers, and none of the full-time software engineers did.

SpaceX interview process round by round

Round	Duration	What it tests
Phone screen	Short	Why SpaceX, resume
Coding assessment or take-home	2-4 hours	Optimization or implementation problem
Technical call	~45 min	Project review plus fundamentals or coding
Onsite presentation	~1 hour	Your project, questioned closely
Onsite one-on-ones	~45 min each	System design, behavioral, whiteboard coding

SpaceX interview process: reports by role

These come from self-reported write-ups on Taro (jointaro.com) and PracHub. Each is one candidate’s account.

Software engineer, Hawthorne (October 2025, no offer). Phone screen, a take-home assessment, a project review with an engineer, then an onsite of a panel presentation followed by four back-to-back one-on-ones. The candidate was asked to leave after the panel.
Software engineering intern, Hawthorne (April 2025, offer). A 45-minute technical call with a software engineering manager on the types of memory and their trade-offs (L1 and L2 cache, RAM, solid state), then a coding round of about four hours. Heard back in about two weeks.
Associate software engineer, US (November 2025, no offer). A quick phone interview that was not difficult, including why do you want to work here. Rejected a few days later.
Engineering intern, Bastrop (January 2025, offer). Two technical calls. The first covered every part of the resume, several technical questions, and why SpaceX; the second was very short.
Test engineer, US (September 2025, no offer). Phone screen, a difficult LeetCode-style challenge combining Python with circuit design (inverting and non-inverting amplifiers), then a technical interview on that problem and basic electrical concepts, focused on programming principles.
Operations engineer, US (April 2025, no offer). Introductory call, a technical interview with the manager, then a campus tour and technical presentation. Asked how they overcome adversity in the workplace. The candidate said SpaceX moves quickly: you either get it or you do not.
Software engineer, Los Angeles (June 2026, PracHub, no offer). Three phone interviews, then an onsite presentation of about an hour on the candidate’s greatest achievement. Sent home right after, before the one-on-ones.
Software engineer, Bastrop (July 2026, PracHub, no offer). HR screen, a technical screen with a hiring manager and a team member that was described as a quick chat but was technical, then a half-day onsite with a short slide presentation and technical conversations on fundamentals where interviewers pushed back on answers.

Detailed interview experiences

Experience 1: Software engineer, Redmond (2024, no offer)

Recruiter phone call.

Coding assessment (2-4 hours): An optimization problem.

Technical phone call (45 min): An in-depth description of a previous project, then coding questions.

Onsite, Redmond:

Starlink factory tour
Project presentation, one hour with Q&A, 15-20 slides on a software project; the candidate said it took a lot of time to prepare
Lunch with the recruiter (30 min)
System design (45 min)
Behavioral (45 min), with follow-up questions on the presentation
Whiteboard coding (45 min)

Result: No decision communicated after the onsite, and no reply to a follow-up.

Takeaways

What decided it: Unknown; the candidate heard nothing back.
How to practice: Rehearse the presentation with someone who interrupts, and prepare system design and whiteboard coding for the same day.
Admin: Keep GPA and test scores on hand; the candidate had to find them years after graduating.

Experience 2: Software engineer, Hawthorne (October 2025, no offer)

Phone screen, then take-home, then project review with an engineer.

Onsite, part 1: A presentation to a panel.

Onsite, part 2 (planned): Four one-on-ones, back to back.

Result: Asked to leave after the panel.

Takeaways

Common fail: A presentation that does not hold up under questioning ends the day early.
How to practice: For each slide, write the three hardest questions someone could ask and your answer.

Experience 3: Software engineering intern, Hawthorne (April 2025, offer)

Technical call (45 min): With a software engineering manager on memory types: L1 and L2 cache, RAM, solid state, with advantages and disadvantages of each.

Coding round (~4 hours).

Result: Offer, accepted, about two weeks after the interview.

Takeaway: Review computer architecture basics; a short conversation on fundamentals can carry as much weight as the long coding round.

Experience 4: Software engineer, Los Angeles (June 2026, no offer)

Technical screen: Three phone interviews with different interviewers.

Onsite: A one-hour presentation on the candidate’s greatest achievement, described as evaluative and fast-moving, not conversational.

Result: Sent home right after the presentation.

Takeaway: Treat the presentation as a technical document that will be checked, not a story.

Experience 5: Test engineer, US (September 2025, no offer)

Phone screen, then a LeetCode-style challenge mixing Python and circuit knowledge, then a technical interview on the challenge and basic electrical concepts.

Question: What is the output of an inverting and a non-inverting amplifier?

Takeaway: Test roles expect both code and electronics. Review op-amp gain formulas and write Python that processes measurement data.

SpaceX interview questions that come up often

Technical

Types of memory and their trade-offs (cache, RAM, SSD)
An optimization problem in a 2-4 hour assessment
Output of inverting and non-inverting amplifiers
Detailed questions on your own past project

Onsite

A one-hour presentation on a project or your greatest achievement
System design (45 min)
Whiteboard coding (45 min)

Behavioral

Why do you want to work at SpaceX?
How do you overcome adversity in the workplace?
Follow-up questions on your presentation

SpaceX interview tips from these candidates

Spend the most prep time on the presentation. Two candidates ended their onsite there.
Expect pushback, even in rounds described as casual.
Block four hours for the coding round and practice long problems with tests.
Have academic records ready and follow up in writing after the onsite.

SpaceX behavioral round in these reports

The Redmond candidate’s behavioral one-on-one included follow-ups on their presentation, and why SpaceX came up in nearly every loop. Sample answers are on the SpaceX behavioral interview questions page, and round-by-round prep is on the SpaceX interview questions hub.

Sample answers for high-frequency questions

Q. What are the types of memory and their trade-offs?
A. L1 and L2 cache are fastest but small; RAM is larger and slower and loses data without power; SSD storage is non-volatile and far larger but much slower per access. Sequential access over contiguous data uses caches well, so data layout often matters more than small algorithm changes.

Q. What is the output of an inverting and a non-inverting amplifier?
A. Inverting: Vout equals minus (Rf divided by Rin) times Vin. Non-inverting: Vout equals (1 plus Rf divided by Rg) times Vin. Real outputs clip at the supply rails.

Q. Why do you want to work at SpaceX?
A. Name the program, a specific technical problem in it, and the work you have done that fits, then be ready to explain your reasoning when asked to.

SpaceX interview tips from these reports

Coding rounds

A 2025 Hawthorne intern had a coding round of about four hours.
A 2024 Redmond candidate’s assessment was a 2-4 hour optimization problem.

Presentation

About one hour, 15-20 slides, with close questioning.
Two candidates were sent home right after it.

One-on-ones

System design, behavioral and whiteboard coding, 45 minutes each.
Four back-to-back in one Hawthorne loop.

Sources

Similar companies

Tesla · Palantir · OpenAI · TikTok · ISRO · Honeywell · NVIDIA