Senior Product Engineer, Front End

Please include your CV and portfolio or sample of work if applicable.

Renovating a home asks people to commit significant money before they know how the work will unfold. Renno gives both sides, the people paying and the builders doing the work, one clear view of where the project stands and where the money is, from agreed scope to final payment. We are hiring the engineer who owns how that feels on screen.

At a glance

• Location: Amsterdam, on site at our office on the Keizersgracht
• Reports to: Mourad, CTO
• Seats: One
• Start: October 2026
• Package: Competitive salary and meaningful equity in Renno, set out in full at offer
• Stack: React and TypeScript

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. Renovation runs on trust between people who have never worked together, and on money moving at the wrong moments. We are building the product that fixes the second so the first can happen: every euro and pound visible, every step clear, in two countries and two languages. The engineers who join now decide how that feels for years. If you care about the details that make people trust software with their money, talk to us.

The Role

This is a building job. You own the journeys homeowners and builders use to run a renovation on Renno, from agreed scope to final payment, and you take them from research and early design decisions through to reliable, polished software in production.

You work side by side with our product designer, proposing interactions as well as building them, and you build and grow the design system the whole product is made from. The challenge is to make complex processes feel clear: helping people understand where they stand, what they can do next, and what happens when something does not go to plan.

What You Own

• You own the product and payment journeys on screen, in React and TypeScript, with close attention to interaction design and the details that earn users' trust.
• You own the design system with our designer: accessible, responsive components that the whole product is made from, not only consumed.
• You bring the interaction proposals. You question assumptions and make the trade-offs between what users need and what the system can do, rather than waiting for a finished design.
• You own the states that go wrong: loading, waiting, failure and recovery are as considered as the successful path.
• You own the quality of what you ship, through thoughtful testing, code review and attention to how it behaves in production, in English and Dutch, on mobile and desktop.
• You use AI-assisted tools as part of how you work, and you know where they help and where they do not.

What Success Looks Like

• Months 1 to 3: you have shipped to production in your first weeks, you know the journeys and the research behind them, and the design system carries your first components.
• Month 4: you own a complete journey end to end, and the designer brings you in before the design is finished, not after.
• Month 6: the experiences you own are live for homeowners and builders in both countries, and the failure states are the ones people praise in support conversations.
• Month 12: the design system is the way the product is built, and the next front-end engineer learns it from you.

Who You Are

• A strong record of shipping and improving production web applications, with deep TypeScript and front-end expertise and confidence working in React.
• You have shipped payment journeys in production, including complex, multi-step flows where clarity and correctness matter.
• You have built a design system, not only used one, and you have opinions about interaction design that you can argue for.
• You have integrated third-party hosted or embedded components and handled their session, loading and error behaviour properly.
• You turn an ambiguous problem into a considered solution, explain your decisions, and work closely with designers and other engineers.
• You are comfortable in a startup: you try things, keep what works and move on from what does not.

The product ships in English and Dutch; experience with multilingual products would be valuable.

Who You Are Not

• Someone who waits for a finished design before thinking about the interaction.
• A pixel-perfect implementer who does not ask whether the flow is right.
• Someone who treats error and waiting states as edge cases to do later.
• Someone who has never worked with a design system before.
• Someone who needs a large front-end team around them to ship.

Where This Goes

The product is expanding in two countries and the front end grows with it. The engineer who owns these journeys well is the first candidate to lead the client side of the product as the team grows, and to set how Renno builds for the markets after London.

Tools You Will Use

You do not need to have used all of these, but you should pick them up quickly.

• Product and engineering: React, TypeScript, Figma, GitHub, Linear…
• AI and automation: Claude Code, Cursor and more.
• General: Notion, Slack, Google Workspace…

How We Hire

1. A 30-minute call with Mourad, our CTO, about what you have built and our plan.
2. A 90-minute working session with the team. You bring one journey you shipped and walk us through it end to end: the problem, the interaction choices, what went wrong and what you changed. Then you show us code you are proud of. We ask you anything, and you ask us anything you like.
3. A written offer within 24 hours of the session, with the package set out in full. Mourad calls two references at the same time, one of them a former manager or tech lead.

Apply

Send a CV, a link to something you built, and three lines on the interaction you are proudest of to [email protected], for the attention of Mourad Chennaoui, CTO. No cover letter.