The stakes are real.
Banklink connects South African bank accounts to the businesses that need their data. We’re building the account-linking flows, transaction ingestion, scheduled fetches and webhook delivery that make that useful.
You’ll work directly with the founder, taking problems from the first conversation through to a working release. That means writing code, making architecture decisions, talking through trade-offs and checking that the thing actually works in production.
There’s meaningful scope to shape the product and how we build it. The responsibility comes with it: this is financial data, and people need to be able to trust the result.
What you’ll own
- Ship complete features across the dashboard, API and bank-data workflows. Understand the problem, choose a sensible scope, and follow it through.
- Make the system dependable: permissions and tenant isolation, data correctness, safe retries, useful audit trails and clear failure states.
- Keep releases safe and supportable, with meaningful tests, monitoring, documentation and a way back when something goes wrong.
- Investigate issues properly. Reproduce them, find the cause, and verify the fix in the running system.
- Build security in from the start: least-privilege access, strong authentication, secrets kept out of code and logs, and safe handling of untrusted input. Apply current guidance such as the OWASP Top 10 and ASVS, and keep dependencies patched.
What you bring
- A track record of shipping enterprise-ready software. You can point to systems real businesses rely on, explain what you personally built, and talk honestly about what happened after launch.
- Depth across the stack. You’re comfortable with TypeScript, React, Node.js, SQL and HTTP APIs, and can work through authentication, background jobs and deployment issues.
- Security instincts, kept current. You follow vulnerability disclosures and supply-chain advisories, and you can explain how today’s threats, such as credential stuffing, broken access control, SSRF and compromised dependencies, apply to an API that handles bank data.
- Sound judgment. You know when to keep a solution small and when security, reliability or a customer’s requirements call for more care.
- A grounded way of working. You’re direct, curious and willing to disagree with a reason. You take feedback, say when you don’t know, and follow through without needing every step assigned.
- The ability to teach. You can explain your decisions, give useful code reviews and help another engineer work through a problem.
Fintech, enterprise integrations, browser automation or experience mentoring engineers would help. Show us the work and how you think.
How we’ll work together
Short feedback loops, small reviewable changes, and evidence that the software works. Security review and threat modelling are part of normal delivery, not a final gate. We value clear writing, practical decisions and ownership of the outcome. Use AI tools where they help; understand, review and verify what you ship.
As the team grows, you’ll be responsible for training and developing your direct reports. That includes onboarding, pairing, constructive reviews and gradually giving people more ownership. Helping them become capable, independent engineers is part of the job.
Show us something you shipped.
A short introduction is enough to start. In the form below, tell us:
Write the message yourself. We want to hear from a human, not read an AI-written application.
- One or two examples of production software you helped ship, and what you personally owned.
- A technical decision or production problem you worked through, and what you learnt.
- Where we can see more of your work, plus your location, time zone and availability.
Private enterprise work counts. Describe it without sharing customer data, credentials or confidential code. If you’ve trained or mentored others, tell us about that too.