Careers
Build payments that keep working.
We are building one API for every way people pay, starting in Nigeria, including when there is no network at all. The problems are hard, specific and written down. If that is the work you want, read on.
What you would work on
Three problems worth your next few years.
Payments with no network.
A customer taps a terminal and neither device has signal. Both sign; the payment settles hours later, verified against hardware-bound keys, with limits set before the tap and a loss policy chosen in advance.
How offline worksRouting that never charges twice.
Each payment goes to the provider most likely to approve it. A timeout is treated as unknown and checked before any retry, so a cascade to a second provider never charges a customer twice.
How orchestration worksCard data inside one boundary.
Card numbers will live only in a tokeniser and vault inside the cardholder data environment, which is being assessed for PCI DSS now. Everything else, from the API to the logs, is built to refuse them.
How we handle securityHow we work
Write it down, build it, check it.
Moving other people's money leaves little room for guesswork. These are the habits that follow.
We write it down first.
Use cases, the API contract, the security controls and the build plan are written before the code, and kept up to date as the record of what was actually built.
Every phase ends with a check.
Each stage of the build ends with something a person can call against a running system, and a gate they check before the next stage starts.
Rules come with reasons.
Our engineering rules state why they exist. “A timeout is unknown” comes with the double charge it prevents. A rule nobody can explain gets removed.
We say what is not built yet.
Plans name what is missing and what it depends on. On this website, anything not yet live carries a “Coming” label.
Working pattern, location and benefits are listed on each role.
Open roles
Open roles.
No open roles right now.
We still read every note. Tell us what you do, what you want to build, and a link to work you are proud of. When a role opens that fits, we will get in touch.
Email usHow to apply
Four steps, and you hear back at each one.
- 1
Apply.
Use the Apply link on the role, or email us. A CV or a link to your work is enough.
- 2
First conversation.
A conversation with the hiring manager about the role and your work.
- 3
Work sample.
A problem close to the real job, discussed with the people you would work with.
- 4
Decision.
We decide quickly and tell you why, whichever way it goes.
We reply to every application. If you need adjustments at any stage, tell us and we will make them.
Equal opportunity.
PediWave hires on the basis of skill, experience and the needs of the role. We do not discriminate on the grounds of sex, ethnicity, religion, disability, age, marital status or any other characteristic protected by law. If you need an adjustment to apply or interview, tell us.
Your data.
We use what you send us only to consider you for roles at PediWave. We delete it when it is no longer needed, or sooner if you ask. Read our privacy notice for your rights and how to exercise them.
Looking to buy rather than join?
Tell us what you need, or get a test key in five minutes.