.png?width=500&height=113&name=FORWARD%20Brand%20Board%20(72).png)
Scaling Engineering Culture Without Breaking It – Martín Sagastume
The engineering culture that makes a 10-person team exceptional rarely survives headcount growth. Martín Sagastume helps engineering leaders preserve what matte
Get Matched in 48 Hours →Martín Sagastume advises engineering leaders on preserving the culture, operating habits, and team cohesion that make engineering organizations productive as they scale from 10 to 50+ engineers. He works with companies in the 12-to-18-month window following a Series B or Series C raise, when headcount is growing fastest and the cultural fractures that will drive attrition three years later are forming silently.
How engineering culture breaks – and why it's invisible until it's expensive
Engineering culture does not break during a hiring surge. It breaks in the 6–12 months after a hiring surge, when the informal norms and operating habits that made a small team effective have been diluted by new members who never learned them and are not being deliberately taught. The earliest signal is not attrition – it is a qualitative shift in how engineers talk about the company in 1:1s, a decline in voluntary knowledge-sharing, and a gradual increase in coordination overhead that shows up as missed sprint commitments before it shows up as departures. By the time the attrition signal is visible, the cultural damage is 18 months old.
The operating habits that define engineering culture at scale
Engineering culture at scale is not a values statement on the wall. It is the set of operating habits that every engineer practices consistently: how architectural decisions are made and documented, how code review is conducted and what standards it enforces, how incidents are handled and learned from, how new engineers are onboarded and evaluated, and how disagreements between engineers are resolved. These habits were informal and self-reinforcing at 12 people. At 40 people they need to be explicitly designed, documented, and actively maintained – otherwise the team will develop conflicting micro-cultures across squads that generate coordination friction and attrition risk.
Why culture advisory is different from management consulting
Engineering culture advisory is not a survey-and-report engagement. It is a diagnostic and design process that produces specific behavioral changes in how the engineering team operates: a new code review standard, a redesigned incident retrospective process, a squad formation principle that prevents team identity fractures, a new engineer onboarding program that transmits culture deliberately rather than by osmosis. The advisor's role is to identify which specific operating habits are at risk, design the interventions that protect them at the new scale, and work with the engineering leadership team to implement them in a way the team will actually adopt.
A STAR case from the Forward Share Ventures network
Situation: Series B engineering org scaling from 18 to 45 engineers over 14 months. Senior engineers beginning to leave, citing "it doesn't feel the same anymore." New hires not ramping to expected velocity. On-call fatigue rising. Architecture debates becoming political with squad splits forming along new-hire vs. tenure lines.
Result: 12-week engagement identified 3 cultural fracture points (ownership ambiguity, architecture decision process, on-call equity). Recommendations implemented by engineering leadership – annualized attrition dropped from 22% to 9%, new hire ramp time improved by 35%, and the architecture debate process was restructured to resolve disagreements within one sprint rather than escalating indefinitely.
Forward Share Ventures expert operators are selected from a verified STAR Portfolio™ of documented outcomes.
"Engineering culture doesn't break when teams grow – it breaks when the operating habits that worked at 12 people aren't adapted for 40, and no one is paying attention to the adaptation process. The signal always comes in retention before it comes in metrics. By the time it shows up in metrics, you're repairing damage that took two years to accumulate."
– Martín Sagastume, Engineering Culture Expert Operator, Forward Share Ventures
Frequently asked questions
What makes engineering culture scale differently from just adding headcount?
Engineering culture is transmitted through operating habits, not through documentation or values statements. At 12 people, culture is transmitted by proximity – new engineers see how senior engineers operate, what standards they hold, how they handle disagreements, and what behaviors get praised and what get pushed back on. At 40 people, that transmission mechanism breaks down because new engineers are joining squads where they may never work directly with the people who defined the culture. Without deliberate design of how culture gets transmitted at scale – through explicit onboarding, structured code review, documented decision processes, and active modeling by engineering leaders – the culture fractures into whatever micro-norms emerge organically in each squad.
What are the early signs that engineering culture is breaking during growth?
Four early signs appear before attrition becomes visible: engineers in different squads starting to apply different standards to the same processes – code review, PR size, testing requirements; senior engineers becoming less likely to volunteer knowledge in all-hands or internal channels; a qualitative shift in 1:1 conversations from "here's what I'm excited about" to "here's what's frustrating me"; and architecture or technical decisions becoming political – where the argument is about who proposed the idea rather than the merits of the idea. These signals are soft and easy to dismiss individually. Together they indicate that the cultural infrastructure that made the team cohesive is no longer holding at the new scale.
How do I measure engineering culture health?
The most reliable engineering culture health metrics are: voluntary attrition rate by tenure band (the most predictive signal is attrition among engineers with 1–3 years of tenure, not new hires who haven't had time to decide, and not long-tenured engineers who have high exit costs); new hire ramp time to first meaningful contribution; participation rate in optional knowledge-sharing activities like internal tech talks or engineering all-hands; and the ratio of architectural decisions made by team consensus versus by escalation to VPE or CTO. These four metrics together give a more accurate picture of culture health than any engagement survey, because they measure behavior rather than sentiment.
What does an engineering culture advisory engagement involve?
The engagement has three phases. The diagnostic phase (weeks 1–4) involves structured interviews with 15–20% of the engineering team across seniority levels and tenure bands, observation of recurring engineering meetings, review of code review patterns and incident retrospective outputs, and analysis of attrition data and exit interview themes. The design phase (weeks 5–8) produces specific recommendations for each identified cultural fracture: a redesigned onboarding program, an updated code review standard, a new architecture decision process, or a squad formation principle. The implementation phase (weeks 9–12) works with engineering leadership to implement the highest-priority interventions and establish measurement for each one.
What is the relationship between engineering culture and retention?
Engineering culture is one of the three primary drivers of engineering retention alongside compensation and technical challenge. Of the three, culture is the most difficult to rebuild once it has degraded and the most powerful retention force once it is strong. Engineers with strong cultural alignment stay through compensation gaps, through difficult technical problems, and through management changes. Engineers who have lost cultural alignment leave at the next compensation offer regardless of how competitive their current package is. The investment in engineering culture is not a soft people investment – it is a direct ROI calculation on the cost of replacing engineers who leave because the culture they joined no longer exists.
Get an operator read on your situation
Twenty minutes with an expert operator who has been here before. No prep needed – bring the situation as it is. You will leave with a clear read on the gap and a concrete next step.
Get an operator read →No prep needed. 20 minutes. You'll leave with a clear read on the gap.
Find Your Expert in 48 Hours.
Founder-Vetted. Matched in 48 Hours. STAR-Verified.