The Clock Runs Differently Here
Metriport processes more than 100 million network requests a day, 4.2 billion monthly, per Metriport's website, with a p80 time to first structured record under 15 seconds and 99.999% uptime. Sub-second response times are a stated standard, not an aspiration. The company achieves this with 66 open roles as of mid-2026, most in San Francisco, a median salary of $185,000, and engineers working close to infrastructure without a dedicated platform insulation layer.
That lean scale and data-forward hiring mix are the spine of Metriport's culture. They dictate how work gets done day to day, the operating principles evidenced in reporting, the traits the hiring bar selects for, the two-sided employee experience, and who is likely to thrive versus burn out. The platform ingests from dozens of health information networks, normalizes into FHIR, deduplicates, enriches, and runs an AI layer that surfaces suspected conditions, HEDIS care gaps, and clinical summaries — "answers, not just records," per the company's own framing. Customers including Amazon One Medical, Sollis Health, Color Health, and Brightside Health have gone from contract to production in days, not quarters. But speed is gated by a deliberate counterweight: General Counsel Matt Davis-Ratner investigates every prospective customer organization, scrutinizes onboarding call attendees, and rejects access when the use case doesn't meet the bar. "We built this level of scrutiny into our process from the beginning, because healthcare data demands the highest level of protection." The company achieved HITRUST r2 certification in 2026, adding to SOC 2 Type II, HIPAA BAA, and AES-256 encryption, compliance work that runs in parallel with feature velocity.
Quarterly off-sites provide the only fixed planning cadence the company advertises. Between them, work organizes around the open-source repo, customer escalations, and the expanding AI/ML roadmap funded by the $26 million Series A led by Matrix's TJ Parker, as PR Newswire reported. Co-founders CEO Dima Goncharov and COO Colin Elsinga set direction; the in-house legal function gates risk; engineers decide implementation. There is no public evidence of OKRs or RACI matrices. The operating principle: hire owners, make the code auditable, and let the latency targets enforce discipline.
Operating DNA: Open Source as Competitive Wedge
Metriport's operating DNA traces directly to its founders' frustration with healthcare's closed systems. Elsinga and Goncharov, who had known each other for over 15 years before quitting their software engineering jobs in 2021, entered Y Combinator's S22 batch with a consumer health app. They pivoted to B2B after discovering how painful EHR integrations were, and how few companies were tackling the problem with an open-source, non-proprietary approach. "We realized that there was so much work to be done in this space to make the data more accessible and that hardly anyone in the space was working on an open source, non-proprietary solution," Elsinga told TechCrunch in December 2022. "Since we've always been mission-driven founders, having previously built a consumer health app, we decided to go after this larger problem with the goal of democratizing access to healthcare data and ultimately improve patient health outcomes."
That mission manifests in three interlocking principles the founders have stated repeatedly: transparency, reliability, and security through openness. Elsinga described the open-source decision as a rejection of the "black box" model that dominates health tech: "Through Metriport's open-source software it provides transparency into how everything is built, so companies can build on top of Metriport's solution and innovate, rather than having to reinvent the wheel every time." The team frames open source as "immortal code" — if a closed-source vendor fails, customers lose everything; with Metriport's approach, clients retain the ability to self-host critical infrastructure. Security follows the same logic: external audits catch vulnerabilities faster than closed-source vendors, who may not disclose issues promptly. "We created Metriport with open source code because the decisions around how patient information is managed and transformed are too important to trust to a black box," the company stated in its August 2026 Series A announcement.
A fourth principle — rigorous vetting — operates as a cultural constraint, not just a compliance checkbox. "We do deep diligence on every organization that wants to access the healthcare exchange data networks via Metriport. We thoroughly investigate the company, conduct a comprehensive vetting process, and pay attention to who's actually in the room during onboarding calls," General Counsel Matt Davis-Ratner wrote in the same announcement. That discipline earned HITRUST r2 Certification in 2026 and drew explicit praise from investor Parker, who noted the team "pairs exceptional technical execution with an exceptional level of customer service and compliance rigor that's built into how they do business."
Internally, the engineering culture reflects a deliberate rejection of corporate hierarchy. The team operates with "high autonomy, minimal bureaucracy, and a strong hacker mentality," according to a 2026 interview guide published by Dataford. Engineers own projects end-to-end (design documents, v0 in staging, pilot feedback, production v1) without handoffs to separate QA or release teams. The guide emphasizes "pragmatic focus on customer value over architectural over-engineering" and "simple, scalable, and maintainable solutions, prioritizing speed of execution and high ownership over rigid processes." Competence outweighs pedigree: "Metriport values competence over prestige. Focus on demonstrating your practical building capabilities and problem-solving skills rather than relying on pedigree or past company names." Self-direction is expected; candidates are asked for concrete examples of identifying problems and shipping fixes without manager prompting.
The founders also articulate a disruption mindset rooted in industry stagnation. When asked why no one had built this already, Goncharov told TechCrunch: "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. That time is now in the healthcare data space, we know this needs to be built, and we'll be the company to spearhead those efforts, setting industry standards along the way." That ambition appears in the company's stated north stars: "One platform for every workflow" and "Built for the scale of U.S. Healthcare" — phrasing that signals they view the current fragmented environment as a temporary condition they intend to replace.
The Hiring Bar: Entrepreneurial Builders, Not Ticket Closers
Metriport's hiring bar selects for a specific intersection of technical depth, entrepreneurial wiring, and pragmatic execution, traits that map directly to the company's lean, engineering-heavy composition and the messy reality of healthcare data integration. The team is largely comprised of former founders, a profile the careers page highlights explicitly: "an engineering-heavy team of former founders shipping infrastructure that matters." The interview process surfaces people who operate like them: high autonomy, high ownership, low tolerance for bureaucratic overhead.
The signal starts with how the company frames the role. A software engineer at Metriport is described not as an individual contributor writing code but as an "entrepreneurial builder charged with solving one of healthcare's most persistent challenges: patient data interoperability." That language appears in the company's own interview guide and reflects a deliberate filter: they want engineers who think in product outcomes, not ticket closure. The work spans modernizing 1990s-era hospital TCP protocols, building transformation engines that turn legacy messages into modern webhooks, and applying LLMs to structure freeform clinical notes. Each of those problems demands someone who can work through ambiguity without a spec sheet.
Competence over prestige is an explicit principle. The evaluation avoids generic algorithm puzzles in favor of practical assessments that mirror daily work — a hands-on coding exercise and a system architecture deep dive where over-engineering is penalized. "Metriport favors simple, pragmatic architectures that work reliably over complex, highly-abstracted systems that are difficult to debug," the guide notes. That preference reveals a hiring bar that rewards judgment over cleverness.
The process itself tests alignment with a high-intensity, high-ownership environment. It opens with a conversation with a founder or senior engineer to gauge "entrepreneurial drive and mutual expectations," then moves through technical evaluations that emphasize velocity and customer-value trade-offs. The final stages weight team collaboration and problem-solving under ambiguity heavily, signaling that the company treats cultural alignment as a technical requirement, not a soft-skills checkbox. Candidates who need structure, handoffs, or permission to ship tend to self-select out.
Mission motivation matters concretely. Scoutify's profile notes that people who thrive at Metriport are "motivated by impact on patient lives" and have "patience with regulatory requirements." The healthcare context imposes long sales cycles, compliance overhead, and integration friction with legacy systems that don't forgive move-fast-break-things posturing. The hiring bar selects for engineers who can sustain velocity inside those constraints, people who treat regulatory complexity as a design parameter, not a blocker.
First-party board data shows equity is a meaningful component of every offer. That range reflects a company paying for senior judgment and autonomy, not junior throughput. The most-hired roles over the last 90 days (eight software engineers, four security engineers, four business/revenue operations analysts) confirm the engineering-weighted, builder-first composition. Open requisitions on Zero G Talent's board include Staff Software Engineer, Staff Data Engineer, Senior Software Engineer, Senior Data Engineer, Account Executive, and Head of Customer Success, all based in San Francisco.
| Role | Salary Band | Source |
|---|---|---|
| All roles (aggregate) | $120,000–$260,000 (median $185,000) | First-party board data (14 roles) |
| Senior individual-contributor roles | $180,000–$220,000 | Zero G Talent board |
| Staff-level & executive-track positions | $200,000–$275,000 | Zero G Talent board |
| Staff Data Engineer | $200,000–$260,000 | Profile analysis (Zero G Talent data) |
| Senior Software Engineer | $180,000–$220,000 | Profile analysis (Zero G Talent data) |
| Account Executive | $200,000–$275,000 | Profile analysis (Zero G Talent data) |
| Head of Customer Success | $190,000–$250,000 | Profile analysis (Zero G Talent data) |
In practice, the bar filters for people who have already operated at the edges of ownership: former founders, early engineers at high-growth startups, or developers who have shipped complex systems end-to-end. The company's open-source posture (both APIs are open source) also selects for engineers comfortable working in public, accepting community contributions, and treating transparency as a competitive advantage rather than a risk.
The result is a hiring bar that reads less like a checklist and more like a self-selection mechanism: if you need a spec to start, if you optimize for architectural purity over shipping, if you expect a dedicated DevOps team to run your code, or if you're allergic to healthcare's regulatory gravity, the signal mismatch shows up fast. The people who pass through are the ones who treat the mess as the job.
The Profile That Thrives — and the One That Burns
The board data shows roles clustered at the Staff and Senior levels across engineering and data, with an Account Executive and Head of Customer Success rounding out the go-to-market side. Salary bands signal that the company pays for autonomy, not potential. In a lean organization, that autonomy is structural: there is no layer of middle management to absorb ambiguity, no abundant headcount to parallelize work. The person who thrives treats that absence as freedom rather than a gap.
Healthcare data interoperability, Metriport's core domain, imposes its own filter. The work sits at the intersection of FHIR standards, legacy EHR integrations, and regulatory frameworks that do not tolerate "move fast and break things" when the thing breaking is a patient record. The hiring bar, as reflected in the seniority of open roles, selects for people who have already navigated that friction elsewhere. A Staff Data Engineer is expected to design pipelines that handle messy, incomplete, non-standard inputs without constant product clarification. A Senior Software Engineer owns features end-to-end, including the unglamorous work of transforming legacy messages into modern webhooks. The thrivers are the ones who find that mapping intellectually satisfying rather than bureaucratic.
The go-to-market roles tell a parallel story. The former, selling into health systems and digital health companies needs the technical fluency to speak credibly with CTOs and integration leads, not just procurement. The latter inherits a function where "success" means the customer's integration stays live through EHR version upgrades, schema changes, and organizational turnover. Both roles demand a tolerance for long, technical sales cycles and the patience to guide clients through implementation details that would be abstracted away in other B2B software. People who need quick wins or clear quarterly scoreboards tend to churn.
Burnout at Metriport, when it happens, typically traces to a mismatch between the individual's need for structure and the organization's reliance on self-direction. The company's lean scale means that on-call rotations, incident response, and cross-functional prioritization fall on the same people building the product. The Staff Engineer who designed the data pipeline is also the one debugging why a specific hospital's ADT feed stalled. For engineers who have operated in larger orgs with specialized support functions, that breadth can feel like scope creep. For those who joined expecting mentorship density, the ratio of senior-to-junior staff offers little of it; the board data shows no junior roles posted. The culture rewards the person who writes the design doc, builds the feature, monitors the deployment, and follows up with the customer success team on adoption metrics, all in the same week. It penalizes the person who waits for a ticket to be groomed, a spec to be finalized, or a decision to be made by committee.
What the Outside World Sees
Public employee-review data for Metriport is sparse. Glassdoor, Blind, and comparable platforms return fewer than a handful of reviews — most undated, none attributed to named individuals — so this section relies on the signals that do exist: first-party hiring activity, founder statements about operating principles, and customer feedback that indirectly reflects on the team behind the product.
Customer references provide the only external, named validation of the team's day-to-day execution. TJ Parker, general partner at Matrix and lead investor in the 2026 round, said: "I see dozens of consumer health companies every year, and the best ones are increasingly working with Metriport. This team exemplifies the exceptional execution, service, and compliance rigor he previously highlighted." Victor Sadauskas, CEO of Kivo Health, noted in 2023 that "Working with Metriport is exceptional as they provide engineering and onboarding support, allowing us to quickly automate our patient record retrieval efforts." Dr. Scott Braunstein, CMO of Sollis Health, described in 2026 how Metriport helped his physicians surface a years-old operative report that changed a patient's treatment plan.
What's missing is the internal perspective: how engineers experience the open-source mandate, whether the compliance review process feels like guardrails or gatekeeping, how the lean headcount translates into on-call load or scope creep, and whether the mission narrative holds up during crunch periods. The absence of named, dated employee reviews means candidates should treat the founder and customer signals as directional, not definitive. The answers will reveal more than any aggregated rating.
The Clock Keeps Running
The 100 million daily requests don't pause for process debates. Neither does the vetting call that rejects a prospective customer. Metriport's culture is the sum of those choices — made by owners who ship, not waiters who ask permission. The next quarter's off-site will set new targets. The code will keep running.
Working in AI? Zero G Talent tracks the openings: see every open Metriport role, browse AI jobs, the companies hiring, and the people building the field.