Hard to Hire, Hard to Learn, Hard to Break: A CTO’s Scala Case at Scala Days 2026
When engineers pitch Scala to business leadership, the conversation usually hits a wall. Leadership hears that Scala talent is expensive and the hiring pipeline is slow, so the safe-looking move is a language that is cheaper to staff. Gordon Cooke, co-founder of Scala Teams, built his Scala Days 2026 session in Berlin around that exact wall, and his argument is that the cheap option costs more than anyone in the meeting is counting.
Scala Days is full of brilliant deep dives into how the language works. Gordon's session zooms out to ask why a company should choose Scala at all, and it answers in the language a CFO uses. The talk is built to bridge the gap between engineering elegance and business reality.
Monday, October 12, 15:00 to 15:30 CEST, Maschinenhaus, Scala Days 2026 in Berlin. Gordon Cooke, co-founder of Scala Teams, presents "Hard to Hire, Hard to Learn, Hard to Break: A CTO's Scala Case." The session argues that optimizing for cheap headcount is a false economy, exposes the "shadow payroll" behind bloated polyglot teams, and gives CTOs the financial vocabulary to prove that a lean, elite Scala team is the most aggressive risk-mitigation strategy available to them.
Why Scala Looks Like a High-Risk Bet to Business Leadership
Gordon's starting point is a fair one. To a CTO or CFO, Scala looks risky for three reasons that show up in every budget conversation:
The talent is expensive. Senior Scala engineers carry a higher salary line than generalist developers.
The hiring pipeline is slow. Scala roles take longer to fill.
The learning curve looks like a wall. Leadership sees Scala as a language that takes real time to learn.
The session title names all three concerns head on. Gordon concedes the first two points and builds his case on the third: Scala is hard to break, and that quality matters most once you count the full cost. If you want more context on the hiring side, our breakdown of the Scala talent shortage covers why the pool is small.
Why Optimizing for Cheap Headcount Is a False Economy
The default corporate instinct is to reduce Scala's risk by optimizing for cheap headcount. In practice, that instinct often produces massive teams writing in verbose, weakly typed languages. Gordon calls that trade a false economy, because the low price per engineer hides what the larger team needs around it to keep running.
The session examines Total Cost of Ownership (TCO) in complex domains to make that hidden cost visible. A team's salary line is only one part of TCO, and the talk focuses on the parts that don't appear in the headcount comparison. Our earlier post on total cost of ownership for Scala development looks at TCO from the engagement side.
What the Shadow Payroll Includes
Gordon's name for the hidden cost is the "shadow payroll." The shadow payroll is the extra layer of people a bloated polyglot architecture needs just to stay upright:
Engineering managers
Manual QA testers
Incident responders
The session's word for what these roles do is babysitting. Gordon's point is that a cheap team plus its shadow payroll is the real number leadership should compare against a lean Scala team.
How Gordon Cooke Makes the Business Case for Scala
The business case for Scala in this session rests on two reframes that translate engineering strengths into terms leadership already tracks.
The Scala Compiler as an Automated Compliance Officer
Gordon frames the Scala compiler as an automated compliance officer. The framing puts a technical feature in terms that leadership already recognizes from the rest of the business.
Concise Scala Syntax as Architectural Leverage
The second reframe treats Scala's concise syntax as a tool for architectural leverage. Like the compliance officer framing, the leverage framing gives a CTO a way to describe Scala's value in a finance conversation instead of a code review.
Gordon pairs both reframes with a practical step: identifying the exact workloads where Scala wins. The session does not argue that every system belongs in Scala. It argues that, in complex domains, the math favors a lean team, and it shows attendees how to find the workloads where that holds.
What CTOs Will Take Away From Scala Days 2026
The session is fast-paced and practical. Attendees will leave with:
The financial vocabulary needed to talk about Scala with a CFO in the CFO's own terms
The organizational math required to compare a lean Scala team against a sprawling alternative
A way to expose the shadow payroll sitting inside a current or proposed team
A method for identifying the workloads where Scala wins
The end goal is a proof stakeholders will accept: that a lean, skilled Scala team is ultimately far more cost-effective than a sprawling one, and the most aggressive risk-mitigation strategy a CTO can deploy. Our post on why Scala fits business needs is a useful companion read before the session.
Who Should Attend Gordon Cooke's Scala Days 2026 Session
Gordon's talk is built for two groups. The first is engineers who believe in Scala and keep losing the budget conversation. The second is CTOs and engineering leaders who need to defend a Scala decision to a CFO or board. If you have ever been asked why your team cannot hire cheaper developers in a more common language, this session was written for that question.
Gordon Cooke is co-founder of Scala Teams and runs the Boston Scala Enthusiasts meetup. His session brings the business side of Scala to a conference program built mostly around the technical side.
Need to make the Scala case to your own leadership?
Whether you catch Gordon in Berlin or not, we can help you work through what a lean Scala team would cost for your workload. Talk to a Scala expert.
Frequently Asked Questions
When and where is Scala Days 2026?
Scala Days 2026 takes place in Berlin on October 12 and 13, 2026. Gordon Cooke, co-founder of Scala Teams, presents "Hard to Hire, Hard to Learn, Hard to Break: A CTO's Scala Case" on Monday, October 12, from 15:00-15:30 CEST in the Maschinenhaus.
What is the shadow payroll in software engineering?
The shadow payroll is the hidden layer of engineering managers, manual QA testers, and incident responders needed to babysit bloated polyglot architectures. Gordon Cooke uses the term in his Scala Days 2026 session to show what cheap headcount actually costs.
Why does Scala look like a high-risk bet to business leaders?
Scala looks risky to CTOs and CFOs because Scala talent is expensive, the hiring pipeline is slow, and the learning curve looks like a wall. Gordon Cooke's Scala Days 2026 session argues that answering those risks by optimizing for cheap headcount is a false economy.
Why is optimizing for cheap headcount a false economy?
Optimizing for cheap headcount often produces massive teams writing in verbose, weakly typed languages, and those teams need a shadow payroll of managers, testers, and incident responders to keep running. Gordon Cooke argues that the Total Cost of Ownership of that setup in complex domains is higher than the cost of a lean, elite Scala team.
What is the business case for Scala?
The business case for Scala, as Gordon Cooke presents it, is that a lean, elite Scala team is more cost-effective than a sprawling team once Total Cost of Ownership is counted. The case frames the Scala compiler as an automated compliance officer and Scala's concise syntax as a tool for architectural leverage.
