Sensile Medical — firmware & design output V&V

Building it, then proving it works

Sensile Medical builds wearable patch injectors for self-administered drug delivery. I split my time between two very different halves of the same device: the firmware that runs it, and the design output phase that verifies and validates what the person wearing it actually sees and does.

A family of Sensile Medical wearable patch injector devices in teal and white, shown in different configurations.
The device family — same platform, different configurations

01 — Firmware

Running the device

  1. 1

    Wrote and maintained the firmware

    Worked on the firmware layer that turns a button press or a sensor reading into the correct behavior — timing the dose, tracking the state of the device, and driving what happens next.

02 — Design output & V&V

Proving the screen tells the truth

  1. 2

    Verified the screen content

    Checked every screen the device could show against its design requirements, so what's displayed always matches the therapy state underneath it.

  2. 3

    Validated the interaction flow

    Walked the full UX/UI flow — every button press, transition, and product interaction — against real use, catching the points where the screen and the firmware behind it disagreed.

A hand holding a Sensile Medical device, screen showing a countdown timer during dose delivery.
Screen state during delivery
Two Sensile Medical devices side by side showing different screen states in the interaction flow.
Two states in the same flow
A Sensile Medical patch injector worn on a person's abdomen, screen showing a countdown timer.
Worn on the body — where firmware and screen have to agree

The firmware decides what the device is actually doing; the V&V work made sure the screen never told the person wearing it something different. On a device managing someone's own therapy, those two halves had to agree every single time.