Team
Engineering
CareersOpen nowEngineering
Founding Senior Product Systems / Platform Engineer (CTO Track)
Own the platform spine: backend architecture, identity, permissions, messaging, billing, workflow, and the technical direction that can grow into the CTO seat over time.
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 and the intended CTO-track role. You will help define how the platform actually works under real operating pressure: how it launches pragmatically, how patients sign in, how providers work, how permissions are enforced, how subscription and billing state changes over time, and how the core system matures as the company grows. The role also owns the technical architecture required for HIPAA-grade data handling, real clinic onboarding, and SOC 2-ready operations. We are looking for someone who can own a real product system, not just ship isolated tickets. For the right person, this role should compound into broader technical leadership as the company scales.
- Own core product and platform architecture across patient, provider, and admin surfaces.
- Define service boundaries that let the company ship quickly now without creating avoidable 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.
- Build the platform so HIPAA security requirements, audit logging, and SOC 2 control expectations are designed in early.
- 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, pace, and the future shape of the engineering organization.
- 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 want to earn technical leadership by owning real systems rather than managing from a distance.
- You can help a company build pragmatically 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.
- Strong backend engineering in TypeScript and/or Python.
- Strong API and system-design judgment.
- Strong PostgreSQL and relational data-modeling ability.
- Experience running production systems on AWS or another serious cloud platform.
- Experience with IAM, least privilege, and secure credential handling.
- Experience building and operating systems that handle PHI under HIPAA security and privacy constraints.
- Experience building in SOC 2-controlled, audit-ready, or similarly regulated environments.
- 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.
How to apply
Send us one thoughtful email.
If this role fits, email us directly. Include the items below. If something does not apply, say so plainly. We care about signal, not performance.
Submission checklist
Send the required items first. Add optional context only if it helps us understand the fit.
* Required
** Optional
Required
- Name
- Country
- Phone
- PDF of your resume or CV
- A few bullet points that best evidence exceptional ability
- 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
- Voluntary self-identification
- How to pronounce your name, if applicable
- LinkedIn profile, GitHub URL, personal website, publications, or Google Scholar profile (if applicable)
- Cover letter
- Anything else you would like to share, including a relevant project