2013–2026 SpaceX Full-Time OA / Interviews: 45 Experiences (Part 2 :)

Continued from Part 1: algorithms, implementation, CS fundamentals, and system design

Coverage: Part 2 covers mechanical and hardware questions, project and behavioral questions, a compact map of all 45 full-time reports, and role-specific preparation.

Mechanical, manufacturing, propulsion, materials, and hardware questions

Topic frequency

Exact reported questions and topics

Each item below appeared in one report unless the table above gives a higher family frequency.

1. Explain the meaning of a modal participation factor.
2. Find the stress in a cantilever beam with a load at the free end.
3. Explain where a pressure vessel will fail when pressure rises until failure.
4. Solve fluid questions involving mass-flow rate and the operation of a device.
5. Explain beam bending, stress, strain, fracture, and buckling.
6. Apply design-for-manufacturing thinking.
7. Explain why a soda can has its familiar shape.
8. Explain Young's modulus.
9. Explain coefficient of thermal expansion.
10. Explain hoop stress.
11. Explain tensile strength.
12. Estimate an answer to a drawn hoop-stress problem, then prove whether it is correct.
13. Explain pipe flow and Bernoulli's principle.
14. Explain converging-diverging nozzles and choked flow.
15. Explain the rocket thrust equation.
16. Explain heat-transfer modes and perform basic heat-transfer calculations.
17. Explain how to validate an FEA or CFD result with residuals and hand calculations.
18. Explain how to set up a fracture analysis.
19. Explain how to resolve a boundary layer.
20. Explain the simplest GD&T constraint.
21. Explain how many degrees of freedom a profile tolerance can constrain.
22. Explain bolted-joint failure modes in tension and shear, including where each failure occurs.
23. Explain why GD&T is needed.
24. Show how a curved surface should be represented on a drawing and measured after manufacturing.
25. Explain how to drill a through-hole in a sphere.
26. Reason through an energy-balance problem.
27. Describe a design project completed outside class, with emphasis on the design process.
28. Explain which materials are best known and how that knowledge fits the role.
29. Explain SpaceX engines, launch vehicles, capsules, and where each engine is used.
30. Name SpaceX rockets, discuss launch history, and explain the reported Falcon assembly question.
31. Explain Falcon vehicle details and general product knowledge.
32. Explain the candidate's understanding of Starship before starting a software coding problem.

Brain teasers and estimation questions — 1× each

1. Estimate how many gallons of water exist on Earth.
2. Put 1,000 one-dollar bills into ten envelopes so any whole-dollar amount from 1 through 1,000 can be formed by handing over whole envelopes.
3. A boat floats on a lake. An object is thrown overboard. What happens to the lake's water level?

These are low-frequency questions. They test calm assumptions and first-principles reasoning, but they should not take most of the preparation time.

Project deep dives, presentations, and behavioral questions

Project questions — at least 21 / 45

The wording changes, but the interview often comes back to these prompts:

1. What was the most difficult, complex, or technically impressive project?
2. What did the candidate personally own?
3. Why was a design choice made?
4. What trade-offs were rejected?
5. What failed, and how was it fixed?
6. How would the project be improved or rebuilt from scratch?
7. How did each component work inside the larger system?
8. What measurable result did the work produce?

Other reported prompts

Technical presentations — 11 / 45

The topic was usually a project, achievement, assessment solution, or case study. Reported lengths range from about 10–15 minutes to one hour, and several presentations were followed by panel questions.

One additional limited full-time record asks for a 10–15-page onsite deck but does not contain enough candidate context to enter the 11 / 45 count.

All 45 reports at a glance

Pick the right preparation track

Software, backend, full-stack, and embedded

Start with Starlink Beam Planner. Add one parsing task, one timestamped or stateful task, and one debugging task. Review data structures, complexity, memory, operating systems, and the language named in the job description. Practice one distributed system and one system connected to physical hardware.

Mechanical, manufacturing, materials, and propulsion

Refresh beams, stress and strain, pressure vessels, failure modes, fluids, thermal behavior, and material properties. Add the manufacturing topics closest to the role: drawings, GD&T, machining, welding, inspection, or design for manufacturing. Practice solving with units and assumptions on a blank sheet.

Hardware, avionics, controls, and verification

Review the electrical, software, and physical fundamentals required by the team. Practice open-ended energy, power, signal, control, and test questions. Be able to move from a block diagram to interfaces, failure modes, test evidence, and a safe state.

Senior and experienced candidates

Prepare for deeper questions about ownership, architecture, failure, influence, and results. Explain career moves and leadership decisions. Do not skip fundamentals: senior reports still include coding, first-principles questions, and detailed project defense.

Do not spend most of the preparation time memorizing one-off brain teasers. The repeat patterns are project depth, fundamentals, clear assumptions, and role-specific problem solving.