Will the Tesla-SpaceX merger cut jobs? Fix your CV

Will the Tesla-SpaceX merger actually cut jobs?

No cuts have been announced, and no merger has been agreed. On October 20, 2026, during SpaceX's third-quarter earnings call, Elon Musk said the boards of Tesla and SpaceX had each formed a special committee of independent directors to review a possible combination, created at the request of shareholders. He was blunt about the limits: the committees haven't reached agreement on the terms of any transaction, and treating a deal as a certainty, in his words, would be overstating it. Because he's CEO and the largest individual shareholder on both sides, he's a conflicted party and sits on neither committee — he described it as an odd kabuki dance he isn't allowed to join. Two groups of directors are talking. That's the whole story so far.

The approval math explains why this will take a while. A Tesla deal would need support from 50% of all outstanding shares — not just the shares actually voted — which Musk himself called quite a high hurdle. The SpaceX side is easier: after its June public offering, he holds more than 50% of the voting power there. Meanwhile, the proxy Tesla filed on October 19 sets a December 3 annual meeting with only three items on the ballot — director elections, say-on-pay and auditor ratification. There's no merger vote on it. Tesla ran a special-committee process once before, for the 2016 SolarCity acquisition, and that stretched across months of review and disclosure before anything closed. Nobody is reorganizing your team next Tuesday.

So the near-term risk to your job isn't a layoff notice — it's a reorganization you didn't plan for. Reporting lines get redrawn, open requisitions in overlapping teams quietly go on hold, and the internal postings worth having suddenly attract three times the usual number of applicants. Both companies were hiring hard through 2026: public job trackers counted roughly 2,400 open SpaceX roles in September, with engineering the single largest category, and Starbase has been in expansion mode all year. That's the realistic shape of the next six months — more competition for internal moves, not mass redundancies. Your CV needs to be current and credible now, because the week an announcement lands is the week every colleague you have starts writing theirs.

Which roles get consolidated first in a merger like this?

Duplicated corporate functions go first. In almost every merger, the earliest consolidation lands on the back office — finance, HR, IT, legal, procurement, internal communications, facilities — because that's where a combined company is suddenly running two of everything, and where the savings are easiest to point at on a slide. Frontline roles that physically build, test and fly the product are usually last to be touched, since cutting them destroys the thing the deal was supposed to be worth. Overhead integration typically plays out across roughly six to eighteen months, not six weeks. If you sit in a shared service function at either company, you have time to work with — but you're in the first tier, and you should plan like it.

This particular combination is unusual, though, and the oddity works in most employees' favor. A carmaker merging with a rocket company isn't two competitors with overlapping production lines; battery-pack assembly and Starship stacking don't substitute for each other. The genuine overlap sits in the areas Musk named as the synergy case: superintelligence software, chip design, Terafab, robotics, mass-to-orbit and connectivity. Teams working in those lanes are far more likely to get a merged roadmap, a new manager and a reshuffled priority list than a termination letter. That's still disruptive, and it still resets your internal story. A reassigned engineer with no written record of what they shipped is in a much weaker position than one who can hand over a one-page summary of outcomes.

Find your function in the table below and act at the matching speed. Shared-service staff should have a finished, externally readable CV in hand within a fortnight — not because a cut is coming, but because internal moves open first and close fast. Engineers and technicians have more runway, and they should spend it on evidence rather than anxiety: numbers, scope, systems, certifications, sign-offs. Senior managers sit in the awkward middle, since two companies rarely need two directors of the same thing. Whichever tier you're in, the move is identical at different urgencies: rebuild once, properly, then tailor per posting. If you're starting from a file you last opened years ago, a seven-day CV plan written for staff facing an acquisition is a faster route than patching.

How do you rewrite your CV for both automotive and aerospace hiring managers?

Write one neutral engineering spine, then fork it into two targeted versions — don't try to build a single document that pleases both audiences. An automotive hiring manager reads for rate, cost and quality systems; an aerospace one reads for traceability, qualification and flight heritage. The same project can be framed either way, but the vocabulary has to commit to one or the other. Keep your employment history, dates, education and tool list identical across both versions so nothing looks invented, then swap the summary, the skills block and the leading clause of each bullet. Two files, one source of truth. That's also how you stay honest about it: you're changing emphasis and terminology, not manufacturing experience you don't have.

The translation work is mostly nouns. On the automotive side, recruiters scan for IATF 16949, PPAP and APQP, DFMEA, takt time, OEE, line balancing, first-pass yield and cost per unit. On the aerospace side it's AS9100, NADCAP, GD&T, qualification and acceptance testing, vibration and thermal-vacuum campaigns, non-conformance and corrective action, configuration control, and export-control awareness. A Tesla engineer who ran a high-rate assembly line already has the aerospace story — high-rate production, build-to-print discipline, root-cause analysis under brutal schedule pressure — but it reads as unqualified until the words match the posting. Spell out each acronym once, then use the short form, so a human skim and a keyword parser both find what they're looking for.

Format decides whether any of that gets read at all. Keep it single column, use the plain section headings a parser expects — Experience, Education, Skills, Certifications — put dates on the same line as the employer, and drop the icon grid, the skills bar chart and the text boxes that look sharp in a design template and vanish entirely in extraction. Save as PDF unless the posting explicitly asks for Word. If you're an engineer and want the layout spelled out section by section, our guide to building an engineering CV that clears the first screen covers how to structure a stack section parsers can actually read. One base file, two variants, both machine-readable from the first line.

Which achievements should you quantify before an internal reshuffle?

Quantify the things only your current access can tell you: yield, scrap and rework rates, cycle time and takt, first-pass test turnaround, cost per unit, line uptime, launch or delivery cadence, headcount led, budget owned, and the before-and-after on anything you personally fixed. These are the numbers that make a CV survive a verification call, and they're also the first things to vanish when dashboards, ticket queues and shared drives get reassigned. Write them down this week, in a plain text file kept outside work systems: the baseline, the change, the timeframe, and your specific role in it. 'Improved yield' is a claim. 'Raised first-pass yield from X% to Y% in two quarters as owner of the fixture redesign' is evidence — fill in your own figures.

Do this carefully. Don't export data, screenshot dashboards or copy internal documents — at SpaceX in particular, a great deal of technical detail sits under export-control rules, and a CV bullet that leaks it is a far bigger problem than a thin CV. Percentages and ratios are your friends here: 'cut test turnaround 40%' says everything you need without disclosing absolute volumes or program specifics. Strip program code names and swap them for generic descriptors — 'a crewed vehicle program', 'a high-volume EV platform' — and keep supplier names out entirely. If you genuinely can't tell whether a number is publishable, describe the mechanism instead of the metric; what you changed and why it worked still reads as competence.

Then collect the softer evidence while people still remember the work. Ask two managers and one cross-functional partner for a written recommendation now, before anyone's reporting line changes, and save the message where a program lead thanked you for a save. Pull copies of your last performance review and any certifications stored on a company system, because access is the thing that goes first. If you've spent years inside a single employer, that paper trail is the only difference between a CV and a list of job titles. And if you've been writing for the EV market specifically, note that the roles reopening across batteries, charging and grid storage reward different keywords than the ones that landed interviews in 2023.

How do you test your CV against live job ads this week?

Pull three real postings you'd genuinely accept, then check your CV against them one at a time instead of guessing. The fastest version: upload your file to the free HRLens CV analysis and paste the text of a job description alongside it. You get an overall score out of 100 rated Weak, Decent, Strong or Excellent, five category scores — experience, tech stack, impact and ownership, clarity and structure, ATS compatibility — a visual layout analysis showing how the document actually parses, and a list of the skills that posting asks for which your CV never mentions. That missing-skills list is the gap to close first, before you touch anything cosmetic.

A few practical notes from people who do this daily. LinkedIn and Indeed block automated fetching, so paste the job text rather than the link. Every analysis also produces ATS-friendly rewritten versions of your CV in six templates that mirror the posting's keywords, which is usually quicker than rewriting bullets by hand at midnight. If you'd rather build from scratch, or from a file that hasn't been opened since 2019, the chat-based CV builder does it by conversation and exports to PDF and Word. The $3.99 full analysis adds the fix list, your blind spots, a candid read on why you might be rejected, an estimate of interviews per ten applications against the market, and a salary range.

Here's the part most people get wrong. The instinct, the week a merger headline lands, is volume: eighty applications in a fortnight, same PDF, same note. It doesn't work, and it works least well for engineers at these two companies, who tend to assume the logo does the explaining for them. It doesn't. Outside Hawthorne and Austin, a recruiter reads 'Manufacturing Engineer, Tesla' and still needs to be told what you owned, at what rate, with what result. Six properly tailored applications beat sixty generic ones, and tailoring takes about twenty minutes each once your base document is solid. Build that base now, while nothing has been decided and you're applying from a position of choice rather than urgency.

Frequently asked questions