Careers at Metriport: Teams, Pay and How to Get Hired

Who Gets Hired

A 12-person company that has raised $28.4 million, Metriport reported, to rewire how U.S. healthcare data moves does not hire for headcount. It hires for leverage. Every role on Metriport's board exists because the founding team, mostly former founders and Y Combinator alumni, has identified a bottleneck that only a certain kind of operator can unblock. The question candidates should ask isn't whether they qualify on paper. It's whether their default mode matches a team that expects six-day availability not from policy but from the volume of wood left to chop.

This guide breaks down the exact qualifications, compensation structure, and interview process Metriport uses to evaluate applicants across 15 open positions in engineering, customer success, sales, product, operations, and people.

Metriport organizes those 15 roles across six functions. Engineering carries the most openings: six roles spanning Staff Software Engineer, Staff Data Engineer, Senior Software Engineer, Senior Data Engineer, Senior AI/ML Engineer, and Senior Software Engineer, Internal Tools. Customer Success carries two senior roles: Head of Customer Success and Technical Account Manager. Sales lists a single Account Executive. Product has two openings: Product Design and Design Engineer. Operations seeks a Partnerships Lead and a Strategic Projects Lead. People is hiring a Technical Recruiter and an Office Manager/Executive Assistant.

Compensation & Qualifications by Function

First-party board data from Zero G Talent puts Staff bands at $200K–$260K and Senior bands at $180K–$220K; Glassdoor confirms the ranges and adds a Senior AI/ML band of $200K–$260K. The spread between the top of the Account Executive band ($275K with commission, Glassdoor's figures put) and the Technical Recruiter floor ($120K) is 2.3x, typical for a 15-person company where quota-carrying roles carry variable upside. Engineering roles cluster tightly: Staff and Senior AI/ML positions share the same $200K–$260K band, Zero G Talent's data shows, while Senior Software and Data Engineers sit at $180K–$220K. That compression suggests Metriport values specialized AI/ML talent at a premium but keeps core engineering bands aligned.

Glassdoor's aggregate data shows a narrower $140K–$180K range, but that figure appears stale; it doesn't capture Staff-level roles or the Account Executive commission structure that push the real ceiling higher. The first-party board postings, dated to current hiring cycles, are the more reliable signal.

Equity is listed on every role, though grant sizes, vesting schedules, and strike prices aren't public. Candidates should ask for the current 409A valuation and outstanding share count during offer stage. The Office Manager/Executive Assistant role, the only hourly position, still includes equity.

Benefits details are thin in public sources. The careers page and Wellfound listing reference "perks, benefits, work-life balance" without specifics. Glassdoor lists: full family Platinum health insurance, dental, and vision coverage; 401(k) retirement plan with matching; flexible work from home or in-office; healthy lunches complimentary when in-office (and breakfast + dinners as needed); quarterly company off-sites; MacBook provided; unlimited PTO.

On-site requirements for customer-facing and operations roles (Account Executive, Head of Customer Success, Technical Account Manager, Design Engineer, Product Designer, Partnerships Lead, Strategic Projects Lead, Technical Recruiter, Office Manager) mean commute costs and daily schedule rigidity factor into total compensation.

Hybrid engineering roles (Senior AI/ML, Staff Data, Staff Software, Senior Software, Senior Data, Internal Tools) offer hybrid schedules per the listings. That flexibility carries real value. Metriport's choice to keep senior engineering hybrid while requiring on-site for product design and customer success reflects deliberate org design: the team building the API stays distributed; the team selling and supporting it sits together.

Engineering: The company builds every layer of its stack (connect, transform, insight), so engineers who have only consumed APIs will not last. Staff roles require architects who have designed data-intensive systems from scratch; Senior roles need contributors who can own a domain end-to-end and still ship fast. A Staff Engineer who has never touched FHIR but has built high-throughput data pipelines at scale will get further than a healthcare lifer who hasn't shipped in years.

Customer Success: The Head role ($190K–$250K, Metriport's postings show) demands seven-plus years with five in CS, Account Management, Solutions, or Implementations at an early-stage startup between Seed and Series C, plus experience scaling the function from 1 to 100. The posting stresses technical fluency, driving conversations with CTOs and engineers, and a "no problem too big, no problem too small" operating style. The Technical Account Manager ($160K–$190K) sits closer to implementation, requiring the same blend of customer obsession and engineering literacy.

Sales: The Account Executive ($200K–$275K with commission and equity) carries quota in a market where sales cycles are long and bureaucratic. Credibility with enterprise buyers who cannot afford downtime is non-negotiable.

Product: Product Designer ($140K–$180K) and Design Engineer ($140K–$180K) both require on-site presence. The Design Engineer role in particular sits at the implementation boundary, translating design systems into production code that engineers can trust.

Operations: Partnerships Lead ($140K–$160K) and Strategic Projects Lead ($140K–$160K) are on-site, high-agency roles. The Recruiter posting emphasizes three-plus years sourcing across technical and non-technical roles, outbound mindset, tool fluency (LinkedIn Recruiter, Gem, Juicebox, Ashby), and a preference for healthcare IT sourcing experience.

Across every function, qualifications converge on three signals. First, autonomy: the ability to take an ambiguous objective, break it down, align stakeholders, and execute without waiting for direction. Second, entrepreneurial tempo, the posting's phrasing is deliberate: "When someone scopes something for three weeks, you ask why it can't be done in three days, and you also know the difference between shipping a fast v0 and cutting a corner that comes back to bite you." Third, domain adjacency. Healthcare interoperability experience is a "significant bonus" for Customer Success and "preferred" for Recruiting, but the company hires on competence, not pedigree.

The team is small enough that every hire changes the density. Leaders are in the South Beach office six days a week and expect the same availability — not as a mandate but as a consequence of the work. Time-off requests have never been denied. The filter is self-selecting: candidates who need structure, process, or a 9-to-5 rhythm opt out before the first screen. The ones who remain have already started thinking like someone in the role.

Bottom line: a Senior Software Engineer at $200K base plus equity is competitive with Series A peers at similar headcount. An Account Executive at $200K base plus commission target plus equity matches mid-market SaaS OTEs. Ask for the equity percentage, 409A, and refresh policy before signing.

Inside the Hiring Loop

Metriport runs a hiring loop built for speed and signal, not ceremony. The company describes its process as streamlined and fast-paced, with a deliberate bias toward practical evaluation over academic ritual. Dataford reports a highly responsive process where decisions are made quickly once mutual fit is clear, a pattern consistent with a team that doubled headcount after its Y Combinator-backed fundraise in late 2022.

The first conversation is not a screen; it's a calibration. A founder or senior engineer walks through your background, entrepreneurial drive, and expectations on both sides. This isn't a cultural-fit checkbox — it's a mutual assessment of whether the pace and ownership model match how you work. Metriport explicitly values competence over prestige, so the dialogue centers on what you've built, shipped, and owned, not where you studied or which logo sits on your résumé.

Technical evaluation mirrors the actual work. The company avoids generic algorithm puzzles in favor of exercises that reflect the day-to-day: integrating with fragmented healthcare APIs, designing for regulatory constraints, debugging data-quality issues in production. In system-design rounds, interviewers penalize over-engineering. They favor simple, pragmatic architectures that operate reliably over abstracted frameworks that look elegant on a whiteboard but fracture under real traffic. Dataford puts it bluntly: avoid complex, highly-abstracted systems that are difficult to debug.

Self-direction is a screened trait, not a slogan. Strong candidates come prepared with concrete examples of identifying a problem in a codebase or infrastructure, designing a fix, and pushing it to production without a manager's prompt. That pattern — seeing the gap, closing the loop — maps directly to how the engineering team operates. For non-technical roles, the equivalent is owning a funnel end-to-end: sourcing, experimenting, closing. The recruiting role description on their Ashby board makes this explicit: "drive a full cycle recruiting process from sourcing to closing."

Applications land in Ashby, Metriport's applicant tracking system. Because most recruiters review inbound in chronological order, early applicants receive disproportionately more attention. Scoutify monitors the career page continuously and surfaces new postings within minutes of publication, a mechanical advantage for candidates who act fast. The company has no H-1B petition history on record, so international candidates requiring sponsorship should factor that into their timing.

The loop compresses when signals align. A candidate who demonstrates technical clarity, regulatory patience, and a builder's mindset can move from first call to offer in days rather than weeks. The disqualifying pattern is the inverse: theoretical answers where practical ones are expected, prestige signaling in place of shipped work, or design proposals that optimize for cleverness over operability. In a regulated domain where that dynamic prevails, the team selects for people who ship boring, reliable code — and do it without being asked.

San Francisco, Full Stop

Metriport operates out of San Francisco. The company incorporated in California on July 13, 2022, with its principal address listed in San Francisco, and every open role on the Zero G Talent board shows "San Francisco, CA, US" as the location. That consistency matters: at roughly 12 people as of mid-2026 (per Latka), the entire team sits in one metro area, not distributed across time zones.

The headcount trajectory tells its own story. Latka's tracking shows 15 employees in June 2024, then settling at 12 in December 2024, a pattern typical of a founding team that hired fast after Y Combinator, then right-sized before the Series A. The $26 million round closed in August 2026, led by Matrix with ARTIS and Y Combinator participating. That capital is earmarked for scaling the platform and expanding AI and agentic capabilities, which in practice means more engineers and customer-facing hires. The board currently lists 14 salaried roles, Zero G Talent's board shows, with a median band of $185K, Zero G Talent's figures put, all San Francisco–based.

No public handbook, blog post, or job description mentions distributed work, home-office stipends, or mandatory in-office days. The safest read: the company is small enough that the default is physical presence in San Francisco, and candidates should assume the interview process and day-to-day collaboration happen there unless a hiring manager says otherwise. For a team handling HITRUST r2–certified infrastructure, SOC 2 Type II compliance, and real-time PHI flows across 750,000-plus providers, colocation simplifies security posture.

The office itself isn't described in any filing or press release. What we know is the work: an engineering-heavy crew (former founders, per the company's own recruiting copy) shipping open-source data infrastructure that normalizes FHIR R4 records from HIEs, ADT feeds, pharmacies, labs, and EHRs into a single API, data warehouse, or EHR embed. The stack processes 4.2 billion network requests per month with a p80 time-to-first-structured-record under 15 seconds and 99.999% platform uptime. That throughput implies a production environment that demands low-latency collaboration between backend engineers, data engineers, and the customer success team onboarding enterprises like Amazon One Medical, Sollis Health, and Color Health.

For a candidate, the takeaway is concrete: you'll be in San Francisco, working shoulder-to-shoulder with a sub-20-person team that moves at startup speed but operates under healthcare-grade compliance. The next hire changes the ratio noticeably. If you need remote flexibility, ask early — the current signal points to an in-person default.

The Filter

Metriport is not a place for people who want to hide behind a ticket queue. The company sits at the intersection of three unforgiving domains: healthcare regulation, data infrastructure, and open-source accountability — and its ~12-person team operates with the surface area of an organization three times its size. The people who last here share a specific cluster of traits, and the hiring record makes them legible.

Mission orientation that survives contact with reality

The founders frame the company explicitly as a mission-driven venture: "democratizing access to healthcare data and ultimately improve patient health outcomes." That language appears in their 2022 TechCrunch announcement and again in the 2026 Series A materials. But the mission isn't decorative — it dictates product decisions. Metriport chose open source for both its Health Device API and Medical API because "the decisions around how patient information is managed and transformed are too important to trust to a black box." That commitment means every engineer's code is public, every data transformation is auditable, and every architectural choice can be challenged by a customer or a competitor.

Comfort with earned trust, not assumed access

Healthcare data demands "the highest level of protection," and Metriport built that into its go-to-market motion from day one. The company does "deep diligence on every organization that wants to access the healthcare exchange data networks via Metriport," investigating the company, vetting comprehensively, and "paying attention to who's actually in the room during onboarding calls." This isn't compliance theater — it's a cultural operating mode. Candidates who thrive here treat security and privacy as product features, not checkboxes. The HITRUST r2 Certification (achieved 2026) is the external validation; the internal habit is questioning every data flow before it ships.

Engineering rigor in a regulated maze

The technical problem is genuinely hard: dozens of connections to major healthcare data sources, each with its own quirks, normalized into a unified data model accessible via API, warehouse, or in-EHR apps. Records arrive in bespoke formats — HL7, FHIR, CCDA, proprietary vendor dumps — and must be matched, extracted, standardized, deduplicated, and enriched in real time. The team is simultaneously building the ingestion pipelines, the standardization layer, and the AI summarization that surfaces "exactly the information the clinician needs, without requiring a data science background to get there." That stack requires engineers who can move across infra, data, and product without losing the thread.

Disruptor temperament without the chaos

Goncharov, a co-founder, put it bluntly in 2022: "in every industry, when the existing players stagnate from being comfortable off of profits from the status quo, the market is open for disruption by younger, hungrier and more modern companies." Metriport positions itself as the Plaid for healthcare data, the infrastructure layer that lets digital health companies scale without building their own integrations. But unlike many "move fast" startups, this one sells to those same enterprises. The sales motion demands that same credibility.

Small-team ownership, large-surface accountability

With 12–15 people generating $5M ARR, Latka's data shows, (June 2024), every role carries disproportionate scope. The Head of Customer Success ($190K–$250K) isn't managing a team of CSMs, they're defining the function, onboarding enterprise clients, and feeding product feedback directly to engineers. Senior engineers own entire integration pathways. Data engineers build the pipelines that turn raw claims and clinical notes into the longitudinal records clinicians actually trust. There is no "my job ends at the PR" culture; the PR is the starting point for a conversation with the customer who will use it tomorrow.

Transparency as a working style, not a value statement

"We will set a new standard for dev-friendliness, transparency and accessibility in the health tech data space." That promise, made at launch, shapes how the team communicates. Open-source repos mean public issue trackers, public roadmaps, public design docs. Customer onboarding calls involve scrutiny of who's in the room. Internal decisions (from data model changes to pricing adjustments) are documented with the expectation that a customer or community member might read them.

AI curiosity grounded in clinical utility

The 2026 Series A explicitly funds expansion of "AI/machine learning and agentic capabilities", but the use case is constrained: surfacing the right clinical insight at the point of care. PR materials cite a concrete example: a patient with abdominal pain who recalled an endoscopy years prior but not the findings; Metriport surfaced the operative report showing an early ulcer, enabling immediate treatment without a duplicate CT scan. That is the bar. Candidates who want to train foundation models on healthcare data will find the data access but not the compute budget; candidates who want to build retrieval-augmented summarization that a physician trusts in a 15-second glance will find the problem space and the distribution.

The filter

If you need structure handed to you, if you treat open source as a marketing checkbox, if you view HIPAA and HITRUST as someone else's problem, if you want to optimize a narrow slice of a large codebase, Metriport will frustrate you. The people who stay are the ones who look at a fragmented, regulated, high-stakes data environment and see the infrastructure problem worth solving. They write the code, close the deal, answer the security questionnaire, and push the commit to the public repo — all in the same week.

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