Case Study: Scaling a Sydney Fintech Engineering Team from 5 to 25

The setup

A Sydney-based fintech (Series A, $14m raised) needed to scale from 5 engineers to 25 in 14 months while taking a regulated lending product from beta to production. They needed to:

• Hire 20 net new engineers across backend, frontend, platform and data
• Stand up SRE and on-call discipline
• Maintain delivery velocity through the growth
• Keep the burn defensible to the board

We partnered on the hiring operating system, channel mix and interview loop redesign. This case study covers what worked, what didn't, and what the numbers looked like.

The numbers

Headcount grew steadily after a slow first quarter. The slow start was deliberate — the first hire was a tech lead, not a senior engineer.

Hiring channels: what actually worked

Referrals dominated once the first 8 engineers were on board — each new hire opened 2–3 strong introductions. Targeted LinkedIn outreach by engineers (not the recruiter) outperformed recruiter-led outreach by ~3×.

The interview loop redesign

The original 6-stage loop ran ~4 weeks and was leaking senior candidates. We compressed to 4 stages over 14 days:

1. Recruiter screen (20 min) — sell, qualify, schedule
2. Hiring manager (45 min) — trajectory, motivation, mutual fit
3. Practical (90 min) — live coding or system design, not both
4. Bar-raiser + cofounder + verbal offer (75 min)

Verbal offer at the end of stage 4 changed everything. Counter-offer loss dropped from 41% to 12%.

The compensation philosophy

Comp strategy was simple: median of the Sydney range plus meaningful equity, paid super at 13%, $4k learning budget. Indicative bands at the time:

• Mid engineer: $145k + 0.05% equity
• Senior engineer: $190k + 0.12% equity
• Staff engineer: $245k + 0.30% equity
• Engineering manager: $225k + 0.20% equity
• Tech lead (early hire): $215k + 0.45% equity

Equity grants used a 4-year vest, 1-year cliff, with double-trigger acceleration on change-of-control. Notably no sign-on bonuses — every engineer who declined did so on equity terms, not cash.

The structure that held up

At headcount 12, the single-team model collapsed into meeting-driven mush. The fix was two pods:

• Pod A (Lending product): 5 engineers + 1 EM
• Pod B (Platform + payments): 5 engineers + 1 EM
• Shared platform / SRE: 2 engineers
• Tech lead and CTO: cross-cutting

Each pod ran their own standup, retro and roadmap. Cross-pod coordination was a 30-minute weekly tech lead sync — not a 60-min all-hands.

This held through to headcount 25, at which point the pods split again into four (3 product pods + 1 platform pod of 4).

The biggest mistake

Hiring senior engineers before hiring the tech lead. For the first 8 weeks, the team brought on three strong senior engineers without an anchor — each pulled the architecture in a different direction. Rework cost ~6 weeks of delivery before a tech lead landed and re-aligned the direction.

The lesson: hire your anchor first, then build around them.

Retention through the scale

Despite hiring 20 new engineers in 14 months, voluntary attrition was 4% — well below market. Three things made the difference:

1. A real onboarding plan, not a Notion page. 4 weeks structured, with a project shipped to production by week 4.
2. Manager 1:1s weekly, no exceptions. EMs were measured on this.
3. Quarterly comp benchmarking, with adjustments made before resignation.

What we'd do differently

• Hire a Talent Lead in-house at headcount 12, not 18. The first six months were under-resourced on coordination.
• Build the EM bench earlier. Promoting the second EM internally took 3 months too long; the second pod ran without dedicated leadership for that window.
• Move on-call rotation in earlier. Production incidents at headcount 16 caught a team that hadn't built the muscle.

The takeaways

For any Series A–B tech company planning a similar scale:

1. Hire your anchor first (tech lead or staff engineer), then build around them
2. Compress the loop early — 4 stages over 14 days
3. Verbal offers at final interview kill counter-offer loss
4. Split teams at 12, not 16 — meetings will tell you when
5. Don't ship hiring strategy without a single throat to choke — one Talent Lead, one EM, one recruiter as the candidate quarterback
6. Re-benchmark every quarter and adjust before resignation

Closing thought

Scaling fast doesn't require heroics — it requires a hiring operating system. The fintechs that nail this are the ones who treat hiring as the same discipline as shipping product: clear specs, fast cycles, measured outcomes.