Careers
Every piece of work here has a finance team waiting at the end of it.
The product gets built when a customer asks for it, and that decides most of what working here is like: what you ship has a real group behind it the day it goes out, and whether it is right is settled against a bank statement rather than against an opinion. There is no list of open roles below. There is a description of the work, and an address.
How the work arrives
Where does a piece of work actually come from?
Not from a roadmap workshop. Four things happen instead, and they happen in this order.
- 01
A group asks for something specific
A structure they need modeled the way their banks really run it, a file a bank sends that nobody in the market reads well, a report their auditor keeps sending back. The ask arrives with a real company attached, which is what makes it a specification rather than a guess.
- 02
It is scoped against their actual files
Not against a description of their files. Somebody opens the statement, the ledger extract and the format profile, and finds the three things the description left out. That is where most of the design happens, and it is why nobody here designs from a slide.
- 03
It ships to them
The first user is the group that asked. They open it the week it lands and they say whether the number is right, which is a faster and harsher review than any internal process could be.
- 04
And then it belongs to everybody
Because every module reads from the same reconciled reality, what was built for one group is a configuration for the next. Nothing here is a one-off integration that has to be kept alive on its own forever.
That is the whole method, and it explains the parts that look unusual from outside. Nothing is shipped that nobody has opened, and nothing is carried that nobody asked for.
What you would work on
What is the actual work?
Four areas. They are not four teams — most weeks touch more than one of them.
- The matching engine
- It weighs competing explanations for one movement, scores them, knows which questions are not worth asking, and changes its mind when new evidence arrives. The hard part is not the matching. It is keeping the reasoning defensible afterward, at group scale, on data that never stops moving.
- The ledger engine, and money that has to be exact
- Amounts are integer minor units end to end, rounding is a decision rather than something inherited, and an allocation that has to add back to its total does. A floating-point cent in a treasury system is not a defect somebody finds in a test — it is one an auditor finds in a report.
- Reading what banks actually send
- MT940, CAMT.053, BAI2, CSB43, ISO 20022 messaging, and the dialects underneath them that no specification mentions. Every one of those files is somebody’s real money described badly, and getting it exactly right is far more interesting than it sounds.
- The screens a treasurer lives in
- A position, a calendar, a reconciliation queue, a payment run. They are opened every morning by people under time pressure, in more than one language, on more than one size of screen — so a figure that wraps or a column that quietly disappears is a defect and not a polish item.
The standard
What is the bar, in practice?
This is finance. A wrong figure is not a bug report, it is a liability — so the standard here is not speed and it is not cleverness.
- Exact, or an honest decline
- A figure is either arithmetically exact and traceable to the record it came from, or it is refused with the reason on the surface. There is no tolerance band and no proportional guess wearing the clothes of a fact.
- A number you cannot explain does not ship
- Population, unit, magnitude, in one sentence, or it goes back. A total that looks too good is treated as a defect signal, because nobody ever escalates a flattering result.
- The evidence outlives the answer
- The explanations that lost keep their scores, the inputs stay attached to the decision, and the whole trail exports. A result somebody has to take on trust is a result we did not finish.
- Complete, or loudly incomplete
- When something is missing from a figure, the surface says what is missing and why, where a reader who never hovers and never clicks will still see it. Quietly partial is the failure that survives every other check.
None of that is a code style. It is what the job is: the person at the other end of one of these screens is about to sign something.
How to write to us
There is no roles list. So what should I send?
Say which of those four areas you would want to be in, and show one thing you built and why it was hard. That tells us more than a role title does, and it is a better use of your evening than answering a posting somebody wrote to fill a slot.
Where the work happens
- Austin, Texas
- Madrid, Spain
What you would be building
The questions we get
What people ask before they write.
- 01Is there a list of open roles?
- A role here is shaped around a person rather than posted and filled. Say what you would want to work on and what you have built, and the conversation starts from that instead of from a title.
- 02Where would I be working from?
- The work happens in Austin, Texas and in Madrid, Spain. Say where you are, and you will get a plain answer about whether it works rather than a form.
- 03Do I need a finance background?
- No. What you need is a willingness to learn what a bank statement actually contains, because most of the interesting defects in this code are only visible to somebody who knows what the file was supposed to say.
- 04What should be in the first message?
- One thing you built, why it was hard, and which of the four areas you would want to be in. Skip the cover letter. If you have built something that had to be exact — money, timestamps, anything a person puts their name to — lead with that.
Tell us what you would want to build.
One message: one thing you have built, why it was hard, and which of the four areas you would want to be in.
No posting to answer, and no form to fill in.