Founding Integrations Lead

The Role

Healthcare data is fragmented by default. Every provider, payer, EHR, referral source, and clinical system speaks a slightly different language. For Frontera to scale, both as a care delivery organization and as a technology platform, that fragmentation has to disappear behind a reliable, extensible integration and data layer.

The Founding Integrations Lead will build that layer.

This role sits within our ML & Data organization because we don't view integrations as implementation plumbing. The systems we connect determine what data Frontera can access, how cleanly we can understand it, and ultimately what our product and AI systems can do with it. Every integration expands the number of organizations Frontera can work with, and adds breadth, fidelity, and context to the clinical data underlying the platform — the same longitudinal dataset that comes from operating real care alongside our own platform, not abstract transaction data.

This is a highly hands-on technical leadership role. You'll spend the vast majority of your time building, deep in the code and shaping architecture decisions. From day one, you'll also lead a small team: two engineers to start, growing as integration volume and complexity increase. This is people leadership from the outset, not something added later as the team happens to grow.

What You'll Do

• Lead the integrations team — hire, onboard, and set the technical bar and working norms for the function, starting with two direct reports and growing the org as scope increases
• Own the integration architecture — design how Frontera connects with external healthcare systems (EHRs, partners, and other data sources), establishing reusable patterns and tooling rather than one-off builds for each new organization
• Bring an AI-informed lens to the work itself — use agentic tooling to accelerate data mapping and schema discovery across new partner systems, rather than treating each integration as a fully manual build. Judgment on when to automate discovery versus handle a partner's edge cases by hand is part of the technical craft this role requires
• Shape the unified data model underneath those integrations, in close partnership with ML/Data, Product, Engineering, and Clinical Operations
• Own technically complex integrations end-to-end — discovery, data mapping, implementation, reliability, observability, and long-term maintainability
• Set clear standards for data quality, error handling, monitoring, and operational ownership as integration volume grows
• Work directly with external technical teams and internal stakeholders on problems where the specification doesn't yet exist — you'll be expected to help define the right answer
• Coach the engineers on your team through the same kind of ambiguous, partner-facing problems this role itself requires judgment on
• Help determine what should become platform capability versus what should be solved pragmatically for a specific partner or workflow

Why This Matters

Better integrations mean faster onboarding of new organizations, less operational friction for clinicians and teams, and a more complete view of the care journey. They also improve the quality and usefulness of the data Frontera can learn from — because we operate care directly, that data reflects real clinical workflows and outcomes. As that dataset grows, it becomes increasingly important to how we evaluate care models, build AI systems, improve workflows, and differentiate the platform. This role — and the team behind it — is one of the foundational technical layers behind that scale strategy.

Qualifications

• 6+ years of experience in backend-leaning engineering, with strong experience building APIs, integration systems, or distributed backend services
• Experience leading, mentoring, or managing engineers — comfortable owning both the technical direction and the people side of a small, growing team
• Experience building and scaling integration platforms, APIs, or data pipelines in production environments
• Strong understanding of system design, distributed systems, and data flow between services
• Experience working with third-party integrations (e.g., healthcare systems, EHRs, SaaS platforms, or partner APIs) is highly preferred
• Comfortable operating in fast-paced, ambiguous, zero-to-one environments — moving between architecture, hands-on implementation, partner conversations, and product tradeoffs
• Familiarity with agentic or AI-assisted tooling for tasks like schema mapping, data discovery, or accelerating integration work is a strong plus
• Strong product mindset — focused on building practical, reliable solutions that deliver real user and business impact
• Excellent communication skills and ability to drive alignment across technical and non-technical stakeholders
• Interest in healthcare and/or experience working with regulated data (HIPAA, PHI) is a plus

Compensation

We are open to candidates across multiple levels for this role. Final level and compensation will be determined through the interview process based on experience, technical depth, and scope.

Expected Salary Range in Denver: $160,000 to $220,000
Expected Salary Range in San Francisco: $175,000 to $240,000