Founding Frontend & DevOps Engineer

Scanwick builds financial-data infrastructure for Nigerian lenders. Most credit decisions are made on a snapshot: a borrower hands over a statement, someone reads it, the loan goes out, and nobody looks again until a repayment is missed.

We work on the part after that. Continuous monitoring of a borrower's financial position once money has been disbursed, and an audit trail that lets a credit committee interrogate every conclusion we reach.

The engineering problems on this side are about legibility rather than polish. A locked feature and a figure we genuinely cannot compute must never look alike on screen, because the moment a user confuses the two, the correctness the whole product rests on is gone. Coverage has to be present on every view, so nobody reads silence as health. Every number has to open to the transactions beneath it, in a way a credit officer will actually click. And the system has to stay up and keep receiving data, because monitoring is only monitoring while the data is still arriving, a feed that quietly stopped looks identical to a borrower doing fine.

Compensation : read this first

We are early stage and pre-revenue. We cannot pay a market salary yet, and we won't pretend otherwise. The role is:

Meaningful equity, with a documented vesting schedule
A monthly data and internet allowance
Transition to a salary as revenue begins or funding closes

If that doesn't work for your situation, we understand completely, and there's no hard feelings in stopping here.

What you'd work on

Frontend development across the individual and institutional surfaces
Integration against our APIs, including the states where data is partial or unavailable
Production deployment, releases and rollback
CI/CD and the development workflow
Cloud and server infrastructure across the services the system runs on
Monitoring, logging, reliability and incident response
Production testing and resolving issues before a customer reports them

Stack: React and TanStack Router, TypeScript, Tailwind, REST APIs, Fastapi, Python, Git, Linux server environments, CI/CD, cloud infrastructure and container deployment.

Two firm requirements

Prior professional experience with financial data, banking, lending, credit, payments, account aggregation, KYC or BVN systems. This isn't a preference. Someone without that background tidies an interface in ways that quietly break it: rounding a figure because it reads better, hiding a null instead of labelling it unavailable, giving a locked feature and a missing one the same treatment. Each of those is a small design decision, and each one destroys the thing a lender is paying us for. We don't have the runway to teach it.

Production deployment experience. You must have deployed and run something yourself, not handed it to an ops team, but run it, watched it break, and fixed it while people were using it. The system is several services with a database, a queue and a scheduler behind it, and there is nobody else to pass it to. If your experience is frontend only, this is not the right role and we'd rather say so now.

Details: Remote. You'd work directly with the founder and the existing backend team.

To apply: send your CV and GitHub or portfolio to [email protected], with one or two lines on any financial data system you've worked on and something you deployed that went wrong.