There’s a pattern that shows up regularly across growth-stage space companies, and it rarely gets diagnosed correctly.
A company hires a strong systems engineer. The person is exactly what the team needs – technically sharp, experienced with the relevant subsystems, capable of working autonomously in a fast-moving environment. Six months in, the company has doubled its engineering headcount. Twelve months in, the engineer is spending most of their time in program reviews, managing subcontractors, and writing documentation. The spacecraft design work that drew them to the role has been handed to the junior engineers they helped bring on board.
By month 14, they’re interviewing elsewhere. By month 18, they’re gone.
The company restarts the search – for the same role, at a higher salary, in a market that’s gotten more competitive since the last time they hired.
The Role Evolved. The Conversation Didn’t
This isn’t a story about bad hires. The engineer was the right person for the role as it existed when they joined. The problem is that in a scaling space company, roles don’t stay the same for long. A 30-person company that grows to 80 in 18 months has fundamentally different needs at every level. The systems engineer who was hands-on-keyboard designing architecture is now, whether anyone planned it or not, functioning as a technical program manager.
That evolution is natural and often necessary. Someone has to manage the complexity that comes with growth. But when the transition happens by default rather than by design – when the engineer realizes they’ve drifted into a different job without anyone acknowledging it – the result is disengagement followed by departure.
The cost in the space sector is higher than in most industries. Replacing a mid-to-senior engineer takes three to six months when you factor in the search, the clearance timeline if applicable, and the onboarding period before the new hire is contributing at full capacity. The institutional knowledge that walks out the door – understanding of the mission architecture, relationships with the team, context on design decisions that were never fully documented – doesn’t come back.
Why This Happens More in Space
Every growing company deals with role evolution. What makes it more acute in the space sector is the nature of the people and the work.
Engineers who choose space tend to be mission-driven. They joined because they want to build spacecraft, design propulsion systems, write flight software, or solve GNC problems. The technical work isn’t just their job – it’s their identity. When that work gets replaced by management overhead, the loss feels personal in a way it might not for an engineer in a less mission-connected industry.
The technical complexity of space programs also makes the transition harder to manage gracefully. In a SaaS company, you can promote a senior engineer to engineering manager and their direct reports can largely self-direct their technical work. In a space company, the technical decisions are higher-stakes, the regulatory requirements are more demanding, and the consequences of getting something wrong are more severe. The temptation is always to keep the most experienced person close to the decisions – which means close to the meetings, the reviews, and the vendor calls, and further from the engineering.
And because the candidate pool for experienced space engineers is small, the cost of losing someone and replacing them is disproportionately high compared to other sectors.
What the Companies That Retain Do Differently
The space companies with the strongest retention – the ones where senior engineers stay for three, four, five years – tend to do a few things that others don’t.
They have the 12-month conversation at the point of hire.
During the interview process, they’re transparent about what the role looks like today and what it’s likely to look like in a year. They describe the growth trajectory honestly: “Right now, you’ll be hands-on designing the thermal subsystem. In 12 months, if we’ve grown the way we plan to, you’ll probably be leading a team of three and spending more time on program integration. Is that a path you want?” The engineer who says yes to that question with full information is far more likely to stay than the one who discovers it by surprise.
They build technical tracks alongside management tracks.
The assumption that the only way to advance as an engineer is to manage people is what causes the most preventable attrition. Companies that create principal engineer, technical fellow, or chief engineer roles – positions with seniority, compensation, and influence that don’t require managing direct reports – give their best technical people a reason to stay. The GNC engineer who wants to spend the next five years solving increasingly complex navigation problems shouldn’t have to become a people manager to get promoted.
They audit role drift proactively.
Every six months, someone – a manager, a founder, an HR lead – should be asking: is this person still doing the job they were hired for? If the answer is no, is the new version of the role something they want? If it’s not, what can be restructured before they start looking elsewhere? This conversation is cheap. The replacement search is not.
They compensate for scope changes.
When a role expands significantly – when the engineer who was hired as an individual contributor is now effectively managing a program – the compensation should reflect that. Companies that let scope creep happen without adjusting the title or pay are telling the engineer that their expanded contribution isn’t valued. That message gets received clearly, even if it’s never said out loud.
The Takeaway
Losing a strong engineer after 12-18 months is one of the most expensive and preventable problems in the space sector. It’s rarely caused by compensation alone, and it’s rarely caused by the market offering something better. It’s caused by a gap between what the person signed up for and what the role became.
The companies that close that gap – with honest conversations, parallel career tracks, and proactive check-ins – keep their best people. The ones that let roles evolve by default and hope the engineer will adapt keep restarting searches they shouldn’t have to run.