August 10, 2026

Scaling from 40 to 200 Engineers Without Losing the Plot

(Sample post drafted from my work notes - edit before publishing.)

Growing an engineering org from 40 to 200+ people is mostly a fight against entropy. Every new layer of coordination you add slows shipping; every layer you skip creates chaos. Here’s the structure that worked for us at Concierto.

Organize around value streams, not functions. We aligned each team to a product cluster - Migrate, Manage, Modernize, Insights, and Agentic AI - with end-to-end ownership from ideation to production. No handoffs to a separate QA org or an ops team that didn’t write the code. When a team owns the outcome, the outcome improves.

Make the roadmap a shared contract. Technology strategy and the quarterly roadmap are built in partnership with Product, Sales, and Customer Success, tied directly to revenue targets and client commitments. Engineers can see the line from their sprint to the business.

Treat onboarding as a product. We rebuilt hiring, onboarding, and retention deliberately - and cut attrition by 30% while halving time-to-productivity for new engineers. At 200 people, a mediocre onboarding experience compounds into months of lost output every quarter.

None of this is exotic. What’s hard is holding the line on ownership as you grow - resisting the instinct to add coordinating layers every time something goes wrong. Structure fixes what process patches.