Book a strategy call
Back to case studies
Education Administration Programs

Eos Learn: Supporting Engineering of a Digital Learning Product

How an education platform for UK training providers hired two WordPress engineers and a DevOps engineer.

Challenge

Eos Learn builds EOSONE, a platform that takes work off tutors at UK training providers. It co-delivers the training, pre-marks every activity before a tutor sees it, and gives each tutor what they need to individualise their coaching, so the same team can carry more learners. That is an unusual promise to engineer against. The product’s value is measured in work that no longer happens, which means every judgement it makes automatically sits inside a regulated programme: marking that affects a learner’s progress, and data that feeds the ILR submission a provider’s funding is calculated from. Quality and compliance have to hold while the platform is actively being used to grow.

Two requests were opened together, and a third followed later. The first two were Senior WordPress Engineer roles needing nine years and more of production WordPress and WooCommerce, and specifically the experience of working inside a large existing codebase rather than starting one: custom themes, plugins and learning modules, membership architecture, REST API integrations against payment gateways and third-party services, on PHP, WordPress Core, Gutenberg, React and MySQL. The third came once that extra output needed somewhere reliable to land: a Senior DevOps Engineer, seven years into AWS infrastructure design, containerisation and CI/CD automation, with Terraform, Docker, Kubernetes and GitLab CI, and a background in security hardening through IAM, WAF and compliance automation rather than infrastructure maintained at arm’s length.

The two sets of requirements were screened differently. For the WordPress roles the question was not whether someone could build a feature but whether they had refactored a mature product without taking it down, which is the most relevant thing for a platform that cannot have a bad release. For the DevOps role it was whether security and compliance work had been owned rather than inherited, given the type of data in the system. The engagement was confirmed 72 hours after the request opened, and Eos Learn product management team interviewed and selected all three engineers themselves.

3
Talents Secured
9+
Months
72h
Time-to-hire

Outcome

Building more into a product and keeping it safe to run are different problems, and most teams meet the second only once the first is solved. Eos Learn added two WordPress engineers to build inside the product, then came back for a DevOps engineer to take on the infrastructure, security and compliance work underneath it, which on a platform holding funding data is not a background task. The third request opened against the same account as the first two, which is the difference between scaling a team and starting a search.

  • Three requests filled in sequence, with the engagement confirmed inside 72 hours.
  • Engineers on both platform side of the product where providers work every day, and the infrastructure, security and compliance holding it up.
  • Three engineers absorbed into the team rather than run as a separate build, working to its standards under existing product management.
  • Nine months in, three engineers are on the engagement, covering product development alongside devops work.
I’ve worked with them for over a year, and all their developers have been top-notch and helpful in my selection process.
Miguel De La Cruz
Miguel De La Cruz
Product Manager, Eos Learn

A Strategic, Multi-Phase Hiring Approach

Phase: Request

Two WordPress requests opened together for the product itself, with a DevOps request following later on Terraform, Docker, Kubernetes and GitLab CI across AWS, once more features needed a release process that could carry them.

Phase: Matching

9 shortlisted engineers were screened on work inside large existing codebases, with refactors delivered without downtime vetted for the WordPress roles and owned security and compliance work vetted for the DevOps role, and 3 of 9 went through to interview.

Phase: Interviews

Interviews were booked and conducted by the product management team of Eos Learn, and the first engineers was engaged 72 hours after request opening.

Phase: Engagement

All three engagements opened with a full-time monthly workload with daily hour commitments in the internal tracker and monthly reports with breakdown of hours approved over 9 months.

Phase: Support

As Eos Learn added and implemented features over nine months, workloads for all roles moved with the product, and every change was requested and approved in the account.