Rebuild after layoffs in three moves: stabilize the survivors and critical systems first, then redesign the team shape around AI leverage instead of restoring the old org chart, and only then hire, fewer people, more senior, explicitly tooled. Layoffs are brutal; rebuilding the same structure that existed before wastes the one thing they offer, a clean redesign.
Phase 1: Stabilize (weeks 1-4)
- Map orphaned systems, everything the departed uniquely owned, and assign interim owners.
- Cut the roadmap honestly to what the remaining team can carry; overload now causes the second wave of departures.
- Talk to every survivor: what they're worried about, what they want to own next.
- Document tribal knowledge before it fades, an AI assistant transcribing walkthrough sessions makes this fast.
Phase 2: Redesign the shape
- Start from workload, not headcount: what does the roadmap actually require now that AI tooling handles a real share of routine code, tests and docs?
- Prefer small senior pods with full ownership over layered structures that need coordination roles.
- Budget for tooling as headcount: an AI-tooled senior engineer replaces more capacity than their salary suggests.
- Decide what stays permanently smaller, and say so, false promises of regrowth destroy credibility.
Phase 3: Rehire deliberately
- 1Write scorecards for the new roles, they will not match the old job descriptions.
- 2Hire senior first: people who ship with AI leverage and mentor as they go.
- 3Use embedded engineers to bridge urgent gaps while permanent hiring runs at its own pace.
- 4Screen for tool fluency: how candidates work with AI assistants is now a core interview signal.
- 5Protect the survivors' growth, fill some reopened scope by promoting from within, visibly.
