Skip to content
Vocca

Lead Software Engineer, Integrations (TypeScript)

ParisHybrid · France
Staff · FullTime · Product & Engineering
POSTED 5 OCTVERIFIED 1D AGO
Apply Ask
Role
35 days opentrue age
Posted 5 Oct
Pay
€75k–€89kno pay posted
Market p25–p75
€75k–€89k
Paris · n=8 · 365d to 6 Nov
CompanyVocca →
21open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
9,307open · Staff Software engineering
Opened · 7d
+4725% of open
All software engineering
74,985open
All tracked boards · live 9 Nov · n=9,307
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

Opening the US market

The problem

Every medical practice runs on software that holds its calendar and its patients. There are dozens of different ones. Most were built twenty years ago and some have no API at all. To book an appointment during a call, our AI agent has to read and write in that software in real time, while the patient waits on the line. On several of these systems, Vocca is the only integrator in the world.

This is the work with the most direct impact on the business. A clinic whose software is connected to our agent does not switch. Retention, pricing power, our lead over competitors: it all depends on these integrations. Every software we cannot connect is a clinic we cannot sign.

The next step is writing back. Today the agent reads and books. Tomorrow it updates records in EHR, PMS and RIS systems, which raises the reliability bar a lot. In the US, we are opening the dental software ecosystem, with the compliance work that comes with it (HIPAA, SOC2).

There is no product manager on this scope. You would be the one deciding.

What you will own

The architecture of our booking layer. Today it is code written provider by provider, under pressure, partly in Python. It is becoming one unified layer in TypeScript that handles the rules of each medical centre, where adding a new software takes days, not weeks.

Speed and reliability at close to 1M calls a month. A call to a clinic software can take several seconds, and the patient cannot wait. You decide how we detect a booking failure in a clinic within 24 hours and what a healthy integration looks like.

The roadmap of your scope. You decide which software we connect first, with the sales, ops and support teams and the clinics themselves, and you prove it worked with a number: bookings that go through, failures caught, clinics signed.

The relationship with the software vendors, in France and in the US. The hard integrations are the ones nobody else wants to do. They are what makes Vocca hard to replace.

The team. You define how this scope works (reviews, documentation, technical decisions), you take part in hiring the next engineers and you help them ship in their first week.

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. You talk every day with the ops team that deploys clinics, the support team that hears when something breaks and, when it matters, the clinics and the software vendors themselves.

Stack

TypeScript everywhere (Node, monorepo), PostgreSQL, REST and SOAP APIs from software vendors. We are migrating our last Python services to TypeScript over the coming months.

Source · VoccaFirst seen 7 NovOriginal ↗