We hire rarely and deliberately. When we do, it's usually someone who found us first.
There are no posted openings right now. We'd rather tell you that plainly than keep a listings page that looks alive and isn't — you'd spend an afternoon on an application that was never going anywhere, and we'd have wasted it.
If you think you'd be an exception, write to us anyway. Not a cover letter. Tell us what you'd want to work on here and why this particular problem is the one you'd pick. A link to something you've built or shipped is worth more than a résumé, and one specific paragraph is worth more than three general ones.
We read everything that arrives. We reply to the notes we can do something with, and we'll say so if we can't — a role that doesn't exist today sometimes exists in six months, and we keep the good ones.
You've shipped software where a defect has consequences beyond a bad review — EMRs, pharmacy or lab systems, payments, anything audited. You already think in terms of state machines, idempotency and evidence.
You practice, or you did, and you've spent years working around tools designed by people who never had to use them. You want to fix that from inside the product rather than file another ticket about it.
Intake through fulfillment: licensure, credentialing, consult throughput, refills, pharmacy, support, the reconciliation nobody talks about. You know where the money and the risk actually leak.
You've taken a healthcare company through a real assessment — an audit, an enterprise vendor review, a breach tabletop that wasn't hypothetical — and you can tell a control from a paragraph describing one.
We work remotely, and people own problems end to end rather than passing them along. Whoever picks something up sees it through.
You'll own areas outright and decide most of the how. There is also nobody assigning you work each morning, and that suits some people and not others.
Decisions get written down — the reasoning, the trade-off, the thing we rejected. Across time zones it's the only version of context that survives, and it makes disagreeing productive instead of loud.
We'd rather ship something that holds up under a real patient load and a real audit than something that photographs well in a demo. It's slower on the parts that must not break, and we're at peace with that.
No role, no form, no tracking number. Tell us what you'd want to work on and why this problem, and we'll read it.