All case studies

EF Education First · 2023 – present

The platform behind ef.com

Turning slow, risky releases into a daily routine across 60+ markets.

The ef.com homepage: “hello!” above a row of travel and study photographs.

45 → 15minutes per CI run for the 17 frontends behind ef.com, with coverage up from ~30% to 85%.

The project

EF’s global homepage and the consumer brand surfaces around it, released daily to 60+ markets from a shared delivery platform.

Role
Senior Frontend Engineer · EF Education First
Stack
  • Next.js
  • TypeScript
  • GitHub Actions
  • Jest
  • React Testing Library

The problem

Seventeen production frontends shared one CI/CD pipeline that took 45 minutes, and test coverage sat around 30%. Slow, risky releases across 60+ markets.

What I did

  • Took ownership of the shared CI/CD platform behind all seventeen frontends.
  • Parallelised builds and removed repeated package installs, bringing a pipeline run from 45 minutes to 15.
  • Introduced structured testing with Jest and React Testing Library and made it part of every pull request.
  • Negotiated API contracts with backend teams for the multi-region applications, and mentored engineers through review.

What changed

Daily multi-region releases became routine: pipelines run in a third of the time, coverage rose to 85%, and production incidents fell by about 40%.

CI pipeline time−67%

Rebuilt the shared CI/CD pipeline that ships 17 production front-end apps.

45 min
15 min
Test coverage+55 pts

Brought Jest + React Testing Library in and made tests part of every PR.

30%
85%
Production incidents−40%

A downstream result of the coverage work and faster, safer rollbacks.

baseline
−40%

All of it at the scale of 3.4M monthly active users, 57 international markets and 17 production apps deployed daily.