A renovation means months of work and significant money moving between people who may never have worked together. Renno brings clarity to that relationship. We are hiring the engineer who owns the systems that move and account for the money.
At a glance
- Location: Amsterdam. Four days a week at our office on the Keizersgracht, one day wherever you work best.
- Reports to: Mourad, CTO
- Start: November 2026
- Package: Competitive salary and meaningful equity in Renno, set out in full at offer
- Stack: TypeScript, PostgreSQL, background workers and schedulers
About Renno
Renno is the payment rail for renovation. Homeowners fund a project and pay as the work is approved. Builders get paid without chasing. Both sides see exactly where the money is.
We are live in Amsterdam and London and hiring the team that builds the next chapter of the product.
From Mourad, CTO. Every euro and pound on Renno has to be accounted for. That means a ledger we can explain, reconciliation we can trust and recovery we have tested. The engineer who joins takes responsibility for how those systems are built and how they behave in production. If you have kept a payments system dependable under real conditions, talk to us.
The Role
This is an ownership job. You take responsibility for the backend systems behind payments across two countries and two currencies: the ledger, provider integrations, reconciliation and the behaviour when something fails.
You work in TypeScript and PostgreSQL, build on existing work and carry decisions through to production. The challenge is to keep money correctly accounted for when events arrive late or twice, requests are retried and external services fail.
What You Own
- You own the integrity of the ledger: clear financial invariants, safe concurrent updates and an auditable record of every movement.
- You own the service’s API and event contract with the product, keeping it small and versioned, with idempotent commands and explicit event-ordering guarantees.
- You own reconciliation: discrepancies are detected, investigated and resolved, with a clear explanation of what happened.
- You own payment integrations and event handling, including retries, duplicate or delayed events and partial failures.
- You own production quality through meaningful tests, monitoring, runbooks, incident response and participation in on-call.
- You review changes to payment logic, document the decisions that matter and improve the systems you own as the product evolves.
What Success Looks Like
- Months 1 to 3: You have shipped changes, understand the financial model and can trace a payment through the system. You have tested a failure and its recovery.
- Month 4: You own a complete payment flow, including its reconciliation, monitoring and failure handling.
- Month 6: You confidently operate the systems you own, investigate discrepancies and lead recovery when something goes wrong.
- Month 12: Your work has made the systems easier to understand, change and operate. The decisions are documented and the recovery procedures are tested.
Who You Are
- You have built or operated a ledger or payments core in production, including reconciliation against an external provider. You can explain a reconciliation break you found and what you changed afterwards.
- You have integrated payment or banking APIs and webhooks, and understand idempotency, concurrency, event ordering and failure handling.
- You bring deep PostgreSQL expertise: transactional data modelling, access control, safe migrations and tests against the database.
- You have shipped and maintained TypeScript in production.
- You can take ownership of an existing system, explain its trade-offs and make it better.
- You are comfortable making decisions in a startup, working with incomplete information and taking responsibility for the outcome.
Experience with PSD2, Strong Customer Authentication, identity verification or onboarding would be valuable. So would Dutch.
Who You Are Not
- Someone whose payments experience stops at calling an API.
- Someone who treats reconciliation, retries or recovery as details to add later.
- Someone looking for a role that ends when the code is deployed.
Where This Goes
You will have substantial influence over how Renno builds and operates payments. There is room to grow your technical leadership through the quality of your decisions, the standards you establish and the engineers you help develop.
Tools You Will Use
TypeScript and PostgreSQL are central to the work. You will also use tools for code review, automated testing, observability and AI-assisted development, with responsibility for understanding and validating what you ship.
How We Hire
- A 30-minute conversation with Mourad, our CTO, about what you have built and the role.
- A 90-minute working session. You walk us through a payments system you shipped: the model, the invariants, a reconciliation problem and what you changed. Bring code you are able to share. There is time for your questions too.
- If there is a mutual fit, a written offer within 24 hours of the session, with the full package set out clearly. We also speak with two references, including a former manager or tech lead.