Gena Health: Scaling Engineering Team for an AI Product Empowering Cancer Patients
How an AI health tech platform for precision oncology backed by Innovate UK engaged Frontend and Full-Stack Engineers.

Challenge
Gena Health is a London MedTech startup building a platform for cancer patients, connecting them and their clinicians to personalised treatment options drawn from genomics and AI, with funding from Innovate UK behind it. The hard part was never the genomics. It is that the people on the other side of the screen are patients facing rare or late-stage cancer and the specialists treating them, and both have to be able to follow the reasoning behind an option rather than take it on trust. Evidence in precision oncology also arrives faster than any clinician can read it. What Gena Health needed to prove first was therefore an interface, not a pipeline, and at the point they came to us it did not exist.
Two requests, separated in time, because the company scaled its engineering deliberately rather than all at once. The first was a Senior React Engineer to build the MVP, specified by a CTO already in post who knew what the first version had to do and needed hands to build it rather than someone to decide its shape. The second came later, once the product was functional, and widened to Senior Full-Stack across Python and React to refine and polish something that now had real users to answer to. Both roles needed seven years and more of React and TypeScript, and the judgement to work inside an existing technical direction rather than set one.
Both requests were screened against the CTO’s own specification, on evidence of MVPs actually shipped rather than enthusiasm for greenfield work, which in practice meant asking what each engineer had cut from a first build and why. The first match was engaged 12 hours after the request opened, one the fastest placements we have made. The CTO ran the interviews and made the technical call, which is the shortest version of this process: one person who knows exactly what they need, and a shortlist short enough to act on the same week.
Outcome
Scaling an engineering team means hiring against the stage the product is at, not the team you eventually want. For a grant-funded company that stage comes with a date attached. Gena Health needed one pair of hands to get an MVP in front of people, and a different shape of engineer once that MVP worked and had to be made good. Two requests, months apart, each matched against where the product actually was rather than against a plan written before it existed.
- Two roles matched across two requests, the first engagement confirmed 12 hours after it opened - one of the fastest placements we’ve had.
- The patient-facing MVP and then both backend and frontend behind it, built first and then refined.
- Capacity added under a CTO already in post, so technical ownership stayed in-house while the build got the engineering capacity it needed.
- Five months on, engineers are on the engagement, carrying the product from first build through to refinement of a working platform.
Yotewo team were really flexible when we had delays during our development process and were able to accommodate a last minute change to the project KO! And we’ve had great experience working with them this far.

A Strategic, Multi-Phase Hiring Approach
Phase: Request
Two requests opened months apart rather than together: a React engineer to get the MVP built against the grant’s delivery timeline, then full-stack Python and React capacity once there was a working product to improve.
Phase: Matching
6 shortlisted engineers were screened against the CTO’s own specification, with the health tech and MVP experience in each profile vetted rather than taken on trust, and 4 of 6 went through to interview.
Phase: Interviews
The CTO ran the interviews and made the technical decision, and the first engagement was confirmed 12 hours after the request opened.
Phase: Engagement
Both engagements opened with a full-time monthly workload sized against the stage the product was at, with daily hour commitments in the tracker and monthly reports approved over 6 months.
Phase: Support
As the product moved from MVP to polish, the workloads were changed and approved from the account.
