HubSpot Cut 'Layers and Spans.' Pitch Its Managers Head of Eng, Not EM
HubSpot's 660-role cut targeted management layers, not weak performers. How to find its senior EMs and directors and pitch them a head of engineering role.
On October 6, 2026, HubSpot said it would cut about 660 roles, roughly 7% of the company, and that "layers and spans" was one of six criteria every role was judged against. If you're a founder hiring a first engineering manager or a head of engineering, that phrase is the most useful line in the memo. It means some of the people leaving lost a box on an org chart. Their performance reviews weren't the reason.
The catch is that most of them won't want the job you probably wrote. Here's who is in the pool, why the usual first-EM pitch reads as a step down to them, and what to offer instead.
What did HubSpot actually cut?
HubSpot is eliminating nearly 660 roles under a restructuring plan its board approved on October 1, and it expects the eliminations to be substantially complete by the end of March 2027. The aim is a flatter structure, with Hub-based product teams replaced by teams organized around customer outcomes.
CEO Yamini Rangan's memo scored every role on six criteria:
- Strategic need
- Layers and spans
- Revenue capacity
- Capability
- Capacity
- Leadership
"Layers and spans" is an org-design term with two halves. Layers are the number of management levels between the CEO and the people doing the work. Spans are how many direct reports each manager has. The memo boiled it down to one question: "Do we have the right number of layers and spans to move quickly?"
A few other facts shape the hiring picture:
- Cost: $65 million to $75 million in restructuring charges, mostly in the fourth quarter, disclosed in the 8-K signed by CFO Kate Bueker.
- AI framing: Rangan said the decision "is not driven by AI-related efficiencies."
- Scale: 660 roles at 7% implies a company of roughly 9,400 people.
Why doesn't a "layers and spans" exit say anything about performance?
The criterion scores the seat, not the person sitting in it. When a company reorganizes from product lines to customer outcomes, the management roles that were repeated inside every product line all become redundant at once, whoever held them.
That's the mechanism here. Under a Hub-based structure, management roles repeat in every Hub. Rebuild around outcomes and many of those parallel seats collapse into fewer, wider ones. A strong director whose Hub merged into someone else's outcome team can lose the seat for purely structural reasons.
HubSpot's own history backs this up. This is only its second workforce reduction, and the first one, in January 2023, was the same size: about 7%, or roughly 500 people. In 2023 HubSpot acknowledged that staffing had grown faster than revenue in several groups. That was a correction for over-hiring. The 2026 memo describes disciplined hiring and a structural redesign instead. Those are different stories, and the second one is much better news for anyone hiring the people who leave.
One caution. HubSpot hasn't published a breakdown of the cuts by title or function. "Targeted management layers" is accurate, but "mostly managers" is a guess. Capability and leadership were also on the list, so some exits are about the person. You still run references. Just don't open the conversation assuming the cut was a verdict.
Who is in the reachable HubSpot manager pool?
In Refolk's index of professional profiles, 128 people have HubSpot in their headline and hold an Engineering Manager, Senior EM, Director of Engineering, Group Product Manager or Product Manager title. In a 25-profile sample, 21 (84%) still work at HubSpot. The top regions are Greater Boston, New York and Dublin.
Treat that number as the reachable pool, not a list of people who were cut. It's the set of managers you could reasonably talk to through the severance window, whether they're leaving or just reconsidering after watching their org get flattened.
The sample's title mix is the finding that matters most:
- Senior Engineering Managers: 6
- Directors of Engineering: 5
- Engineering Managers: 2
- Product Managers: 7
- Group Product Managers: 4
That skew makes sense. A delayering hits the middle layers, and the middle layers are where managers of managers sit. If you search for "engineering manager, HubSpot" and stop there, you miss most of the people who matter.
| Metric | Figure | Source |
|---|---|---|
| HubSpot-headline EM, Director and PM profiles | 128 | Refolk's index |
| Share of sample currently at HubSpot | 84% (21 of 25) | Derived |
| Senior EM + Director vs plain EM (sample) | 11 vs 2, about 5.5:1 | Derived |
| US EM + Senior EM profiles | 52,679 | Refolk's index |
| Ireland EM + Senior EM profiles | 1,078 | Refolk's index |
| Implied HubSpot headcount | about 9,400 | 660 ÷ 0.07 |
Matching on titles across levels is where keyword search falls short. "Senior Engineering Manager," "Director, Engineering" and "Head of Platform" are all the same hire for a startup, but they're three different Boolean strings. Refolk closes that gap. You describe the person once in plain English ("engineering leaders at HubSpot who have managed managers") and get one ranked list.
Should you pitch them a first-EM job at a startup?
Usually not as it's written. A Senior EM or Director of Engineering with managers reporting to them will read "Engineering Manager, 4 reports" as a demotion. Pitch head of engineering with an explicit hands-on period instead.
Hiring externally for the role is the right instinct. In his LeadDev piece on first-EM traps, Jason Wong recommends hiring externally for your first manager. He also warns that player-coach setups (where the manager still writes production code) work only if your team stays small, under five engineers. Lena Reinhard's guidance on when to add a first manager at an early-stage startup is worth reading before you write the role.
Use team size to decide which title is honest:
- Under five engineers, staying small: this is a player-coach role. Call it founding engineering manager, put the coding expectation in writing, and expect a former director to turn it down. That's fine. Look for the Senior EMs who miss shipping code.
- Five or more engineers, hiring: this is head of engineering. Promise a hands-on start, then a path to hiring managers under them. This is the role the 5.5:1 senior skew fits best.
- Never inflate to VP if there is nothing to be VP of yet. People who just watched a company remove layers will notice an invented one.
Don't skip the product side. The sample had 11 PMs and GPMs out of 25. If your founder is still acting as the product manager, a HubSpot GPM could be a better first leadership hire than another engineer.
How do 20 to 30 weeks of severance change the timing?
HubSpot's 2026 severance removes any urgency on the candidate's side. Leavers get 20 weeks of base pay plus a week per year of service, capped at 30 weeks, along with five months of healthcare and career support. Nobody has to say yes quickly.
The SEC filing says substantially all related cash payments should be made by June 30, 2027. A manager notified in early 2027 can have five to seven months of income secured. The founder who wins is the one with the best role, not the first message in the inbox.
For the wave-by-wave timing (severance checkpoints running roughly from February 23 to May 4, 2027, with Dublin as a second wave), see HubSpot's 20-Week Severance Kills the 5-Day Blitz. This piece won't repeat it. The practical takeaway is simple: build the shortlist now, start conversations about scope early, and give candidates a start date that lets them use their severance instead of giving it up.
What should the pitch to a laid-off HubSpot manager actually say?
Sell what HubSpot just took away from them: fewer layers, real decision rights and ownership of an outcome, described in HubSpot's own language. They've just been through a reorganization built around a flatter structure and customer outcomes. Your company can offer both in practice, starting on day one.
HubSpot removed layers to move faster. Your pitch should sell the absence of them, starting with the reporting line.
Build the message around five points:
- Name the reporting line. "You'd report to me. There's no layer between you and the decision." For someone who was just cut over layers, that one sentence does a lot of work.
- Offer an outcome, not a team. HubSpot is moving to teams organized around customer outcomes. Name the outcome they'd own, such as activation, reliability or time to value.
- Offer a flexible start date. Tell them up front that a start after their severance window is fine. It shows you understand their position and it costs you little.
- Make the equity case directly. HubSpot's stock was down more than 43% for the year as of October 6. Unvested RSUs anchor people less than usual right now, so startup equity compares better than it did a year ago.
- Treat the cut as structural, out loud. "Your role was cut in a layers-and-spans redesign" is factual and respectful. Leave performance out of the first message entirely.
What to avoid:
- Opening with "sorry to hear about the layoff." It centers the loss instead of the opportunity.
- A job description written for a line EM. Senior people screen on scope before they read compensation.
- Pushing for a start date in weeks. With severance in hand, pressure reads as desperation.
Why is Dublin a separate market for these managers?
Dublin is a thin market for engineering managers, so HubSpot exits there will shift local supply more than they would in Boston. In Refolk's index, Ireland has 1,078 EM and Senior EM profiles against 52,679 in the US.
HubSpot hasn't said where the 660 roles fall, but Dublin is its EMEA base and one of the top three regions in the HubSpot manager sample. Even a few dozen engineering managers leaving there would be a noticeable share of everyone with that title in the country.
Two things follow.
- They'll appear later. Under Irish law, consultation must start 30 days before the first notice, and no dismissal can take effect until 30 days after the minister is notified. Dublin managers will reach the market after their US colleagues.
- The competition is concentrated. The top Irish employers of EMs in Refolk's index include CrowdStrike, LearnUpon, Workhuman, Stripe and Databricks. Each of them will notice the same supply shift, and most can offer a local office you can't.
If you're hiring remote-first or have an EMEA presence, start mapping the Dublin pool now and plan to reach out after the consultation period.
FAQ
When will HubSpot's laid-off engineering managers be available?
HubSpot says role eliminations should be substantially complete by the end of March 2027, subject to local law and consultation requirements. US leavers come first. Dublin leavers will likely follow because Irish law requires a 30-day consultation before the first notice and another 30 days after the minister is notified before any dismissal takes effect. Severance payments should be substantially done by June 30, 2027.
How much severance are HubSpot employees getting in 2026?
The 2026 package is 20 weeks of base pay plus one week per year of service, capped at 30 weeks, along with five months of healthcare and career support. In practice, most leavers can take their time choosing a next role, so founders compete on scope and flexibility, not speed.
Is it a red flag to hire a manager who was cut in a layoff?
Not by itself. HubSpot scored roles on structural criteria, including "layers and spans," and Yamini Rangan said the decision was not driven by AI-related efficiencies. But capability and leadership were also criteria, and HubSpot has published no breakdown by title. Run normal reference checks and judge the person, not the layoff.
Should a startup's first engineering manager be hired externally?
Often, yes. Jason Wong at LeadDev recommends hiring externally for the first manager, and notes that player-coach setups work only while the team stays under five engineers. If you're past that size and growing, hire a head of engineering with a hands-on period, which is the role HubSpot's senior-heavy manager pool fits best.
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.