You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Lyrebird Health

Staff AI Engineer (Agents)

  • Hybrid
  • 6+ years

Salary

Not stated

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

Each day in Australia, 10 people die from errors that could have been prevented. The causes are misdiagnosis, missing information, and clinicians deciding under extreme pressure. Much of this traces back to doctors spending 40% of their day on paperwork instead of with patients. The company is working on that problem.

The company turns real clinical conversations into accurate notes automatically. Its platform covers real-time ambient documentation, document management, workflow automation, integration with fragmented health systems, and patient and clinician communication. Thousands of clinicians across several disciplines use it daily in settings where accuracy and safety matter. The team is growing in Melbourne, the UK and Asia, and has a short window to set the standard for clinical AI in Australia.

An agent that gets a clinical note wrong creates a decision a doctor makes on bad information, so the systems you build determine how much time clinicians save and how much they can trust what they see.

Responsibilities

  • Build the agents behind the company's clinical AI, joining one of three areas: note generation, workflow automation, or EMR integrations. You own an outcome from start to finish, whether that is the note, the workflow that follows it, or the EMR connection beneath it. Clinicians act on every output, so it must be correct.
  • Own a product outcome end to end, such as activation and note quality, workflow conversion, or integration depth and reliability.
  • Design, build and run production agents, covering architecture, tool design, evals, rollout, and the failures that only appear in live clinics.
  • Write specs and evals before building, so quality and hallucination are measured rather than guessed.
  • Build reusable components so a new workflow or integration ships as configuration rather than a rebuild.
  • Work with product as a peer on what to build, and make the smaller product decisions yourself.
  • Work with clinicians, clinical safety staff, EMR vendors and enterprise customers to find problems worth solving.
  • Nobody hands you a spec. You find the problem, sit with the clinician who has it, and decide whether it needs an agent or plain deterministic code. Treat model improvements as a design input. Use AI tools to move fast, but hold all shipped code to your own standard.

Requirements

  • Hands-on experience building agentic systems, including at least one agent you took to production and owned through real use, failures and iteration.
  • A habit of writing evals while building, not afterwards, with the ability to explain how you defined good, what you measured, and what you changed.
  • Sound judgment on tool use, orchestration, context, guardrails and human-in-the-loop design, including knowing when not to use an agent.
  • Daily use of AI coding agents such as Claude Code or Codex, reviewing their output to the same standard as your own code.
  • Product judgment: you can explain what you chose not to build and why.
  • Practical experience with FHIR and HL7, ideally from integrations you have built by hand.
  • Experience in healthcare, SaMD or other safety-critical environments.
  • Time spent working directly with end users, ideally clinicians, to shape what gets built.
  • Familiarity with TypeScript and AWS.
  • The company encourages applications from people with underrepresented backgrounds in tech, even if they do not meet every requirement.

Conditions

The company is building a team that reflects the people its work serves, and wants everyone to feel safe, supported and able to thrive.

Where you’d work

Part of the week in the office

You can work from

  • Australia

About the company

Lyrebird Health

  • Industry: HealthTech

Office in Melbourne, Australia

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • TypeScript
  • AWS
  • LLMs
Seniority
Staff
Type
Full-time
Industry
HealthTech
Specialty
ML
Region
Australia
Show 7 more factsShow less

Role

Category
Data & Analytics
Specialty
ML
Seniority
Staff
Experience
6+ years
Tech stack
  • TypeScript
  • AWS
  • LLMs

Location

Work model
Hybrid
Region
Australia
Office
  • Melbourne, Australia
Remote from
  • Australia

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
HealthTech

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason