Senior Backend Engineer (Node.js)

About the role

Remote in EU, or hybrid in Barcelona, Palma, Dublin, or Casablanca.

Own the backend of a white-label travel platform as it adds new verticals.

Hotels and flights are live. Experiences launch within weeks, and car rentals and more payment providers come next. Our clients are travel brands, banks, and influencers, so every launch brings a new challenge and a chance to design it properly.You'll step in as the backend owner at a pivotal moment. You'll shape the architecture, lead the integrations for each new vertical, and stay hands-on in the code. We've moved quickly to get here, so there's real room to set the standards and clean up the foundations as we grow.This is a role with real ownership. You'll work directly with the backend lead, and within about six months you'll be making the backend decisions yourself.

What makes it interesting for you:

You get real technical authority. You become the primary backend decision-maker for a product line, working directly with the backend lead and engineering leadership. Your architecture choices stay in the product, and the role has room to grow as the platform and team expand.

You build on a product that is still taking shape. The platform is heading toward Shopify-level customization, with modular components and configurations for very different clients. You'll build foundations that later verticals depend on.

You get variety. Each client brings an odd requirement, and the good ideas often become features for other clients. You'll learn something new most weeks.

You join a stable team. The team has worked together for two to three years, and the engineers look out for each other.

Nuitée has grown 10x since 2022, was profitable before raising a $48M Series A led by Accel, and works with companies such as Revolut, Grab, Hopper, Priceline, and Sabre.

The kind of problems you’ll work on:

How do we design the backend so that adding a vertical, such as experiences or car rentals, doesn't mean rebuilding what already works?

Which pieces of existing technical debt hold back reliability or delivery speed, and what is the cleanest order to fix them while shipping?

How do we integrate third-party travel APIs and payment providers so that bookings stay reliable when a supplier is slow or fails?

How should our schedulers, cron jobs, and workers be built so they stay dependable as traffic grows?

How do we keep AWS infrastructure performing for client launches without over-engineering it?

You’ll work on problems where the product, technical approach, and best path forward are still being figured out.

The role is backend-heavy and product-driven. You should be comfortable going from idea to design, implementation, and real usage, without needing detailed specs.

A good way to think of it is: you build the first version that proves something works.

This role fits if you:

Have 4 to 5 years in backend engineering, including at least 2 years of full-time Node.js and TypeScript in production. Java or Python backgrounds are welcome if you have since worked in Node full time.

Have designed REST APIs and relational schemas in PostgreSQL.

Have worked with background jobs, schedulers, or workers that talk to third-party systems.

Have roughly two years of hands-on AWS, enough to run a product that has to handle real traffic.

Have taken ownership of a product's outcomes beyond the tickets assigned to you, and stepped in when a teammate was out.

Have experience leading technical decisions for a team, or have been in a position to. You still write code every day.

Nuitée is fast-moving, low on process, and high on ownership. This suits people who are comfortable with ambiguity, pace, and responsibility. It is less suited to people who prefer structured environments and clearly defined scope from day one.

Travel experience helps but is not required. Experience in a fast-moving product company probably is.

We move quickly and have little process. You'll see 10 plus features moving in parallel, and priorities can change when a client needs something.

You'll contribute code in your first days and take decisions with incomplete information. The first couple of weeks are about getting used to this rhythm, and after that you have a lot of autonomy.

If that resonates, we’d love to hear from you. You can apply with your LinkedIn profile or CV. The process is straightforward and typically takes 2 to 3 weeks.