Benjamin Doyle

MediCann's first technology hire and de facto technology lead. Own architecture, delivery, vendor selection, analytics, and systems strategy end to end, partnering directly with the executive team on roadmap, build vs. buy, and commercial trade-offs.

Stood up the patient-facing product and internal admin tooling on Next.js, with a marketing surface in Framer. Designed the data and event model, operational dashboards, and reporting layer that expose drop-off, appointment flow, utilisation, and commercial bottlenecks, converting raw operational data into board-level signal.

Made the early build vs. buy vs. API calls across the stack (Salesforce, Next.js, third-party integrations, AI tooling) with cost, lock-in, and regulatory posture as explicit inputs. Set the foundations for security and access control appropriate to handling patient data in a clinical workflow.

Joined as a Senior Engineer and was promoted twice in seven months as scope kept widening. Started shipping product features across front end and backend, moved into a product role to design the first Practitioner Portal directly with clinicians, then took over technology leadership across product and platform.

The Practitioner Portal was the headline piece. Took a messy clinical workflow and turned it into a clean, usable product surface. Designed in Figma from scratch, validated directly with practitioners, then partnered on the build through APIs, code review, and the component patterns that became the foundation of the design system.

As Technology Director the title was senior but the work stayed practical: unblocking delivery, tightening access controls and system configuration, and improving the systems behind reliable practitioner and customer experiences. Worked with the Head of Data and Strategy to establish cleaner operating foundations so product decisions ran on better signal rather than assumption.

Joined as a Senior Software Developer in a rapidly scaling healthcare environment, contributing across the stack as the platform needed to support more patients, more roles, and more operational complexity. Promoted to Engineering Manager / Tech Lead within six months, then to Group Engineering Manager leading multiple teams across product and platform.

Treated management as a way to improve delivery quality, not a step away from hands-on work. Stayed close to architecture, API and database design, code review, and production support throughout. Introduced lightweight rituals like retros, sprint planning, pair programming, and code reviews, plus an epic ownership model that gave engineers more autonomy and clearer accountability.

As Group EM, worked with clinical, compliance, product, and executive stakeholders to shape roadmap decisions around complex healthcare workflows. That cross-functional work sharpened how I pressure-test ideas early and balance user needs, delivery speed, and technical integrity. Mentored managers and engineers while staying hands-on for interface-heavy features.

Joined as a Software Engineer and progressed through three levels over five and a half years, building full-stack systems across backend and front end in a high-traffic, multi-team environment. Shipped customer-facing features at scale and got a strong foundation in turning complex platform and data problems into reliable product behaviour.

Seconded into a data engineering team partway through, working on big-data pipelines and ML-backed APIs used across the organisation. That stretch sharpened how I think about instrumentation, data models, and the interface decisions needed to make complex data actually useful downstream.

Moved into native iOS development in the final year and ramped quickly with no prior mobile experience, which is how I tend to work in unfamiliar domains: learn fast, ship, close gaps directly. Contributed to customer-facing travel experiences where polish, performance, and reliability mattered at scale, adding mobile depth to an already broad full-stack background.