Skip to content
Vocca

Product Engineer (TypeScript)

ParisHybrid · France
FullTime · Product & Engineering
POSTED 6 OCTVERIFIED 1D AGO
Apply Ask
Role
34 days opentrue age
Posted 6 Oct
Pay
€47k–€91kno pay posted
Market p25–p75
€47k–€91k
Paris · n=25 · 365d to 6 Nov
CompanyVocca →
21open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
37,440open · Software engineering
Opened · 7d
+1,7755% of open
All software engineering
74,985open
All tracked boards · live 9 Nov · n=37,440
TypeScriptNode.jsPythonPostgreSQL

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 15 000+ 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 teaser

Eliott's interview for Welcome to the jungle

Eliott's quick interview for Speedinvest

Articles on our A round (techfundingnews, Maddyness, les echos, our blog)

Vocca in a few words

Vocca is an AI voice agent that answers 100% of the calls of medical centres. The patient calls, the AI books the appointment or answers the question, and the medical secretaries keep their time for the cases where a human is really needed.

$20M raised, with the founders of Alan and Datadog as investors

Close to 1 million calls a month going through the platform

More than 1,000 medical staff use our product all day

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. 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 scenario engine and its 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. Internal tooling already took a clinic deployment from days to under an hour. 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 follow a design system written in code.

Your features, end to end. From the spec with the ops team to production, and the fix when something breaks, with the reason it does not happen again.

How we build

Experimental, not R&D. You test, you prove with data, you ship. Challenging a decision means coming back with a result, not a debate.

Ship, then fix the last 1%. 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. The judgment about what not to touch is yours.

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

Close to the field. Every change lands in front of more than 1,000 medical staff. You talk every day with the ops team that deploys clinics and the sales team that sells the product.

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.

Who does well here

3 to 8 years building full-stack products in production, in startups that were growing fast.

You stayed long enough somewhere to see a system live, break and get better, and you learned from it.

TypeScript is your main language, backend and frontend, not a line on your CV. You have a real eye for interface quality and the discipline to follow a design system.

Source · VoccaFirst seen 7 NovOriginal ↗