SpaceX · Primly Community

SpaceX coding interview online assessment format and difficulty: real data from January 2026

backend_bekah · 4 replies

Did the SpaceX online assessment in January while I was halfheartedly running a search. Leaving the data here because the info I found before taking it was mostly from 2023 and I didn't fully trust it.

Platform: HackerRank. Received the link by email after the recruiter screen.

Format: 2 questions, 90-minute timer that starts when you open it. You can use any language they support. I used Python.

Question 1: Graph traversal. Find the minimum cost path in a weighted graph with some constraints on which nodes can be revisited. Felt like a Dijkstra variant with an extra condition. Medium difficulty, maybe Medium-Hard. Solved it.

Question 2: String manipulation with a sliding window. More straightforward. Solved it clean.

Things I noticed: The problems are not identical to LeetCode but they rhyme. Specifically: graph traversal, dynamic programming, and sliding window have all come up in multiple reports I've seen. No ML, no SQL, no system design. Pure DSA. HackerRank's autocomplete is annoying. I'd recommend testing your language of choice in their environment before the real thing. I left with about 20 minutes to spare. 90 min is enough if you're comfortable with the patterns.

I moved to phone interview stage after, so passing the OA does not feel like a super narrow filter. It's more of a baseline DSA check. If you can do LC mediums consistently you're probably fine.

The actual hard filter is the onsite coding rounds, from what I can tell.

4 replies

marketer_mei

Do you get feedback if you fail the OA or just silence? I submitted mine 10 days ago and heard nothing.

content_cole

OA rejection is usually silence or a templated email after 2-3 weeks. Most companies at SpaceX's scale don't give substantive OA feedback. It's volume: they're screening hundreds of applicants per role.

frontend_fran

Does the OA vary by role or is it the same for all SWE levels? Asking because I'm applying for a frontend-specific role and I'm less worried about graphs than about getting blindsided by something niche.

quietquit_quincy

From what I've seen shared, the OA is pretty standardized across SWE regardless of specialization. They're checking general DSA, not React hooks. So yeah, graph problems whether you're a frontend person or not.