causaLens
causaLens

Lead Forward-Deployed AI Engineer

$130–200kUnited States; Washington, DCRemoteSeniorFull-time

Posted 18 days ago

The role in short

Lead hands-on technical delivery of production agentic AI systems for pharma and life sciences customers, working onsite to build integrations and guide engineering teams.

Job description

Why causaLens

  • The next Accenture will have no employees. We are building it.

  • We are partnering with both sides of the industry: helping CROs, CCOs, consultancies and BPOs reimagine how they deliver services, and partnering directly with pharma companies of every size, from mid-market to global leaders.

  • We build Digital Workers: pre-skilled AI workforces that do knowledge work inside the customer's own environment and are paid for the outcome, not the seat.

  • We build with pharma services. Our Digital Workers already run inside two of the five largest CROs, helping partners like Syneos Health and Parexel deliver more for their pharma clients. Read our press release with Syneos' Global Head of Commercial Product: link

  • AI tools alone have not moved the P&L. MIT found 95% of organisations saw no return on $30 to 40B of GenAI spend. We sell finished work with SLAs, not software, so the value shows up in results.

  • Pharma runs on trusted service partners. About half of drug development is outsourced, and $300B+ of branded sales lose exclusivity by 2032. Digital Workers give that ecosystem the extra capacity and cost efficiency the next decade demands.

  • Life sciences is our largest sector, and where we are doubling down. Millions in ARR, flagship logos including J&J, Syneos Health and Parexel, with more of the largest CROs and brands onboarding now.

  • $51M raised from top VCs and angels, including the CEO of Revolut. 3x ARR growth and 160% net revenue retention last year.

  • Unique IP that regulated enterprises trust: Our Digital Worker harness incorporates unique, proprietary reliability technology (causalens.com/the-reliability-features) and causal reasoning (causalens.com/causal-reasoning-lab).

  • Ownership. Help establish local technical delivery in the US, working directly with customers and collaborating with our UK engineers.

The Culture

Our culture values intellectual rigour, ownership and the primacy of winning. Two articles that define how we think:

Job requirements

The Role

Lead hands-on technical delivery for US pharma and life sciences customers, operating independently onsite and coordinating with UK engineers and Value Engineering.

What you'll bring

  • Personal ownership of production AI systems using Python, LLMs and agentic workflows, with sound software engineering and measurable business impact

  • Independent client delivery: lead onsite discovery, clarify requirements, resolve technical blockers and communicate risks, with limited day-to-day supervision

  • A track record of leading a small engineering team or enterprise delivery workstream from discovery through production, staying hands-on and accountable for technical outcomes

  • Experience evaluating and operating reliable systems. Pharma, life sciences or regulated-enterprise delivery experience is preferred

  • Based within practical reach of a named US pharma hub and willing to work regularly at customer sites

What you'll do

  • Lead customer discovery and turn workflows into feasible scope, technical designs and measurable acceptance criteria

  • Build and integrate agentic systems with enterprise data and APIs; own evaluation, failure handling, testing and deployment

  • Own technical delivery through production and customer acceptance, partnering with Value Engineering on scope, dependencies and progress

  • Guide engineers, review code and designs, collaborate with UK colleagues and turn delivery lessons into reusable approaches

What you'll not do

— R&D in the lab, isolated from customers

— Product or platform development. There is a separate team internally for this

Benefits

We care about our people’s lives, both inside and outside of causaLens. Beyond the core benefits like competitive remuneration and a great work-life balance, we offer the following:

  • 20 days of paid holiday, plus bank holidays

  • carry over/sell holiday options (up to 5 days)

  • Share options

  • Referral bonus program

  • Learning and development budget

Logistics

  • Recruiter Screen

  • Hiring Manager / Team Interview (30 mins): Deep dive into past projects, recent codebases

  • Take-Home Challenge (3 hours): Testing structured thinking and practical coding/problem-solving.

  • "Day 0" Onsite (Hammersmith): 3 x 30-minute technical interviews.

  • Founders/Exec Interview

If you require accommodations during the application process or in your role at causaLens, please contact us at talent@causalens.com

Prep for this interview

5 questions likely to come up at causaLens, each matched to a line in this posting.

  1. 1Discovery and scoping
    They wrote: “Independent client delivery: lead onsite discovery, clarify requirements, resolve technical blockers and communicate risks, with limited day-to-day supervision”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  2. 2LLMs, RAG and agents
    They wrote: “Personal ownership of production AI systems using Python, LLMs and agentic workflows, with sound software engineering and measurable business impact”

    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.

  3. 3Integrations and APIs
    They wrote: “Build and integrate agentic systems with enterprise data and APIs; own evaluation, failure handling, testing and deployment”

    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. 4Ownership and working with customers
    They wrote: “Ownership. Help establish local technical delivery in the US, working directly with customers and collaborating with our UK engineers.”

    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.

  5. 5Travel
    They wrote: “Based within practical reach of a named US pharma hub and willing to work regularly at customer sites”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

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

causaLens

$130–200k · Remote

Apply