Build software that has to keep working
Centricone takes on the systems businesses actually depend on — the ones where a bad release is somebody's Monday morning. If you would rather do a small number of things properly than ship a lot of things quickly, we should talk.
How we work
We say what we will do, and we do what we said. Estimates are honest even when the honest answer costs us the work, and code is reviewed by someone who will have to maintain it.
What working here is like
Remote, on your own time zone
We deliver across US and Canada hours. Overlap with your team is planned into the engagement rather than left to goodwill.
Senior work, not ticket queues
Engineers scope what they build and talk to the client directly. Nobody here is handed a specification and told to type.
Time to do it properly
Tests and documentation are part of the estimate, so writing them is the job rather than something you fight for.
Range across real systems
eCommerce, healthcare, finance, and telecom — greenfield builds and fifteen-year-old systems, often in the same quarter.
What to expect from our hiring
A conversation, not a screen
First call is with an engineer. We describe the work honestly, including the parts that are unglamorous, because a surprise in month two is expensive for both of us.
A working exercise
Relevant to the role and time-boxed. You talk through decisions with someone who does the job — we are interested in how you reason, not whether you memorised an algorithm.
A decision, quickly
We come back either way, with feedback. Leaving candidates without an answer is the most common thing wrong with technical hiring and it costs nothing to fix.
Open roles
No roles open right now
We hire in small numbers and only when there is real work waiting. If you build the kind of software described above, send us what you have worked on and we will keep it on file — we would rather hear from you early than advertise late.