Real time and integrations
Streaming voice, live structuring, HL7/DICOM and on-call reliability: a system with clinical consequences.
CAREERS
Build the post-imaging
layer with us
Lean team, hard problem and a demanding user: the Brazilian radiologist. If you like products with real clinical consequences, talk to us.
IN DETAIL
How we work
- CLINICAL
Physicians in the product
Product decisions go through the people who write the reports. Clinical feedback enters the cycle every week, not in an annual survey.
- TECHNIQUEFINDINGSIMPRESSIONDICTATING · THE STRUCTURE BUILDS ITSELFSCIENCE
Measurement before marketing
If it does not pass LaiBench, it does not reach the user. The criterion is public, and the internal incentive points in the same direction as the user's.
- FOCUS
Few things, done well
Four modules and one flow. Depth instead of a new feature every week; the 52-second median is the result of that.
What we look for
Engineering that likes systems with consequences: real time, voice, hospital integration, real reliability. Product and design that respect expert users. Clinical people who want to build the tool they would like to use on shift.
We do not publish a decorative list of openings. If the problem pulls you in, write to us about what you have already built and what you want to build here. A small team hires the person, not the job description.
OVERVIEW
Where you would fit in
Expert user
An interface for people who decide in seconds. Zero-Click is not a slogan: it is the hardest design problem we have.
Applied radiology
RadCommons curation, LaiBench cases and the weekly feedback that guides the product.
In practice
- MODELRemote in Brazil, with periodic in-person meetups
- STACKA real-time product with voice, AI and healthcare integrations
- CULTUREClear writing, autonomy with accountability, public criteria
- PROCESSDirect technical conversation with the team, no group dynamics
- STEPSA chat with a founder, a technical conversation about real work, and an offer. Weeks, not months
- CONTACToi@laudos.ai, subject "Carreiras"
Building clinical software is detail work
The kind of problem that exists here
Working at Laudos.AI means dealing with clinical language, a real-time editor, integration with legacy systems, privacy of sensitive data and interfaces used under pressure. A small change can affect productivity, trust or traceability, so product, engineering and clinical need to review the same flow from different angles.
Open positions, type of contract, pay range and process steps must appear in the specific opening, not be inferred from this page. When there is no matching position, contact remains open to anyone who can show work relevant to the problem; this is not a promise of a process or a timeline.
NEXT STEP
Didn't find an opening with your name on it?
Send your interest anyway. A small team hires the person, not the job description.