An acquisition lives or dies on the unglamorous organizational plumbing-- brand identity, staffing, tooling, shipping cadence, culture-- not the press release. I learned this managing attrition through the acquisition of a small startup called Beeswax, first as an Engineering Manager, later as a Director of Engineering. Three things made the difference, and none of them are retention bonuses: mapping ownership so gaps don’t hide, treating 1:1s as the highest-leverage thing you do in year one, and defining a vision honest enough to survive being wrong. I’ll touch on hiring and firing-- they matter-- but attrition is where acquisitions are actually won or lost.
This isn’t a niche problem. M&A volume cratered under macro pressure in 2022 and 2023, but ad-tech had already bucked the trend by 2024-- 73% YoY growth in ad-tech M&A alone-- and by 2025 overall deal value was back above $5 trillion, ahead of the last two decades’ average. If you’re the acquirer trying to protect the team you just bought, or the team on the other side of that deal, this is worth reading closely-- more of you are going to be living this than at any point in the last five years.
The story starts in 2021. The founders stayed on for a year, but in truth, most of the acquisition work happened after they left.
<aside> 🏗️
The shape of this post. An acquisition lives or dies on the unglamorous plumbing-- not the press release.
Attrition’s Long Tail
Every team I’ve run falls into one of four states: Firefighting, Treading Water, Recovering (paying down technical debt), or Driving Innovation. I’ve taken teams through all four, and leadership matters most in the first three-- a team that’s merely fighting fires or treading water is where an acquisition either stabilizes or quietly unravels. Before you diagnose which state your team is in, though, figure out whether the problem is your team or the org around it. As an engineering manager, there’s little you can do to fix the org itself; as a director, your leverage grows, and your strongest tactic becomes managing up without overstepping. People like to say impact can come from anywhere regardless of title-- true in small orgs, generally false in big ones.
Two other processes matter too: hiring (generally to meet new business objectives) and firing (a deduplication of roles and talent-- note that the mothership often chooses its own).
Botching the decision making in the first year of an acquisition will lead to a series of cascading problems with each cycle bringing an escalating reverberation of eventual failure. Regardless of the state of hiring and firing, attrition is a part of every acquisition (exceptions may be acqui-hires). Retention bonuses are only so effective-- if you want to keep your talent, keeping the founders on for as long as possible is a much stronger lever. The question of what the founders will do or how long they might stay was a consistent one. Salary was secondary and only became a larger concern after the founders departed.
Most of my early experience was centered around refueling the fire that was nearly extinguished by the journey to acquisition. In the early stages, my team would be considered small compared to the behemoth of an org I would lead a few years later-- roughly 4 employees and 4 contractors. I still believe 8 engineers is a realistic team size for one leader to run well.
With the advent of A.I., executives will push for larger teams anyway. This movement will largely fail-- not because a team that size can’t function, but because there aren’t enough leaders skilled enough to handle 15+ engineers moving at the speed of Claude.
For additional context, the baseline for attrition in tech has been historically high. The median job tenure for a startup employee receiving equity compensation is a mere 2.2 years, the average tenure at Big Tech is a little over a year. Oddly enough, employees tend to yield the best ROI between years 2 and 4 of their tenure. If leaders are frustrated with delivery-- retention is one of the best places to look.
While 75% of employees depart in the first 3 years, management tells an even more asymmetrical tale-- 40% of managers are lost in the first 24 months. In a hostile takeover, this rate surges past 50%.
100% of the direct reports on my initial team stayed for 2+ years-- some would go on to stay 5+ years. I managed to keep the majority of our highest achieving contractors as well. Here are a few things that made the difference:
First: ownership.
Map out individual team member’s AOR.
Find the gaps, communicate those gaps with your team and your manager. If the gap is high value, assign that space to your highest available talent and determine the risk if this gap goes unfulfilled.
Acquisitions are the end goal for a lot of organizations-- the successful exit. For the people inside, though, it’s just as often a beginning: a career at a startup and a career at a large parent company look very different, and this is where engineering leadership can make a difference. Your AOR document doubles as a first resource for that conversation.