Build the revenue infrastructureAmerican healthcare needed twenty years ago
We're hiring operators, engineers, designers, and policy minds who treat craft as a non-negotiable and who enjoy complex, ever-evolving challenges.
Why Camber
Three reasons to take on the challenge
The problem
The infrastructure broke. Nobody fixed it
American healthcare loses more than $125 billion annually in legitimate revenue to denied, underpaid, or unrecovered claims. The standard response has been more labor: more billers, more audits, more tools layered on top of broken systems. It works briefly, then regresses. We're building the replacement, not another layer.
$125B+
In legitimate provider revenue lost annually
The people
Operators who've seen the problem from inside
Our founding team spent their careers deep in the weeds of healthcare operations, revenue cycle, and specialty care admin, so we're not guessing at the problem. We've lived it. And that shows up in how the team works: people here are genuinely trying to change how healthcare operates, not build their own empire. It's a small, low-ego, high-craft team where the problems are real, the impact is real, and everyone cares more about getting it right than getting the credit.
100+
on the team
The stage
Series B. a16z and Y Combinator. Real traction
Backed by a16z and Y Combinator. $50M raised. 500+ providers across 50 states. Growing from ABA leadership into PT, ENT/Allergy, and broader specialty care. We have product-market fit, a repeating revenue model, and a roadmap that gets more interesting every quarter.
Series B
a16z and Y Combinator backed
How we work
Specific, hybrid, and honest about the pace
We're a hybrid team headquartered in New York City, in the office three to five days a week. The pace is high, and the work is measured against outcomes, not activity.
A few moments from the past year
NYC Tech Event, 2026
NYC Tech Event, 2026
NYC Tech Event, 2026
The team
NYC Tech Event, 2026
NYC Tech Event, 2026
Open roles
Where we're hiring now
What we look for
The kind of person we hire
These are some of the patterns we've noticed in the people who do their best work here and who raise the bar for everyone around them.
You've seen broken systems and want to build the replacement
Not patch it. Not work around it. Build the thing that makes the workaround obsolete. We're rebuilding revenue infrastructure from first principles, and the people who thrive here have that instinct.
You treat craft as a non-negotiable
Whether you're writing code, designing a workflow, or drafting a policy position, you hold yourself to a standard that exists independent of whether anyone is watching. The work reflects you.
You have high standards and low patience for theater
Meetings that could be a message, processes that exist because they always have, status updates that obscure rather than inform. You push back on these without needing to be asked.
You operate well with ambiguity and high autonomy
We're at the stage where the answer to most questions is 'figure it out and tell us what you learned.' If you need a fully specified problem before you can move, this is probably not the right environment.
You want to be measured against outcomes, not activity
We care about what shipped, what improved, what we learned. Not how many tickets were closed or how many hours were logged. If that framing feels natural to you, you'll fit here.
Build something that keeps growing
We're hiring people who want to work on a hard problem with high standards. If that's you, the right next step is to look at what's open.