Parallel (hospital admin AI)
Parallel (hospital admin AI)

Forward Deployed Engineer

ParisHybridSeniorFull-time

Posted Sep 7, 2026

The role in short

Lead on-site deployments of AI, RPA and computer-use agents at hospitals, building integrations and adapting the platform to each facility.

At Parallel, we build AI agents that help healthcare organizations automate their administrative processes and unlock additional revenue, starting with medical coding.

Today, up to 25% of healthcare spending is lost to manual, repetitive administrative tasks. Legacy software hasn't helped: it has made work slower, more complex and more frustrating for care teams.

We believe AI agents can change this. Our technology combines large language models with system-level automation to do real work inside existing hospital tools. No integration, no disruption.

Our first agent automates coding and frees up time for medical teams to focus on patients.

We launched in 2024 and already have 800+ customers and a team of 30+ people. We are backed by top-tier investors (Index Ventures, Y Combinator, Hexa, Frst, Kima Ventures, Better Angle and the CEO of Mistral AI), and this is just the beginning.

The future of healthcare isn't just digital, it's automated. Come help us build it!

The role

Context

Parallel deploys AI, RPA and computer use solutions in healthcare facilities. We're looking for someone who can technically lead these deployments on the ground, adapting to real-world environments and to each facility's specific constraints. Someone who can be the technical interface between the Parallel platform and our customers, and lead deployments end to end.

What you'll do

  • Understand the IT infrastructure of each facility.
  • Adapt our platform to their constraints: interfaces, integrations, security, network architecture, on-premise deployments.
  • Unblock projects by working directly on the product when needed.
  • Identify and solve blockers, both technical and organizational.
  • Support customers through change management so they use Parallel effectively.
  • Help progressively define our deployment standards.

In your first months, you will have led and stabilized deployments at our customers' sites, built specific adaptations and integrations for each facility, and ramped up on our AI and RPA / computer use stacks, interoperability and on-premise infrastructure.

Who you are

  • You have at least 5 years of experience in full-stack development.
  • You graduated from a top engineering school.
  • You are proficient in Node.js and TypeScript (NestJS, Express, Prisma, Postgres) as well as React (TanStack, Tailwind).
  • You have already worked with LLMs and AI agents, on personal or professional projects (LangChain, Hugging Face).
  • You enjoy working directly with customers and know how to help non-technical users get to grips with a tool.
  • You are comfortable in complex, non-standardized environments and with infrastructure: networking, security, on-premise deployments.
  • You have already connected systems together.
  • You can quickly understand a problem, take ownership of it and find pragmatic solutions.
  • You are an engineer with a real feel for the field and for customers.

Our values

  • Play to Win: we're not here to just take part, deliver something "good enough" or simply enjoy the startup ride. We want to win. That means caring about results, moving fast and bringing the right intensity when it matters.
  • High Trust, High Standards: trust is our starting point. If you join us, it's because we believe you can own your scope and make good decisions. We don't want a company built on approvals, control and micromanagement. But trust comes with accountability: the more freedom you have, the higher the bar.
  • Low Ego, Hands-On: at Parallel, no one is above the work. No title, seniority or past success exempts anyone from getting involved in the actual work. Leading means taking responsibility, not distancing yourself from execution.
  • Don't Take Yourself Too Seriously: we take our mission very seriously, not ourselves. Building a company is intense. We want Parallel to remain a place where people enjoy spending time together, laughing, celebrating and giving energy to others. High standards and a good atmosphere aren't opposites: we want both.

Hiring process

  1. Call with the Hiring team (30 min)
  2. Call with Chris, CTO (30 min)
  3. Case study and interviews with Chris and Paul, the founders, at our office in Paris 2nd (2 hours)
  4. Reference checks

Why join us?

  • A problem that matters: reducing admin work in hospitals directly gives time back to care teams. The impact is concrete.
  • A different technical approach: agents that work on existing systems without heavy integration, a real competitive advantage that you put in place on the ground.
  • Real traction: seed and Series A ($20M with Index Ventures) closed in less than a year, 800+ customers and a team of 30+ people.
  • Strong investors and founders: Index Ventures, Y Combinator, Hexa, Frst, Kima Ventures, Better Angle and the CEO of Mistral AI; founders who come from Meta, McKinsey and Hublo.
  • A complete package: competitive salary and equity (BSPCE), Alan health insurance, Swile meal vouchers, Apple equipment, 50% of public transport covered.
  • A close-knit team: a team event every month and two offsites a year.
  • Our office: Paris 2nd arrondissement.
  • Flexibility: on average one day of remote work per week and one week of remote work per year.

We care about who you are, not just what's on your CV.
If you're drawn to what we're building but don't meet every requirement, we still want to hear from you. Studies show that women in particular tend to apply only when they meet 100% of the criteria. If that's you, please don't let that hold you back. We'd love to receive your application.

Prep for this interview

5 questions likely to come up at Parallel (hospital admin AI), each matched to a line in this posting.

  1. 1LLMs, RAG and agents
    They wrote: “You have already worked with LLMs and AI agents, on personal or professional projects (LangChain, Hugging Face).”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

  2. 2Cloud, deployment and security
    They wrote: “Adapt our platform to their constraints: interfaces, integrations, security, network architecture, on-premise deployments.”

    A bank wants our product inside their own cloud account, with no data leaving it. How do you approach it?

    How to answer

    Why they ask: Self-hosted and private-cloud deployments are common in regulated industries.

    1. Learn their rules early: network limits, approved services, review process
    2. Package the product so it installs the same way each time (containers, Terraform)
    3. Plan how you'll get logs and updates without touching their data
    4. Run a test install with them before the real one

    Tip: Talk about the conversation with their security team as much as the setup.

  3. 3Integrations and APIs
    They wrote: “We believe AI agents can change this. Our technology combines large language models with system-level automation to do real work inside existing hospital tools. No integration, no disruption.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  4. 4Coding
    They wrote: “You are proficient in Node.js and TypeScript (NestJS, Express, Prisma, Postgres) as well as React (TanStack, Tailwind).”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  5. 5Ownership and working with customers
    They wrote: “You can quickly understand a problem, take ownership of it and find pragmatic solutions.”

    Tell me about something you shipped that broke in production.

    How to answer

    Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.

    1. What broke and who it affected
    2. How you found out and what you did in the first hour
    3. The root cause, said plainly
    4. What you changed so it can't happen the same way again

    Tip: Pick a real one with a cost. Spend most of the answer on what you changed.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

Similar roles at other companies

Parallel (hospital admin AI)

Hybrid

Apply