Unifying engineering after a merger.
Five teams, one delivery cadence. What I did when integrating engineering after an acquisition.
Post merger integration is the only time you get to redesign an engineering org from scratch with everyone's blessing. It is also the only time you can quietly make it worse forever. The window is short.
My first instinct used to be to standardize tooling. Same CI, same language, same cloud. I have learned that it is the wrong first move. People resist tools they did not choose, and you burn political capital you will need later.
What worked for me was to standardize the delivery cadence first. One shared planning ritual. One shared definition of shipped. One shared on call rotation. Tools follow naturally once the rhythm is shared, because the friction becomes obvious to the engineers themselves.
The full arc, including what we kept, what we killed, and the org chart we landed on, is on my main site.
Related notes
More from INSIGHTS / 2026
01 · Quality Systems · April 2026
Quality is a systems problem, not a testing problem.
Why throwing more QA at a broken pipeline never works, and what I do instead.
02 · AI & Delivery · April 2026
Letting AI write the tests humans never would.
How I embed AI generated regression coverage into a CI pipeline without the noise.
04 · AI & Delivery · May 2026
Predicting flaky tests with Random Forest.
How I used a Random Forest classifier on test metadata to quarantine flaky tests before they ever ran, and earned developer trust back.
05 · Leadership · May 2026
Unpopular opinion that might save your career.
If you are a Senior Manager, Director, or VP in Quality Engineering and you are not still hands-on and technical, you are already obsolete.
Get the next one