Relativity Space hires PMs who can prove they think in systems, not just features.

In a Q3 debrief, a senior hiring manager pushed back on a candidate who listed three polished app redesigns, saying the work showed execution but no insight into how propulsion constraints shape product trade‑offs. The candidate was passed over despite strong communication, because the portfolio failed to signal the judgment Relativity values for its vertically integrated rocket‑software pipeline.

TL;DR

Relativity Space looks for PM portfolio projects that demonstrate systems thinking, hardware‑software trade‑off awareness, and a clear link to the company’s mission of 3D‑printed launch vehicles. A standout portfolio shows deep curiosity about manufacturing constraints, includes at least one end‑to‑end example that traces a requirement from material selection to launch readiness, and avoids generic tech‑company case studies.

Who This Is For

You are a product manager with 2‑5 years of experience, currently earning between $130,000 and $160,000 base, seeking to break into aerospace or deep‑tech product roles. You have built consumer or SaaS products but lack direct rocket‑related experience, and you need to translate your existing work into evidence that you can handle Relativity’s unique blend of hardware cycles, software updates, and regulatory scrutiny.

What kinds of portfolio projects does Relativity Space look for in PM candidates?

Relativity Space values projects that reveal how a candidate balances competing physical limits with product goals. In a recent debrief, a hiring manager noted that a candidate who described optimizing a satellite ground‑station software schedule while accounting for antenna thermal drift stood out because the story showed awareness of environmental factors that affect performance.

The problem isn't showcasing flashy UI — it's showing judgment about where hardware constraints force trade‑offs in user experience. A strong project will name a specific constraint (e.g., material fatigue, launch vibration, regulatory limit) and explain how the PM adjusted scope, timeline, or features to stay within that bound.

How should I structure a portfolio project to show systems thinking for Relativity Space?

Begin with the system boundary, then drill into subsystems, and finish with the feedback loop that informs next cycles. One candidate presented a project on redesigning a drone delivery routing algorithm; they opened by mapping the entire logistics network — weather patterns, battery degradation curves, airspace regulations — before detailing how they adjusted the algorithm’s cost function to prioritize routes with lower icing risk.

The hiring manager later said the candidate’s ability to zoom out and back in signaled the kind of systems thinking needed to coordinate Relativity’s printer farm, avionics team, and launch operations. Avoid starting with a solution; start with the problem space and the interdependencies that define it.

What technical depth do I need to demonstrate in a Relativity Space PM portfolio?

You do not need to be able to weld a nozzle, but you must speak the language of the engineers who do. In a debrief for a senior PM role, a hiring manager rejected a candidate who said they “worked closely with engineers” without being able to explain why a change in injector plate thickness would affect combustion stability.

The candidate was asked to sketch a simple pressure‑vs‑thickness curve on a whiteboard; hesitation cost them the interview. A good rule is to include at least one technical detail that would make an engineer nod — such as mentioning the specific alloy (e.g., Inconel 718) used in a part, the tolerance stack‑up you considered, or the software interface (e.g., CAN bus message ID) you helped define. Depth signals respect for the team’s expertise and reduces the perceived onboarding risk.

How many portfolio projects should I include, and what length is appropriate?

Relativity’s recruiters typically allocate six to eight minutes per candidate’s portfolio during the initial screen. In a observed debrief, a recruiter mentioned they stopped reading after the fourth slide of a ten‑slide deck because the candidate had not yet connected any work to aerospace constraints.

Aim for two to three projects, each presented in three to five slides or a one‑page written summary that fits within a four‑minute read. Each piece should contain a clear constraint, your role, the trade‑off you navigated, and the outcome measured in a metric that matters to Relativity (e.g., weight reduction, launch schedule margin, software defect rate). More projects dilute signal; fewer than two make it hard to judge consistency.

How do I tie my portfolio projects to Relativity Space’s mission and current initiatives?

Show that you have done homework on the company’s roadmap and can map your experience to its upcoming milestones. In a hiring committee discussion, a PM lead praised a candidate who linked their work on reducing battery swap time for an electric scooter fleet to Relativity’s goal of shortening turnaround between launches via rapid‑swap avionics modules.

The candidate cited Relativity’s public test‑flight schedule and noted how a 15‑minute improvement in ground operations could increase annual launch capacity by roughly two flights. The problem isn't generic enthusiasm for space — it's demonstrating concrete familiarity with Relativity’s specific technical challenges and expressing how your background moves those needles forward.

Preparation Checklist

  • Identify one hardware constraint relevant to Relativity (e.g., printer layer adhesion, vibration modes, launch window) and build a project around navigating it
  • Draft a three‑slide narrative: constraint → your trade‑off decision → measurable outcome tied to launch reliability or cost
  • Practice explaining the technical detail in under 90 seconds to an engineer friend
  • Align at least one project with a recent Relativity press release or test‑flight article (e.g., Terran 1 re‑flight, engine hot‑fire)
  • Work through a structured preparation system (the PM Interview Playbook covers aerospace‑focused PM frameworks with real debrief examples)
  • Review your portfolio with a hiring manager from aerospace or defense to get feedback on signal clarity
  • Time each project read‑through; aim for under four minutes per piece

Mistakes to Avoid

BAD: Including a consumer app redesign with no mention of how battery life, signal latency, or regulatory approval affected feature choices.

GOOD: Describing how you postponed a push‑notification feature because the cellular modem’s power budget would exceed the satellite link’s allowance during eclipse periods, then proposing a batched sync scheme that saved 12% energy.

BAD: Listing “collaborated with cross‑functional teams” without specifying what you learned about their constraints or how you adjusted your plan.

GOOD: Explaining that after learning the avionics team could not tolerate more than 5 ms jitter on the CAN bus, you simplified the UI animation loop to guarantee deterministic timing, which reduced reported glitches by 30% in beta testing.

BAD: Submitting a five‑page PDF that reads like a generic product case study from a tech company, with no reference to aerospace‑specific metrics.

GOOD: Submitting a two‑page brief that highlights a 0.3 kg weight saving achieved by selecting a titanium‑alloy bracket over aluminum, directly linking the saving to increased payload capacity for Relativity’s next launch vehicle.

FAQ

What if I don’t have any aerospace experience?

Focus on transferable judgment: show how you have handled physical or regulatory limits in any domain (e.g., medical device sterilization cycles, automotive crash‑safety standards). Relativity values the ability to learn quickly; a concrete example of mastering a new technical constraint signals you can climb their learning curve.

How technical should the portfolio be for a PM role?

Technical enough to earn respect from engineers — mention specific materials, tolerances, or interfaces — but stop at depth that would require you to do the work yourself. A hiring manager once said they trusted a PM who could sketch a stress‑strain curve for a printed part but did not expect them to run the simulation.

Should I include code or CAD files in my portfolio?

Only if they are central to the story and you can explain them in under a minute. A recruiter recalled a candidate who attached a Python script for orbital decay modeling; the script itself was ignored, but the candidate’s two‑sentence explanation of how orbital decay affected launch window planning earned positive notes. Keep artifacts lightweight and commentary heavy.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.