Application Engineer
Posted 30 Jul 2026
Advertised as “Staff Application Engineer”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 8+ yrs
- Management level
- Individual contributor
- Employment
- Remote
- Contract
- Full-time
No salary listed for this role.
About CertifyOS
CertifyOS is building the data infrastructure that powers modern healthcare.
Today, healthcare organizations rely on fragmented and outdated provider data. This creates unnecessary administrative work, regulatory risk, and higher costs across the system. We’re solving that problem.
Our API-first platform automates provider licensing, enrollment, credentialing, and network monitoring by connecting directly to hundreds of primary data sources. We help healthcare organizations maintain accurate, compliant, and reliable provider networks at scale.
Our vision is simple: One API. One provider ID. Frictionless provider data.
We’re backed by leading investors and built by a team with deep experience in provider data systems. At CertifyOS, we value authenticity, accountability, collaboration, results, and openness to feedback. We’re building a high-ownership team focused on solving real infrastructure problems that impact millions of patients.
About the Role
We’re looking for a Staff Software Engineer to own the application layer of the CertifyOS platform the full-stack systems that translate our provider data infrastructure into products that payers, health systems, and digital health companies actually use.
This is a Staff-level role with real architectural scope. You won’t be handed a spec you’ll define how the application layer is structured, how the frontend and backend evolve together, how API contracts are designed for external consumers, and how the engineering practices that govern application development scale with the team. You’ll drive technical strategy, shape engineering culture, and set patterns that other engineers build on.
Problems You’ll Solve
CertifyOS is an API-first platform with an increasingly complex product surface. As we scale more integrations, more enterprise customers, more AI-powered workflows the application layer has to evolve without accumulating the kind of technical debt that kills product velocity.
How do you build a frontend that scales with product complexity without becoming unmaintainable? React and TypeScript at the component level is straightforward. At Staff level the problem is harder: design systems, state management strategy, API contract alignment between frontend and backend, and a component architecture that lets a growing team move fast without stepping on each other.
How do you design API contracts that serve both internal product teams and external enterprise consumers? CertifyOS APIs are external-facing products, not just internal plumbing. You’ll define versioning strategy, resource modeling, error semantics, and pagination patterns that work for enterprise integrations with complex compliance requirements and evolve without breaking existing consumers.