Engineering
The platform and everything under it
Product and platform · Integrations and devices · Security and reliability
Careers
Work on software thatsomebody depends on today.
Zyposoft builds hospital platforms, AI products and the systems that connect them, for ourselves and for the organisations we work with. The work is unglamorous in the best way: it has to be correct, and somebody notices when it is not.
Small teams, real ownership, and a short line between the decision and the person who has to live with it.
Product and design
Deciding what is worth building
Discovery with the people using it · Workflow design · Interface and research
Clinical and delivery
Getting it into real use
Clinical safety · Implementation · Support and adoption
What working here is like
Five things you should know first.
- 01
You will own something real.
Teams are small enough that there is nowhere for a decision to hide. You will be the person who understands a part of the system best, and the person asked when it breaks.
- 02
The domain is the hard part, and we teach it.
Almost nobody arrives knowing how a ward actually runs, what an HL7 message carries or how a client's old system really behaves. You are expected to learn it, not to have arrived with it.
- 03
Correct beats fast, and we mean it.
A release that is not ready gets stopped, by whoever spots it. That is slower some weeks. It is the reason the thing works at three in the morning when somebody is relying on it.
- 04
Writing is part of the job.
Decisions get written down so the reasoning survives the person who made it. You do not need to be a stylist, but you do need to be able to explain a choice in a paragraph.
- 05
You will see the work land.
This is not software that disappears into a backlog. You will sit in on implementations, watch it used, and hear directly when a screen is in somebody's way.
Life here
The small habits that make a week here.
Not the perks page. The small habits that make a week here feel like a week somewhere specific.
Nobody's first week is spent alone
You are paired with someone from day one. They answer the questions you would feel silly asking in a group, and they are supposed to.
We demo, we do not present
Show the working thing, warts included. A half-finished screen that runs beats a beautiful slide about a screen that does not.
Questions are cheap here
Asking early is treated as good judgement, not as a gap. The expensive thing is the person who quietly guessed for three days.
We go and see it used
Whoever builds it should watch somebody use it, on a ward or at a client's desk. It is humbling, it is the fastest way to learn the domain, and it changes what you build next.
The unglamorous fix gets the applause
The migration that went quietly, the flaky test finally killed, the error message rewritten so it actually helps. Those get called out.
We stop and mark things
A first go-live, a nasty bug closed, someone's first shipped feature. Work in this domain is long, so the milestones are worth pausing on.
No two weeks look identical, and none of the above is a policy. It is just what tends to happen.
Careers
Open roles.
Where we are hiring, and what each role would own. If nothing below fits but you think you should be here, say so.
No open roles right now.
We are not hiring at this moment, and we would rather tell you that plainly than leave a stale listing up for you to apply to.
If you think you should be here anyway, send us a note about what you do and what you would want to work on. We keep them, we read them, and we do come back to people when something opens up.
When we do hire, it is usually in one of these
- Product engineering
- Platform and infrastructure
- Integration and devices
- Security and compliance
- Product and design
- Clinical and delivery
- Quality engineering
Get in touch
Nothing open that fits?
Tell us what you do and what you would want to work on. If there is a version of that here, we would rather know about you before the role exists than after it closes.