Camber pays $230K for engineers who fix healthcare’s $125B revenue leak

What the Board Shows

Camber's careers page lists 16 open roles as of early August, six in engineering, three in billing, two in insurance operations, one in people, and one in go-to-market. Zero G Talent's first-party board, which ingests listings directly from the source, shows a Senior Data Engineer role posted in the past seven days at $180,000–$230,000 in New York. Third-party aggregators Jobscroller and Jobera both show 16 roles on August 6; Engradar's tracker showed 14 on July 31 and labeled the trend "cooling." The discrepancy matters: aggregators scrape; the board sees what the company actually publishes. When the board shows a fresh senior data role while scrapers show a flat count, Camber is still adding, just not in the volume or velocity that triggers "surge" headlines.

The functional spread is where the signal sharpens. Six engineering roles for a 100-person team building revenue-cycle infrastructure signals product depth, not feature churn. Three dedicated billing hires, all remote, signal that the product still needs operators who know the payer workflows the software aims to replace. Two insurance operations roles in New York suggest the feedback loop between product and operations runs tight and local. Nearly nine in ten listings show salary, unusually high for early-stage health tech, and the same share are on-site in New York, with the rest remote. Hybrid doesn't appear. Average listing age is 71 days, suggesting roles stay open until the right profile arrives rather than closing on a hiring sprint timeline.

The board's median salaried band sits at $168,000 across 12 roles with published figures; the overall range spans $38,000 to $230,000. Camber's headcount passed 100 earlier this year, backed by $50 million in Series B funding from a16z and Y Combinator, Jobera's listings show. The company serves 500-plus providers across 50 states, expanding from applied behavior analysis into physical therapy, ENT/allergy, and broader specialty care, camber.health's data shows. That operational footprint — not the raw role count — makes the hiring mix legible.

The Filter Stated Plainly

Camber's careers page states its hiring logic in the first paragraph: "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." That sentence operates as a self-selection mechanism. Candidates who read that sentiment and feel a mismatch don't apply. The ones who stay are pre-screened for operational humility over personal brand-building.

The language extends into the candidate profile: "You treat craft as a non-negotiable." "You have high standards and low patience for theater." "You operate well with ambiguity and high autonomy." "You want to be measured against outcomes, not activity." Each bullet is a negative filter dressed as a positive trait. "Low patience for theater" excludes performers who optimize for visibility. "Measured against outcomes, not activity" excludes resume-builders who count shipped features instead of solved problems. "High autonomy" paired with "low ego" creates a paradox that only resolves for people who've actually operated in messy, low-margin environments, the kind where no one hands you a spec and the credit goes to whoever fixed the billing reconciliation at 2 a.m.

This phrasing matters because "low ego" has become a startup cliché. Ask a Manager documented the term's drift into a cultural fad across certain startups, making it "hard to know if it was just in there to be in there or in there because you were about to work for a toxic dumpster fire." TeamBlind threads from mid-2023 reveal the skepticism: "low ego" translates to "willing to turn a blind eye to manager's backhanded comments," "someone who wouldn't question them or challenge the status quo." Camber's postings sidestep this trap by anchoring the term in operational specifics rather than cultural vibes. The MIT Sloan definition of low-ego leadership, "care more about getting to the right answer than in being the one who came up with it," maps directly to that principle. But Camber goes further: it ties the trait to revenue cycle management's particular demands. RCM doesn't reward heroics; it rewards the person who understands why a 270 denial code keeps recurring and builds the automation to stop it. That work is invisible, iterative, and unglamorous. The job descriptions make that visibility the point.

Founders Who Lived the Problem

Nathan Lee, who founded the company as Juniper in 2019 and led it through a 2025 rebrand to Camber after a $30 million Series B from a16z, has spent years documenting the operational reality that shapes the company's hiring lens. His LinkedIn posts from 2021 through 2026 trace a consistent thread: revenue cycle control erodes not through catastrophic failure but through "thousands of hidden human judgement calls that aren't shared, measured, or reconciled." He describes watching provider organizations scale from regional to national footprints and seeing "small changes make sense locally, but over time and scale, they add up to millions of dollars of leakage." That perspective, grounded in serving clinics from 8 providers to 8,000, and saving multiple clinics from bankruptcy, determines what Camber looks for in candidates.

The job criteria mirror that operator's vocabulary. "You've seen broken systems and want to build the replacement." As previously stated. As previously stated. These aren't generic startup values; they're the specific filters of a team that processed 1 million-plus claims annually across 500-plus providers in 50 states, trained models on $2.5 billion in claims data, and achieved a 95-percent-plus first-pass paid rate. When the careers page says "We're hiring operators, engineers, designers, and policy minds who treat craft as a non-negotiable and who enjoy complex, ever-evolving challenges," the word "operators" carries the weight of lived RCM pain.

That pain also shapes how Camber defines the problem space for technical roles. The company doesn't frame its mission as "AI for healthcare billing" — it frames it as infrastructure replacement. "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." That distinction appears in the evaluation criteria for engineers and data scientists: they're assessed on whether they understand the dynamic, payer-specific complexity that defines modern reimbursement, not just whether they can optimize a model. The Senior Data Engineer role listed at $180,000–$230,000 and the Staff Software Engineer role at $210,000–$225,000 both sit inside a product organization that ships against $125 billion in annual legitimate revenue loss — a figure the founding team cites not as market sizing but as operational scar tissue.

The hiring filter extends to policy and alliances roles. Camber's roadmap includes "legislative advocacy for improved access to specialty care" and "publishing policy position papers grounded in real claims data." The founding team's experience watching reimbursement models shift underneath providers: "American healthcare is mid-transition." The payer environment, the reimbursement model, and the infrastructure underneath are all changing, which means they evaluate policy candidates on whether they can translate claims-level reality into regulatory strategy, not just track legislation.

Every criterion traces back to a specific operational lesson: ambiguity tolerance comes from navigating edge cases that never got reconciled; outcome-over-activity measurement comes from watching labor-based approaches regress; low patience for theater comes from seeing "human patchwork that builds up throughout the years, natural entropy that's never revisited." The filter works because the people designing it have paid the tuition.

Who Applies, Who Stays Away

Camber's job postings don't hide the domain requirement. The salaried roles, including Senior Data Engineer, Senior Software Engineer, Staff Software Engineer, Software Engineer, and Senior Data Analyst, all in New York and all carrying salary bands from $150,000 to $230,000, lead with revenue cycle management, claims processing, denial workflows, payer logic. None list "healthcare experience preferred" as a footnote. A generalist engineer scanning the stack sees the filter immediately: this is not a tour-of-duty role where you learn the domain on someone else's dime.

The filter works because the operational pain is specific. Frontline community health operators describe a system where over half of patients are uninsured, where 100,000 Coloradans face Medicaid disenrollment in 2027, where bilingual staff shortages compound clinical vacancies, where fundraising fills half the budget because reimbursement logic doesn't cover the population. That complexity — eligibility churn, prior auth labyrinths, denial codes that vary by payer and plan — cannot be abstracted into a clean API specification. Engineers who have never watched a billing team rework the same claim three times because a modifier changed on page 47 of a payer manual will not recognize the edge cases that break Camber's product.

Applicants self-select out. The ones who stay are the engineers who spent two years at a clearinghouse mapping 837 transactions, the data analysts who built denial dashboards for a hospital system's RCM department, the product managers who argued with payers over medical necessity criteria. They recognize the problem space because they've lived the 2 a.m. spreadsheet reconciliation. The salary bands — median $168,000, topping at $230,000 for staff engineering, signal that Camber pays market rate for that scar tissue. It's not a mission discount.

The Board Doesn't Lie

The first-party board data shows Camber's hiring fingerprint: 12 salaried roles, salary bands ranging from $38,000 to $230,000 (median $168,000), clustered in engineering and data. One role added in the past seven days: Senior Data Engineer, New York, $180,000–$230,000. That table is the grounded evidence. It tells us Camber pays market-rate engineering salaries in New York, clusters senior roles in a narrow $180,000–$230,000 band, and keeps a $50,000 spread between base and senior, standard for a well-capitalized, post-Series A health tech outfit in New York.

The last role posted, Senior Data Engineer, seven days ago, same band, same location, will sit open for roughly 71 days if the average holds. The right candidate will have argued with a payer over a denied claim at 6 p.m. on a Friday. They'll read "low patience for theater" and know exactly what it means. They won't need the job description to explain the problem. They've already lived it.

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, camber.health's careers page reports. 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, camber.health's figures put the team at over 100

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

Working in frontier tech? Zero G Talent tracks the openings: see every open Camber role, browse frontier tech jobs, the companies hiring, and the people building the field.