You will talk to users
Not through a product manager. You will sit in a school office or a hospital corridor and watch how the thing you built is actually used.
Careers
Build things people actually depend on.
The systems we write are used by school offices, hospital counters and government departments. When they break, somebody's day breaks with them. That is the interesting part.
No open roles at the moment.
We hire when there is work that needs another pair of hands, not to build headcount, so this page is empty more often than not. That is deliberate.
If you write software you would be willing to defend in a code review, send us something you have built anyway. We read those, and we keep the good ones on file for when a role does open.
How we work
What to expect if you join.
Small team, real ownership
You own features end to end, including the part where it breaks in production at an inconvenient time.
Code review is not optional
Everything is reviewed, including work by whoever is most senior in the room. Expect to defend decisions and to change your mind.
We do not ship and run
Every project has a support window we are contractually on the hook for, which changes how carefully you write things.
Boring technology, mostly
We choose tools the client can afford to keep running. That is often not the newest thing, and that is a deliberate call.
Learning is part of the job
New sectors come with domain knowledge you will not have. Reading up on how examinations or pharmacy stock actually work is normal here.