All work

Case study · Pleo · 2021–2025

Scaling engineering from 60 to 200

In about eighteen months, Pleo grew from roughly 300 people to nearly 1,000, and engineering from about 60 to about 200. I led engineering experience, a small team with a programme manager, and we built the structure that let the org grow without coming apart.

Role
Senior Engineering Manager, leading engineering experience
Scope
All of engineering, planned with the CTO and a 20-person management team
Growth
~300 → ~1,000 people; ~60 → ~200 engineers
Also led
Product teams in Payments, Assurance, and Support & Compliance Tech
One dot, one engineer~60 when I joined~140 who joined over the next 18 months

01

The situation

Pleo had few managers, and they were stretched thin. And engineering was on its way from about 60 people to about 200.

More structure sounded like bloated middle management.

What changed my mind was seeing new roles differently.

New roles aren’t filler for gaps. They’re connectors: structure, information flow and coordination.

02

The approach

We mapped the whole engineer experience as a lifecycle, then brainstormed a multi-year list of initiatives and prioritised it with stakeholders across the company.

Each initiative ran as a working group that anyone in engineering could join. That kept ownership spread across the org instead of sitting with one team.

03

What we built

  • Thread 01

    Career framework

    A technical leadership path, so engineers can reach senior levels without becoming managers. Shaped by research and consultation, not by committee.

  • Thread 02

    Architecture group

    Technical leaders own the big calls: how many languages to support, API design, how to break up the monolith. Minutes go to everyone.

  • Thread 03

    Rituals & communication

    A culture book, an engineering All Hands with a Q&A that improved every round, and the channels to keep information moving.

  • Thread 04

    Hiring

    Interview training, consolidated hiring requests and standard interview sets for each role, rebuilt for consistency and fairness.

  • Thread 05

    Early careers

    An associate engineer programme that brought in 20+ entry-level engineers from a wide range of backgrounds, with its own hiring and onboarding.

  • Thread 06

    Growing people

    Peer mentorship across teams, T-group style training for new managers, and a calibrated review and promotion process.

04

What I’d do differently

  1. Start before the plan is perfect.If you try to hit perfection, you never get started. We shipped first versions and kept iterating.
  2. Budget for the rollout, not just the design.Rolling out and maintaining each initiative took far more work than designing it, much of it in one-to-one conversations.
  3. Name the glue work.The career framework missed work like interviewing, and left expectations for testing and incident management unclear.
  4. Practise leadership, don’t just define it.Technical leadership was much harder to put into practice than to write down.
  5. Invest in mentorship early.In fast growth, it’s what keeps people feeling connected and supported.

05

What it led to

“He had a widespread positive impact on the engineering community.”

Meri Williams · CTO, Pleo
Next · Lyft · 2015–2020A support platform that saved $50–75M a year