You can explain the tradeoff
Every decision here costs something. We care much less about whether you picked the popular option than whether you can say out loud what you gave up to get it.
We hire people
who finish things.
Open roles in engineering, design, and delivery. Every application is read by the team you would actually join.
Internal platformsDesign systemsPaymentsData pipelinesClient portalsRealtime tooling
Three things we look for.
None of them are languages or frameworks. Those you can pick up here.
You ship, then you stay
Nobody hands work over the wall. The person who builds a thing runs it, watches it fail, and fixes it. That loop is the entire reason our estimates are worth anything.
You leave it legible
Someone reads this code at 2am eighteen months from now, and it will not be you. Naming, comments, and a commit history that reads like a sentence are part of the job.
How we hire, start to finish.
Four stages. Roughly two weeks, and you always know where you stand.
Apply
A real application, not a keyword filter
You answer questions about work you have actually done. No cover letter, no timed puzzle, no automated screen deciding whether a human sees your name.
Read
The team you would join reads it
Two people from the team read every application end to end and write down what they thought. You hear back inside a week, either way, with a reason attached.
Talk
One conversation about your own work
We walk through something you built and something you would do differently now. No whiteboard algorithms, no panel of strangers, no take-home you never get paid for.
Decide
You get the offer and the context
Salary band, who you report to, what the first ninety days look like, and what we are worried about. You decide with the same information we have.
If none of the roles fit, write anyway.
Tell us what you want to work on and what you have built. We keep good applications on file and we do come back to them.