Careers
Work on software people trust with their inventory
Labnize is used to decide whether there is enough of a reagent to run tomorrow. That is a good constraint to build under, and it is most of what makes this work interesting.
Open roles
Nothing posted right now
We are not hiring for a specific role at the moment. Open applications are read, kept, and answered first when something does open.
Send an open applicationWhere we look
Three areas we always read applications for
Product engineering
TypeScript across the stack, PostgreSQL underneath, and a product surface where a wrong number has a physical consequence. Comfort with data modelling matters more than framework trivia.
Laboratory operations
People who have run a store room, chased a certificate the day before an audit, or maintained the spreadsheet we are replacing. This knowledge is the hardest thing to hire.
Customer success
Onboarding a laboratory means loading a real catalogue, real suppliers and real approval levels. It is closer to implementation work than to support.
How we work
What to expect
Small team, direct decisions
There is no layer between deciding something and shipping it. The trade is that you own what you ship, including the day it breaks.
Written before spoken
Decisions live in documents that still make sense six months later, which is how a small team keeps its memory.
Close to the lab
Features are checked against real store rooms, not against a persona. Expect to see a cold room.
Two languages, one standard
English and Turkish are both first-class in the product. Neither is machine translated, and neither gets the shorter version.
What to send
A note about what you have built or run, and what you would want to work on here. A repository or a written document is worth more than a formatted CV.
Ready to modernise your laboratory?
Join the labs that swapped the shared spreadsheet for a system of record.