SOFTWARE ENGINEER · TECHNICAL LEADER

I build the product surface and the systems behind it.

I design and ship software across frontend, backend, data, cloud infrastructure, and production operations. I am most useful when a problem crosses those boundaries.

Technical flow connecting interface, services, data, infrastructure, and observability.
Interface
Services
Data
Infrastructure
Observability

A problem rarely stays inside one box.

A product issue might show up in the interface, come from a backend rule, depend on the data, or turn out to be a deployment problem. I am comfortable following it through those layers and staying with the work until the outcome is right.

Working in startups taught me not to treat a job description as the boundary of the problem. When the work has required it, I have also led product, business, and partnership conversations to help move the product forward.

Case studies

Three products with different users, business models, and technical constraints.

Audicin V2

Audicin’s original CMS-backed application had become difficult to extend and could not support the company’s plans for personalization, deeper product analytics, and data-informed wellbeing experiences.

I scoped the V2 programme as a software engineer and was promoted to CTO as delivery began. Over the following months, I led a three-engineer team through a rebuild spanning the backend, mobile applications, cloud infrastructure, subscriptions, listening analytics, health-data processing, and internal administration.

Impact: I designed and implemented the new C#/.NET platform, migrated the live product with negligible interruption, and introduced the systems Audicin needed to measure listening behaviour, support research, and evolve beyond the limitations of its original CMS.

Backend ArchitectureProduct DeliveryData SystemsCloud Infrastructure
Read the case study

Audicin Web

Audicin Web brought the product's listening experience to the browser, giving users access without requiring a mobile application installation.

I built the web application and the backend services, infrastructure, and deployment path required to operate it as a production product.

Impact: Created an additional product channel and made Audicin accessible across desktop and mobile browsers.

Frontend EngineeringBackend ServicesCloud Delivery

Key challenge: Translating a mobile-first listening experience into a responsive browser interface while preserving playback state, account behaviour, and backend consistency.

Read case study

Bridger

Bridger enabled businesses to acquire inventory through financing rather than paying the full cost upfront.

I worked on the backend workflows supporting onboarding, identity verification, financing origination, wallet state, payments, and repayment tracking.

Impact: Turned a multi-party financing process into structured, auditable software workflows supporting the full customer lifecycle.

Domain ModellingPaymentsBackend Systems

Key challenge: Maintaining consistent financial state across external providers, multi-step operations, failed transactions, and partially completed workflows.

Read case study