SYMMVIAMEDICINE REIMAGINED
CareersOpen nowEngineering

Founding Senior Product Systems / Platform Engineer

Own the platform spine: backend architecture, identity, permissions, messaging, billing, workflow, and the migration path to a stronger platform core.

Team

Engineering

Location

US hybrid or remote, depending on qualification

Experience

4+ years, or equivalent ownership of real production systems

About Symmvia

Symmvia is building a high-trust care platform across public web, authenticated web, and a patient mobile app.

The product includes identity, permissions, billing, messaging, booking, provider workflow, and the data infrastructure required to make the system smarter over time.

We care about clear systems. Auditability, access control, operational clarity, and careful product design matter as much as speed.

About the role

This is the first foundational engineering hire. You will help define how the platform actually works under real operating pressure: how it ships cheaply now, how patients sign in, how providers work, how permissions are enforced, how subscription and billing state changes over time, and how the system can migrate cleanly to a stronger AWS-native core as regulated workflows become real. We are looking for someone who can own a real system, not just ship isolated tickets.

In this role, you will
  • Own core product and platform architecture across patient, provider, and admin surfaces.
  • Define service boundaries that let the company ship quickly now without creating migration debt later.
  • Design domain models for users, subscriptions, bookings, threads, messages, consents, and audit events.
  • Build and harden auth, RBAC, and access-control boundaries across patient, provider, support, and admin roles.
  • Own queues, async workflows, secrets handling, observability, and environment separation at the platform layer.
  • Implement workflow-heavy areas such as messaging, billing state, provider queues, and exception handling.
  • Work directly with the founder on sequencing, tradeoffs, and the long-term platform shape.
  • Set a high engineering bar for clarity, correctness, and pace.
You might thrive if you
  • You care more about whether systems work than whether they sound impressive.
  • You have built high-trust software where permissions, workflows, and auditability mattered.
  • You can move across product, backend, cloud, and operational reasoning without losing rigor.
  • You like owning a product surface end to end rather than waiting for someone else to define everything first.
  • You can help a company build cheaply now without painting it into a corner later. Experience in healthcare, fintech, identity, or another regulated domain is strongly preferred. Next.js is preferred, not required.
Required capabilities
  • Strong backend engineering in TypeScript and/or Python.
  • Strong backend and API design judgment.
  • Strong PostgreSQL and relational data-modeling ability.
  • Direct AWS production experience is strongly preferred.
  • Experience with IAM, least privilege, and secure credential handling.
  • Experience building permissions-heavy or workflow-heavy systems.
  • Experience with queues, async processing, observability, and infrastructure as code.
  • Evidence of real production ownership, not just feature implementation.
  • Ability to reason clearly about failure modes, recovery paths, and system boundaries.
Compensation

Competitive for the role.

How to apply

Send us one thoughtful email.

If this role fits, email us directly. Please include the items below. If something does not apply, say so plainly. We care about signal, not performance.

Submission checklist
  • First name
  • Last name
  • Voluntary self-identification
  • Email
  • Country
  • Phone
  • PDF of your resume or CV (required)
  • A few bullet points that best evidence exceptional ability (required)
  • How to pronounce your name, if applicable
  • LinkedIn profile
  • GitHub URL
  • Personal website
  • Publications
  • Google Scholar profile, if applicable
  • Preference for working in person versus remote
  • Earliest date you can start
  • Any deadline or timeline considerations we should know about
  • A short answer to: Why Symmvia?
  • Optional cover letter
  • Anything else you would like to share, including a relevant project