Senior Backend Engineer, Product Platform

A renovation brings together agreements, project stages and payments that need to stay consistent as the work moves forward. Renno gives homeowners and builders one clear view of that process. We are hiring the engineer who owns the product backend and makes the systems behind it work together reliably.

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: By December 2026
• Package: Competitive salary and meaningful equity in Renno, set out in full at offer
• Stack: TypeScript, PostgreSQL and Deno
• Focus: Product backend, service integration and engineering standards; most of your week in code

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.

The Role

You own the product platform: the application backend, its data models and the way it works with the payments service. You build the product side of that integration, shape the API and event contracts with the payments engineers, and pair on changes that span both systems.

The challenge is to make the whole journey dependable across service boundaries. Commands must be safe to retry, events must produce consistent state, and the product must remain clear about what has happened when part of the system is delayed or unavailable.

This is a hands-on role. You spend most of your week writing code, while helping other engineers make sound decisions through design discussions, review and pairing.

What You Own

• You own the product backend: application APIs, workflows, data models and access controls that support the user experience.
• You own the product side of payment integration: issuing commands, consuming events and keeping the state used by the product, notifications and analytics consistent with the payments service.
• You shape the API and event contracts with the payments engineers, with clear versioning, idempotency, ordering and recovery behaviour.
• You establish engineering standards across the product and its services through code review, automated checks, database tests and safe release practices.
• You make architectural decisions explicit and keep the system understandable through concise decision records, operational documentation and shared ownership.

What Success Looks Like

• Months 1 to 3: You have shipped backend changes, understand the important service boundaries and have tested how a product journey behaves when an integration fails.
• Month 4: You own a change spanning the product and a service, from its contract and data model through to release and production behaviour.
• Month 6: Other engineers can extend the systems you own using clear contracts, useful tests and documented decisions. Operational knowledge is shared.
• Month 12: Your work has made changes across services safer to deliver and easier to diagnose, with engineering practices that support the product as it grows.

Who You Are

• You have owned correctness in production systems where operations have financial or other irreversible consequences. You can explain a concurrency problem you found and the design change that resolved it.
• You have designed and evolved APIs and event-driven integrations between services, including retries, duplicate events and recovery from partial failure.
• You bring deep PostgreSQL expertise: schema design, transactional behaviour, authorisation models, safe migrations and tests against the database.
• You have shipped and maintained TypeScript in production.
• You have taken ownership of an existing production system and made it easier for others to understand, operate and extend.
• You have been the engineer others turn to for a difficult technical decision. You can explain the alternatives, write down the reasoning and help others carry it through.

Payment or banking integrations, ledgers, identity verification and regulated systems would be valuable experience. So would security or data-residency due diligence. English is our working language; Dutch is a plus.

Who You Are Not

• Someone looking primarily for infrastructure, cloud operations or deployment tooling work.
• Someone looking for a management role with occasional coding.

Where This Goes

You will have influence across the product and its services, with room to grow into broader technical leadership through the systems you build, the standards you establish and the engineers you help develop.

Tools You Will Use

The product backend uses TypeScript, PostgreSQL and Deno-based edge functions. The work spans application code, service contracts, database tests, security checks and delivery tooling.

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 backend system you owned: its boundaries, a difficult correctness problem and the decisions you made. 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.