Acqui-Hire Mechanics: Vest Acceleration, Retention Pools, and Integration Ladders

An acqui-hire (acquisition + hire) is a transaction where the buyer's primary motivation is the engineering team, not the product. The product often shuts down within 6–12 months; the engineers join the acquirer at a known per-head premium. The deal looks like an acquisition on paper, behaves like a hiring round in practice, and has its own specific mechanics that neither M&A nor talent acquisition playbooks fully cover. HR and engineering leaders running their first acqui-hire are well advised to study the playbook in advance.

What an acqui-hire actually is

Recurring features: small target (5–30 engineers); minimal IP value; the engineering team is named in the deal; product wind-down within 12 months; explicit integration plan with retention milestones; deal price quoted per engineer ($1–5M typical, higher for elite teams). The deal structure is usually a stock-and-cash asset purchase or stock-for-stock acquisition, plus a separate retention pool of equity granted to the joining engineers conditional on time.

The financials

The numbers vary enormously by deal context. A team where the founders own most of the equity sees a much different split than one with multiple VC rounds and stacked preferences. HR's job is to understand the structure well enough to predict how each joining engineer feels about it on day 1 — because most will know roughly what each other received.

Vesting treatment

The retention pool

The retention pool is what makes the acqui-hire actually retain people. It is a pool of acquirer equity (RSUs at public companies; options at private companies) granted to joining engineers at deal close, vesting over 4 years. Typical practice:

• Founders: largest share, often $2–10M+ per founder, 4-year vest with no cliff or 6-month cliff.
• Senior engineers (L5–L6): $500k–$2M, 4-year vest.
• Mid engineers (L4): $300k–$800k, 4-year vest.
• Junior engineers (L3): $100k–$300k, 4-year vest.
• Cliffs: standard 1-year cliff increasingly waived to avoid the day-365 cliff exit.

Levelling the incoming team

The single most consequential people decision in an acqui-hire is how to level the incoming team. Get this wrong and you destroy either your ladder or your retention. Practical guidance:

1. Calibrate against the acquirer's published rubric, not the startup's titles. A 'Senior Engineer' at a 10-person startup may map to L4 or L6 depending on actual scope.
2. Run a structured technical conversation with each engineer (90 minutes, two acquirer Staff+ engineers, the startup's CTO present). Not a re-interview, but a scope and capability conversation.
3. Map titles before close where possible. Negotiate as part of the deal. Post-close re-leveling is much harder.
4. If unsure, level slightly higher than your gut and pair with explicit 6-month and 12-month check-ins. Easier to defend than levelling down a former 'senior engineer' to mid.
5. Founders and CTOs: explicit individual conversations about title and scope. There is rarely a perfect map; honesty beats avoidance.

The first 90 days

• Day 1: every engineer has a named buddy from the acquirer team, a written 30/60/90-day plan, and clarity on their team and manager.
• Week 1: deal structure FAQ session (HR-led, optional, well-attended).
• Week 2: founders meet with senior acquirer engineering leadership in a structured 'what does this team know that we don't' session.
• Day 30: first formal check-in. Compensation questions surfaced and addressed.
• Day 60: each engineer ships at least one meaningful contribution to acquirer codebase. Symbolic and substantive.
• Day 90: structured retention conversation. Are they staying? What would change the answer?

The 12-month attrition cliff

Industry data is consistent across multiple academic studies and practitioner reports: 40–60% of acqui-hired engineers leave within 24 months. The 12-month cliff (when the first retention grant slice vests) is the most predictable departure point. Mitigations:

• Eliminate the 12-month cliff (vest monthly from day 30).
• Issue refresher grants at 18 months for top performers.
• Surface management conversations at 9 months — pre-empt the cliff.
• Promote first acqui-hired engineer to a visible role within 12 months. Demonstrates the path is real.

Anti-patterns

• 'Soft landing' framing — implies the team is being warehoused. Engineers leave fast.
• Shutting the product on day 1 without engineer consultation — destroys the team's pride and the founders' standing.
• Levelling founders below VP without a clear scope-equivalent role — they leave within months.
• Letting the deal team negotiate compensation without HR involvement — produces inconsistent offers across the team.
• Not budgeting integration time for the acquirer team — engineers join an org that has no time for them.

Monday-morning checklist

• Confirm vesting treatment is documented before close, in writing, per engineer.
• Confirm retention pool grants are sized against the acquirer's published bands.
• Confirm each engineer's level mapping is set before announcement.
• Confirm 30/60/90-day plans exist for every joining engineer.
• Schedule the 9-month and 12-month retention conversations now.

FAQ

References