Decision record
DR-019
Entry 01
Postgres, not Mongo.
Because
- Relational structure fits how orders and invoices actually behave.
- One query language everyone here already knows how to read.
Specimen copy
Careers
We build software for other companies, which means the work is varied and the standards are not ours alone to set. If you like understanding why a thing is being built before you build it, this is a reasonable place to be.
Decision record
DR-019
Entry 01
Because
Specimen copy
The honest part
Stated as facts rather than values, because facts can be checked.
Some of them you will find interesting. Some of them are invoicing systems, and someone has to build those too.
This is not optional here, and if it sounds like overhead you will find it tedious.
Not through a manager relaying questions. You join their calls, hear requirements in their words, and ask the follow-up while everyone is still on the line.
Reacting to that without visible irritation is most of the job. Estimates get revised out loud, not quietly absorbed.
Open roles
We are not hiring at the moment. If you want to hear when that changes, leave your details below and we will write to you rather than expecting you to keep checking.
Leave your details belowConditions
Three facts about the environment here. None of them involve a ping pong table.
Working hours that overlap your team's day, agreed up front rather than discovered later. Where each of us sits matters less than whether the overlap is real.
Decisions live in documents, not in someone's memory of a call.
Engineers speak to the people they are building for.
Speculative applications
We keep good applications and go back to them. Tell us what you work on and where we can see something you have made.
What happens to it
Kept and reread when a role opens
Replied to either way
Good applications get kept and read again. When something opens that fits what you told us, this is where we look first.
When something opens, this page changes first.