Senior Product Engineer (TypeScript) - Platform

Vocca; Paris; Hybrid; EUR 70,000 - 90,000; Full time

Benefits offered by this job

BSPCE

Hybrid work

Paris office

Job summary

Vocca, Paris-based, is building AI voice agents that connect patients and doctors. You will shape the product and its architecture, focusing on a scalable scenario engine and a zero-developer onboarding flow for clinics.

You’ll lead a fast-growing engineering squad, define how we work, and own features end to end from spec to production, collaborating with ops and sales to deliver value to thousands of medical staff.

Qualifications

• 5+ years building full-stack products in production.
• Strong in TypeScript, backend and frontend.
• You can turn a manual process into a product and explain technical decisions clearly.

Responsibilities

• Architect the scenario engine and configuration model.
• Own self-serve onboarding from backend to dashboard.
• Own the clinic dashboard for day-to-day use.
• Contribute to the platform's technical roadmap and decisions.

Skills

Full-stack development

TypeScript

System design

Backend and frontend

Tools

Node.js

PostgreSQL

Python

Monorepo

Job description

Our team shared's mission is deploy AI agents to transform how patients and doctors connect

We believe healthcare shouldn't be defined by missed calls, endless waiting lines, and overwhelmed staff. Patients and professionals deserve better.

Vocca builds AI voice agents that answer every call instantly, schedule and reschedule appointments, and free up staff to focus on what matters most: care.

Already trusted by 3500+ providers, we’re transforming the patient-provider relationship, one call at a time.

Want to shape the future of healthcare?

Join us !

• Discover our company culture and values

• Here is a product Demo

• Meet the team

• Article on our $20M Series A, led by Norrsken with the founders of Alan and Datadog

The problem

Every medical centre has its own rules. Who can book what, with which practitioner, at what time, what to do with an urgent case at 6 pm. Today these rules live in prompts and in the heads of our ops team. Each new clinic takes hours of manual work, and the ops team is the bottleneck of our growth.

We are building the platform that removes that bottleneck. A scenario engine where the behaviour of the agent is structured configuration, not free text. A self-serve onboarding where a clinic connects its software and sets itself up. A dashboard where the medical staff stop executing and start supervising: the agent handles the volume, humans check what matters.

This is the difference between selling a service and selling a product. It decides how fast Vocca can grow and how many clinics one ops person can support. The long term vision is simple: a clinic signs, connects its software and is live within days, without a single developer involved. You would be building that.

What you will own

The product and its architecture

• The architecture of the scenario engine and the configuration model. One product that handles the rules of thousands of medical centres without becoming a swamp.

• The self-serve onboarding, from the backend to the dashboard. Today a clinic deployment went from days to under an hour thanks to internal tooling. The next step is zero developer ticket on a standard onboarding.

• The dashboard our clinics use all day. Fast, reliable and clean enough that a medical secretary prefers it to the phone. We take frontend quality seriously and we have just created a product designer role to raise the bar.

• The technical roadmap of the platform, built with the product manager and the ops team. You decide what we build first, what we build simply and what we do not build.

The quality bar

• What “done” means on the platform: tests, reviews, monitoring, and what we check before a change reaches 1,000 medical staff.

• Reliability in production. When the dashboard or an onboarding breaks, you own the fix and the reason it does not happen again.

The team

• The engineering team is growing fast and will organise in squads. You will define how this one works: reviews, documentation, technical decisions.

• You will work daily with a confirmed engineer (2 to 5 years of experience) who joins the platform team at the same time. Their growth is part of your job.

• You will take part in hiring the next engineers of the team, and you will help onboard them.

• You will be one of the most experienced engineers in the company and we will expect you to act like it.

Stack

TypeScript everywhere, backend and frontend (Node, monorepo), PostgreSQL, a design system written in code.
We are migrating our last Python services to TypeScript over the coming months.

How we build

• We use AI seriously. Agents in every workflow, Claude Max provided. A migration estimated at 3 months was done in 2 weeks.

• For this role we are looking for the senior who frames the work first, sets guardrails and reviews carefully.

• We ship the version that works, then fix the last 1% when it shows up. With AI, this trade off is much cheaper than before. But the judgment about what not to touch is yours.

• Every change lands in front of more than 1,000 medical staff who use the product all day. We talk every day with the ops team that deploys clinics and the sales team that sells the product.

Who does well here

• 5+ years building full-stack products in production, mostly in startups or fast growing companies where you had to decide with incomplete information.

• Strong in TypeScript, backend and frontend. A real eye for interface quality and the discipline to follow a design system.

• You have turned a manual process into a product before, or you really want to.

• You had good practices before AI: solid system design, clean refactoring and a good nose for the risks of generated code that nobody tested.

• You can say no, reduce the scope and explain a technical decision to a founder in two minutes.

What we expect from you

First week

• Get onboarded on the stack.

• Ship your first improvement on the dashboard.

First month

• Own one feature end to end, from the spec with the ops team to production.

• Write down how the platform should evolve.

First 3 months

• The first version of the scenario engine is in production.

• A standard clinic can be onboarded without a developer ticket.

6 to 12 months

• Most new clinics are live within 7 days.

• Clinics configure their own rules in the dashboard.

• The platform team has its own way of working, and you have hired at least one engineer into it.

Process: 4 steps, fast

1. 45 min with Nans (Talent).

2. 45 min with Pierrick, Head of Engineering.

3. 1h30 in our office with the engineering team, with live coding without AI and a real conversation about product architecture.

4. 30 min with Hugo, CTO.

Then references and an offer. When the match is obvious, we have made an offer in 24 hours. You get feedback at every step.

Practical

• Paris, rue d'Alexandrie (Sentier), new offices.

• 70-90K + BSPCE.

• Hybrid 3 days at the office.

• Claude Max provided.

We aim to keep the process within 30 days. You'll receive continuous feedback throughout.

Why should you join Vocca?

• An entrepreneurial adventure , with a supportive, high-energy, execution-focused team

• A product already live , with delighted customers in a fast-growing market (healthcare automation, voice AI)

• A true scaling phase , with everything still to build

• Real responsibilities from day one

We hire people, not roles.

If you're excited about our opportunities but don't check every box, we'd love to hear from you. Everyone, no matter how underrepresented, should feel free to apply as it can only bring learnings or success. If you identify yourself as a woman : Did you know that research shows women often apply only when meeting 100% of requirements?