SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Papa is a venture-backed healthtech company founded in 2017 that pairs older adults with trained companions to reduce loneliness and improve health outcomes. The company is backed by top-tier investors including Canaan, Tiger Global, SoftBank Vision Fund 2, and others.
You'll join Papa Community, a 0-to-1 venture within Papa based in San Francisco building virtual care for seniors. This is a founding engineering role with significant autonomy and impact. You'll work alongside Staff Backend Engineers and report directly to the Community GM, with mentorship from Papa core's engineering leadership.
Key responsibilities include:
**Platform Development**: Help build and scale Papa Community's proprietary operational platform for the care team, a multi-quarter initiative with substantial growth potential.
**Healthcare Integrations**: Navigate complex healthcare data standards (FHIR, HL7, X12) and build resilient API integration patterns connecting EHRs, care management platforms, revenue cycle management systems, and patient communication tools.
**Revenue Cycle Management**: Work on RCM vendor integration, claims data pipelines, denial handling, and patient responsibility workflows as billing volume scales.
**Platform & Tooling**: Extend platform capabilities including transactional email, customer support tooling, and member/internal-facing systems.
**Problem Ownership**: You won't implement pre-scoped tickets—you'll own business problems and have latitude to determine the best technical solutions. Partner directly with the GM on product decisions and technical priorities.
What makes this unique: You get startup velocity and autonomy (decisions in days, not weeks) while leveraging Papa's established infrastructure, deployment pipelines, security compliance, and DevOps support. You'll influence architecture, technology choices, and engineering practices that define Community for years. The role balances shipping speed with technical judgment—knowing when to build for scale versus iterate quickly.
Challenges include navigating healthcare complexity, working in a high-autonomy environment with open questions and minimal established process, and influencing stakeholders while owning outcomes.
