Clavis: Scaling Technical Team for German Education Platform
How a course and camp booking platform engaged a Product Owner, two Full-stack Engineers and a DevOps Engineer.
Challenge
Clavis runs a booking and enrolment platform for its art courses and holiday camps in Berlin, and the surface of it is deceptively plain. A parent arrives looking for a camp that suits a nine-year-old in the Easter holidays, in multiple languages, and has to find it, take one of a limited number of places and pay for it in the few minutes they have. Behind them, the school’s own staff run sessions, age bands, capacities, attendance and QR-coded entry from an admin panel they need to operate without a developer sitting next to them. Two public language versions, seasonal demand, limited places and live payments is a substantial system for a small organisation, and a version of it already existed, unfinished.
The order of the requests followed the state of that platform. The first was a Product Owner rather than an engineer, a decade of process work and product ownership behind them, brought in to establish what the system owed its users and its administrators before anyone extended it any further. Two full-stack engineers followed, seven years and more each across React, React Native, Node.js and TypeScript with GraphQL, both used to picking up production systems other people had started. A DevOps engineer came third, seven years into AWS infrastructure, containerisation and CI/CD on Terraform, Docker, Kubernetes and GitLab CI, once there was a platform worth running properly.
Three things were screened for beyond the stack. Education, because course structures, age bands and term-time demand behave nothing like generic retail. Booking and payment systems specifically, since the two hardest parts of this platform are taking money reliably and holding a limited place while somebody pays for it. And production systems inherited rather than begun, where the engineers we wanted see the job. The first of the four engagements was confirmed 30 hours after the opening request.
Outcome
Clavis did not need a team assembled on day one. It needed someone to establish what the platform was supposed to do, then the engineers to make it do that, then the infrastructure to keep it standing. Three requests in that order over six months, each written with the benefit of what the previous one had found.
- Three requests, four people in total, with the first engaged inside 30 hours.
- The product defined before it was built on, then the application, then the infrastructure beneath it.
- A software team for an organisation that had never run one, under the management of operations and technical support team.
- Six months in, bookings, payments, age filtering and both language versions have been carried forward on the existing platform rather than restarted.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
Three requests in sequence rather than one brief: a Product Owner to establish what the platform owed its users, two full-stack engineers on React, Node.js and TypeScript to take it over and extend it, and a DevOps engineer on Terraform, Docker, Kubernetes and AWS to put it on proper footing.
Phase: Matching
Engineers were screened on education platforms and on booking and payment systems running in production, then on systems inherited and repaired rather than started from scratch. The Product Owner was screened on operational processes mapped and turned into specifications, and the DevOps engineer on infrastructure owned end to end.
Phase: Interviews
Operations and technical support team as well as founders met every candidate and made each call, with the first engagement agreed 30 hours after the opening request.
Phase: Engagement
Each engagement began with full-time monthly workloads and hour caps set, visible daily hour commitments in the tracker, and a monthly report with full breakdown of hours.
Phase: Support
Each of the four engagements had workloads and hour caps moving month-to-month, and hours as the build demanded with all changes requested and approved from the account.
