Build software that gives medical device teams their week back.
We're a small team automating the coordination work between field reps, distributors, manufacturers, and the ERPs that everything eventually has to land in. If you've done that work — or built the tools that should have — we'd like to talk.
Why we exist
Our software runs inside the medical device case workflow — from a case getting scheduled, to a rep submitting a bill-only, to a manufacturer getting paid. That workflow is broken everywhere we look: reps on paper, billers chasing email threads, manufacturers sitting on millions in unmatched POs and billions in stranded inventory. We exist to make it work — for the rep, the biller, the ops lead, the commercial and finance leaders.
We build for people who can't afford us to be wrong. Their workflow doesn't have room for our bugs. That's the responsibility we accepted when we started selling them software.
How we build
Engineers operating as PMs, more time on specs, async-first, milestones over issues, prototypes before production — exists to make quality the default outcome, not something we fight for at the end.
Quality is the top priority
We're dealing with money, inventory, and patient-adjacent workflows. When we ship something broken, real cases get billed wrong and real reps lose their weekends. We don't trade quality for speed — that trade isn't real. The cost of low-quality shipping is trust we can't buy back.
- Speed matters, but correctness comes first. If the choice is shipping next week with a known problem or in two weeks done right, we ship right. Better still: cut scope, ship sooner, flag what's deferred.
- Anyone can hit the emergency stop. See something about to ship that doesn't meet the bar — a confusing flow, a missed edge case, a regression — pull the cord. We'll reschedule a milestone before we ship something we'll regret.
- If you ship it, you own it. Agentic tools are shovels and pick-axes, not replacements. However the code got into your PR, it's yours once it ships.
Move quickly, but don't overcommit
We earn the right to keep working with our customers every day. The way to move fast and stay correct is to make the shippable unit small.
- Small and fast beats complete and slow. Get the smallest useful capability into customers' hands, collect feedback, iterate.
- Keep PRs compact. Huge PRs are hard to review, hard to undo, and get less attention per line. You and your reviewer should know exactly what's going to production.
- Make commitments deliberately, then keep them. A milestone date is a real commitment — not "I'll try." If it's at risk, raise the flag early. Trust compounds; broken commitments compound the other way.
Love the problem, get to the solution
You're here because we think you're smart and capable. No one will tell you how to work — but empowerment is paired with ownership. You own outcomes, not just outputs.
- Learn the user's day. Our users are surgical reps in hospital hallways, billers chasing $50k POs through email threads, ops leads hunting for a tray that left the warehouse three weeks ago. Before you build, you should be able to describe their day before, during, and after our software touches it.
- Push back when you should. Need context, ask. Disagree with a spec, say so. See a better path, take it — and tell us why.
Open roles
Don't see the role you'd want? Email us anyway — we hire ahead of posted listings when the right person shows up.
What to send
A short note about which problem in medical device operations you'd most like to take on, plus whatever evidence you'd want us to see — code you've shipped, ops you've run, a teardown of a system that frustrates you. No cover letters. We read everything.
Send to hello@deviceflow.com .
The Space Between
What happens between what your field team sends and what your systems need — and what your team can stop doing manually.