Labnote: Supporting Integration of a Note-Taking Platform with Engineering Team
How a UCL-backed electronic lab notebook hired a Frontend Engineer, a Backend Engineer, a QA Engineer, a Project Manager and an Integration Consultant.
Challenge
Labnote is an electronic lab notebook built for teaching: a place where students record what they did in a practical and staff review it afterwards. The buyer is a university department, and that single fact determines the engineering. Institutions do not adopt tools that sit beside everything else they run. Students expect to sign in with the credentials they already have, class lists need to come from the system that holds them, work has to end up where marks are recorded, and files have to live in storage the university controls rather than somewhere a supplier chose. For a product in this position, integration is not a feature on the roadmap. It is the condition of being adopted at all, and with backing from UCL’s Division of Surgery and Interventional Science behind the company, Labnote’s earliest users sit inside exactly the kind of institution least able to bend its own systems to suit a supplier.
Five requests went in throughout a two-month window, and the shape of the group follows from who was asking. Labnote’s founders are a CEO and a CSO: deep subject knowledge, and no engineering direction in the company. The build roles were a backend engineer on Laravel 9 with MySQL, Redis, Docker and socket.io for the real-time side, and a frontend engineer on Vue.js with Vuex and Vue Router, Bootstrap 5 and GSAP. Around them went a QA engineer, because integration work fails in ways that only testing against live systems exposes, an integration consultant for judgement rather than throughput, covering which standards to use and where the edges of someone else’s system actually are, and a project manager working in Jira and Confluence, with Miro and Figma for site maps, accountable for delivery and in practice for the information architecture neither founder was going to produce.
Integration work screens differently from feature work. It fails on credentials, permissions, rate limits, undocumented behaviour and other people’s downtime, none of which appears in a portfolio of screens. So shortlists were weighted towards engineers who had delivered against third-party systems they did not control and could describe what went wrong rather than what shipped, and the consultant towards advice that had later been built on. The first engagement was confirmed 48 hours after the request opened, and both founders interviewed throughout.
Outcome
A push for integration only works if every part of it arrives at once. Labnote needed four disciplines simultaneously: build, test, delivery and integration judgement, because a connected product cannot be assembled in sequence when the thing it connects to is outside your control and unavailable on your schedule.
- Five requests with the first one confirmed inside 48 hours.
- Build, testing, delivery management and integration judgement covered together.
- Assembled around two scientist founders with no engineering direction in-house, so the team had to be self-sufficient from the first day.
- Two months of engagement connecting the product to the systems its customers already run.
The service provided by Yotewo is really incredible and the expertise of the team is really high and hope we can continue this amazing collaboration.

A Strategic, Multi-Phase Hiring Approach
Phase: Request
Five requests opened at once: a backend engineer on Laravel, MySQL, Redis and socket.io, a frontend engineer on Vue.js, Bootstrap and GSAP, a QA engineer to test against live third-party systems, an integration consultant for the standards and architecture decisions, and a project manager working in Jira, Confluence, Miro and Figma.
Phase: Matching
Weighting went to work delivered against third-party systems the candidate did not control, where credentials, permissions and undocumented behaviour are the real obstacles, and for the consultant to advice that had subsequently been built on rather than filed.
Phase: Interviews
Both founders, the CEO and the CSO, interviewed throughout and decided together, with the first engagement confirmed 48 hours after the request opened.
Phase: Engagement
Each engagement opened with part-time workload, hour caps, daily tracker, and monthly reports with breakdown of hour commitments.
Phase: Support
Integration consulting, build, testing and project management ran throughout two months, with workloads and hour caps changing upon request and approval of the founding team.
