Portfolio projects that get interviews: rockets, ROS robots and CubeSats
Three project types that hardware recruiters recognize, how to scope each so you actually finish, and what to write up afterward.
A finished project with a test log beats an ambitious one that’s 70 percent done. That’s the one rule. Hardware teams hire people who close loops: design, build, test, fail, fix, document. Here are three project types that let you show that cycle, from a weekend scale to a multi-year one.
A certified high-power rocket. The NAR Level 1 procedure gives you an external standard: build your own rocket, fly it on an H or I motor, pass a safety inspection in front of a certification team, recover it in flyable condition. Scope it as a kit first. Then add one thing you designed yourself, such as a custom avionics bay that logs altitude and acceleration, and compare the flight data against your simulation. The comparison is the portfolio. “Predicted apogee X, measured Y, here’s why” is a conversation a propulsion or test engineer will happily have with you.
A ROS 2 robot that does one job. Work through the ROS 2 first-steps path in simulation, then move to a cheap wheeled base with a camera or lidar. Pick a single task: map a room and return to a charging spot, or follow a line in bad lighting. Record bag files of failures. A short video plus a write-up of the three worst bugs is stronger than a long feature list. For a space angle, run it on sand or gravel and write about wheel slip, which is a real rover problem.
A CubeSat team role. This is the big one, and it’s a team sport. NASA’s CubeSat Launch Initiative offers launches to small satellites from U.S. educational institutions and nonprofits; NASA says it has selected missions from 45 states, Washington, D.C., and Puerto Rico and launched about 160 CubeSats since the program began. If your school has a team, join it and own one subsystem end to end. If it doesn’t, a nearby university or nonprofit team may take volunteers. On your résumé, name the subsystem and the test you ran, not just the satellite.
The write-up matters as much as the build
Put each project on one page: the goal, a photo, the key numbers, what failed and what you changed. Link it from your résumé. Recruiters skim. Make the failure-and-fix story visible in the first screen.
Our view: pick the project closest to the job you want. Rockets for propulsion and test, robots for autonomy and controls, CubeSats for avionics, power and systems. Our roadmap maps each track to one.
What would change our advice: if postings start asking for simulation-only portfolios, the hardware rule would weaken. We haven’t seen it.
Not affiliated with NASA, SpaceX or any agency or company mentioned. Not investment advice. Disclaimer.