Embedded Logic Problems

Some SpaceX teams write code that talks to hardware, and their live rounds reflect that. Candidates for embedded roles report this kind of round, and so do software interns. If your loop is web or backend work, the take-home and the object-modeling problems are a better use of your time. Here you get a device and a prompt that leaves most of the rules open. Nobody fixes the input format for you, and what counts as a match is often your call.

Three problems from those rounds are worked below. Each one reads timed or ordered input, keeps a small state machine or lookup, and has to recover cleanly from a bad input.

Spend the first few minutes asking questions. Find out whether inputs are timestamps or gaps, and what a wrong input does to the state. Sketch the states on paper before you write any code. Follow-ups tend to change one rule, such as swapping one input device for another, and a clean state model makes that part of the round easier.

If your team is flight software, read Embedded C & Avionics next. It covers the timed C bug screen these rounds sit beside.

SpaceXPremium lesson · Coding round

The 3 SpaceX problems are below.

1. 1A Premium questionCoding · Medium · Frequently asked
2. 2A Premium questionCoding · Medium
3. 3A Premium questionCoding · Medium

Each with hints, the follow-up and a tested solution.

Get the SpaceX questions

$49 a year · all 100 companies · cancel anytime

From 20,000+ candidate reports, forum threads behind logins and write-ups in Chinese.

Read a free SpaceX lesson firstAlready a member? Sign in