Small team. Unreasonably high stakes.
We are building the layer other people’s businesses run on top of — their catalogue, their checkout, their money. That is a good reason to work here and the only reason the standards are what they are.
- Based in
- Enugu, Nigeria
- Remote
- Within Nigeria
- Open roles
- 4
Open roles
4 roles open right now.
Each one describes the actual work in the actual codebase. If a description sounds like it could be any company, tell us and we will rewrite it.
This is the part of the platform where being right matters more than being fast. You would work in Laravel on PHP 8.4 against Postgres, on a money path where every amount is an integer number of kobo, every mutation is a locked, idempotency-keyed transaction that appends to a permanent ledger, and a scheduled reconciliation exits non-zero if a single kobo disagrees.
What you would do
- Extend the wallet, escrow and payout services without weakening their guarantees
- Own the Paystack integration end to end — charges, transfers, webhooks, failures and reversals
- Write the tests that try to break tenant isolation and the money path, before shipping anything near them
- Keep the reconciliation honest as new movement types are added
- Review your own work as if the person on the other end is a seller waiting on a payout
What we are looking for
- Real experience with PHP and a mature framework, Laravel ideally
- You have debugged a production money bug and can describe what you changed to stop it recurring
- Strong SQL — you reach for a transaction and a lock before you reach for a retry
- You are suspicious of floating point in a financial context, without needing to be told why
Opens an email to hello@traxease.com with the role already in the subject line.
Every store on the platform is served by one Next.js app resolving the tenant from the hostname, and every vendor runs their business from a React dashboard on a phone. You would be building both, in TypeScript strict enough that `any` is a conversation, against a shared design-system package consumed by three separate frontends.
What you would do
- Build storefront templates that stay fast on a mid-range Android on a weak connection
- Extend the vendor dashboard — products, orders, wallet, media — mobile-first, not mobile-tolerated
- Add to the shared UI package carefully: three apps consume it, so it is additive-only
- Hold the line on accessibility — real buttons, real labels, keyboard paths that work
- Measure before optimising, and delete rather than abstract when the abstraction has one caller
What we are looking for
- Strong React and TypeScript, comfortable with server rendering and where it stops helping
- You have made something fast on a slow device, not just fast on your machine
- CSS you can reason about, not just copy — layout, stacking, containment
- You care what a component does to the person using it at 11pm with one bar of signal
Opens an email to hello@traxease.com with the role already in the subject line.
Support here is not a script. You would be the first person a seller talks to on WhatsApp and email, which means you need to understand escrow, payouts, delivery zones and the media library well enough to answer without escalating — and to recognise when a recurring question is really a product defect and say so loudly.
What you would do
- Answer sellers and shoppers on WhatsApp and email, in working hours, as a person
- Triage anything touching money to the front of the queue
- Turn repeated questions into help-centre guides and FAQ entries
- Bring the pattern behind ten tickets to engineering instead of closing them one at a time
- Walk new sellers through their first product and first payout
What we are looking for
- You write clearly and calmly under pressure, in English, without sounding like a template
- You have supported people with money at stake and know how differently that lands
- You are curious enough to learn how the platform actually works, not just what to reply
- Comfortable on WhatsApp as a professional channel, because here it is the main one
Opens an email to hello@traxease.com with the role already in the subject line.
Two surfaces: the storefront templates that sellers choose between, and the dashboard they run their business from. Both are used mostly on phones, both handle money, and neither can afford to be pretty at the expense of legible. You would be designing in the constraints, not around them.
What you would do
- Design new storefront templates end to end — home, shop, product, cart, checkout, account
- Improve the dashboard flows sellers use daily: adding a product, fulfilling an order, withdrawing
- Extend the design system rather than working beside it
- Design the empty, error and at-capacity states with the same care as the happy path
- Prototype the interaction, not just the screen
What we are looking for
- A portfolio with real products in it, ideally ones handling money or inventory
- Mobile-first by instinct — you design at 360 and let it grow
- You can hand off in a form an engineer can build from without a meeting
- Opinions about type and spacing you can defend without appealing to taste
Opens an email to hello@traxease.com with the role already in the subject line.
What it is actually like
The honest version.
Written for the person deciding whether to apply, not for the person deciding whether we sound impressive.
You will own something whole
The team is small enough that nobody is handed a slice of a feature. You take a surface — the payout path, the storefront, support — and you are the person who knows it.
The money path is not negotiable
Anything touching a balance gets tests, review and a slower pace, and no deadline changes that. If that sounds like friction rather than relief, this is the wrong team.
We write things down
Decisions live in the code, in comments explaining why rather than what. It is slower to write and it is the reason someone can pick your work up in six months.
Phones first, genuinely
Every feature is judged on a mid-range Android on a patchy connection. Building for the device you own is the easiest way to build something nobody here can use.
Hours that end
Support has stated hours and so does everyone else. Money problems get answered urgently; a marketing page does not. We are not confused about the difference.
Nigeria is the product, not the market
Naira, pay-on-delivery, WhatsApp, local delivery, patchy data. These are the defaults, not the localisation pass, and the team is here.
How we hire
Four steps, about two weeks.
You will know the salary range before the first conversation, and you will hear back either way at every stage. Nobody is left waiting to find out they were rejected.
1.You write to us
Reply within 3 working daysYour CV or profile and a few paragraphs on one thing you built and what you would change about it now. No cover letter theatre.
2.A conversation
45 minutesForty-five minutes on your work, our work, and whether the problem is interesting to you. Salary range stated here, by us, first.
3.A paid exercise
A few hours, paidA small, real problem from our actual domain, scoped to a few hours and paid at your rate. You keep the work. No take-home marathons.
4.The decision
Within 3 daysA final conversation about how you would work here, then a yes or a no with the reasoning behind it, within three days.
Nothing here fits, but you want in?
Write anyway. Tell us what you would work on and why it matters to a seller. A good unsolicited message has started more than one role.
Read the roles properly, then write to us.
One message, addressed to a person, about work you have actually done. That is the whole application.
Enugu, Nigeria · Remote within Nigeria