Careers at IIH Money
We are not advertising any roles right now, so this page does not pretend otherwise. What it does explain is the sort of work building financial infrastructure involves, how an application gets read, and what to send if you would rather not wait for a posting.
No open roles at the moment
There are no vacancies listed today. If the work described below is the kind of problem you want to be solving, introduce yourself through the contact form and say which area interests you.
The work this product creates
These are the areas the platform's own surface area implies. They are a description of the problem space, not a list of vacancies.
IIH Money sits between a business and the tax authorities of the markets it trades in. That position sets the difficulty: an invoice is not a form submission, it is a legal document with a deadline, a required schema and a counterparty who will reject it without explaining why. Almost every discipline below exists because of that one fact.
- Compliance engineering
- Turning tax legislation into working code. Mandate changes, revised schemas and new clearance models arrive on someone else's schedule, and they have to be implemented and validated before a customer's invoice is rejected rather than after.
- Integrations
- ERP connectors, two-way accounting sync, banking rails and the public REST API. The work is mostly in the seams: reconciling systems that disagree about what a customer, a tax ID or a settled invoice is.
- Financial operations
- The domain knowledge behind what the platform automates — how invoicing, collections, dunning and reconciliation actually run inside a finance team, and which of those steps should never have needed a human.
- Product and design
- Deciding what a finance team should see first, what belongs behind a click, and which decisions the software should make on its own. Read-heavy screens where a misread number has consequences.
- Implementation and support
- Getting an existing stack connected and a customer's first submissions clearing, then feeding what went wrong back into the product instead of into a runbook.
How we read an application
Described structurally, because the specifics depend on the role — and there is no role open to be specific about.
We start with the work, not the title
A job title tells us what an organisation called you. It does not tell us what you owned. One problem described properly — what was broken, what you changed, how you knew it worked, what you would do differently — carries more weight than a list of technologies you have been in the same room as.
Expect the conversation to be about the domain
Financial software is unforgiving in a specific way: an invoice that fails validation is a real invoice that does not get paid, and a report that is subtly wrong is worse than one that is obviously broken. So the discussion tends to go towards correctness, edge cases, what happens when an upstream system lies to you, and how you decide something is safe to ship — rather than towards puzzles unrelated to the job.
Judgement matters more than throughput
Most of the leverage in this product is in deciding what not to build, which mandate to support first, and which manual step is worth automating properly instead of partially. We are more interested in how you reason about that than in how quickly you can produce code that will need rewriting.
What to send
Enough to tell whether there is a real overlap. No cover letter template required.
- Which of the areas above you are aiming at, and roughly at what level of responsibility.
- One thing you have built, operated or fixed, with the problem it solved and the constraints you were working under.
- Anything we can look at directly — a repository, a system you can describe in detail, a piece of writing about your own work.
- How to reach you, and whether you are asking about now or about later. Both are fine; it helps to know which.
Send it through the contact form. If nothing is open in your area yet, saying so is still worth doing — it is easier to remember a specific person than to search for one.
Introduce yourself
No posting to reply to, so use the contact form and tell us which part of the work you want.