Senior Fullstack Engineer (F/M/X)

Senior Fullstack Engineer (F/M/X)Full remote — Europe · Product & Engineering Who are we?In 2017, after more than ten years in the lift industry across Europe and Asia, Benoît Dupont noticed a system stuck in its ways where speed takes priority over quality and frontline teams remain invisible.With Jade Francine, he founded WeMaintain to put technology, trust and people back at the heart of building maintenance. Their ambition: give technicians back their autonomy, rely on in-house IoT technology, and deliver a service designed for users and clients.Based in Paris, London, Singapore and Hong Kong, we maintain lifts, escalators, automatic doors and fire safety systems. With 350+ employees, we combine on-the-ground expertise with data-driven management to deliver maintenance that is high-performing, transparent and sustainable.In April 2026, Otis, the world's largest elevator and escalator company, became our majority shareholder. We keep running as we always have: same team, same brand, same mission. What changes is the scale of what we can go after, and the means behind us to do it.We don't just maintain buildings. We transform how they're operated. Why join us?Because here, you don't have to choose between impact and stability.Large groups often offer stability, but little room to manoeuvre. Smaller organisations allow more freedom, but sometimes without clear direction.At WeMaintain, we strike the right balance:Real autonomy, with modern tools and strong supportA culture built on trust, transparency and respectGenuine opportunities for growth and internal mobilityA team that values commitment, perseverance and the drive to make things happenAnd our values guide us every day:Care: Working with respect and kindness, internally as well as with our customersGrit: Seeing things through, with high standards and determinationUniqueness: Daring to be yourself, sharing your ideas and challenging the status quo Who we're looking forWe're looking for a Senior Fullstack Engineer who wants to own problems, not tickets.You get handed a problem before anyone has decided what the answer should be. You help our product managers shape it, you build it, and you take it to production. The whole arc is yours. That suits people who like to argue about what gets built. It would frustrates people who would rather receive a groomed backlog and a clear spec, and people who would rather be left alone to code.We call our team ProdEng (Product & Engineering), and we mean it structurally. There's no fixed org chart where you belong to one squad and that's it. We form small, bespoke teams around a topic for as long as that topic needs one, then we form different ones. Over a year you'll work with several PMs, several engineers, and often directly with the people in the business whose day your work changes. You'll talk to the CTO and the CPO regularly, because there's nobody in between.This is a hands-on individual contributor role with no direct reports. You'll report to Tim Bourguignon, our VP of Engineering.You'll join a Product & Engineering team of 20 people, growing by 50% over the next year.ð ️ Our stackWe're a TypeScript shop, end to end, and we're quite proud of what we've built.Backend: Node.js, TypeScript, NestJS. Microservices in a full mono-repo, with custom tooling we built ourselves for codegen, infrastructure and developer workflow.API: a federated GraphQL API, so every one of our applications talks to a single unified surface.Infrastructure: fully infrastructure-as-code on AWS. EKS for the big services, Lambda for everything else.Data: PostgreSQL with TypeORM. dbt on BigQuery and Looker for analytics, plus our own time-series engine purpose-built for IoT.Frontend: two front ends, both actively maintained. Angular micro-frontends for our back office and customer platform, and a React Native app our field engineers use every day.We keep both front ends current on purpose. If one of them had been left to rot, we'd tell you. Your day-to-day at WeMaintainAs a Senior Fullstack Engineer, you will:Own features end to end: the problem statement, what the solution should look like, the implementation, and getting it into production. The rest of the team is there to help, which is what a tight-knit team of twenty is for, but the topic is yours.Work across the whole stack. Most people here have a centre of gravity, usually backend (although we do have a couple frontend wizards), and that's fine. What we expect is that you're comfortable being asked to do both, and that "the other part" never becomes someone else's problem.Shape the work as well as build it. You'll sit with PMs, with the CTO and CPO, and sometimes with the operations people who'll use what you build. If you think the problem has been framed wrongly, we want to hear it before the build rather than after.Take our engineering standard forward. Our tooling, our mono-repo, our developer experience, our resilience in production: we work on all of it deliberately, we want to keep taking pride in it, and all of it is open to you to improve until you feel it's yours as much as ours.What's on the roadmapThree of the things you could pick up, to give you a sense of the work:Normalising tens of thousands of distinct ways a lift can fail. Yes, really: tens of thousands. Getting that taxonomy right is what lets us automate diagnosis, resolution and quoting instead of having a human read every report.Turning realtime IoT signal from thousands of devices into something a field engineer can act on, working hand in hand with our data science and hardware teams. Raw telemetry at that volume tells you nothing on its own. Making it tell you something is a hard, satisfying (at least we think so!) engineering problem.Bringing agent-in-the-loop workflows into our back office, as a second pair of hands for the people working there. Workflows that do real work, not a chatbot bolted onto a sidebar with a shiny purple "AI" badge next to it.On AI, specificallyUse them. Obviously. We'd think it strange if you didn't.The tooling has moved the goalposts in the last two years, for how we ship and for what we can ship at all. We'd rather talk about what that makes possible than about which model we're on this month. It doesn't remove the need for strong engineers. It makes them more valuable, because someone still has to know what good looks like. Use it however you see fit. You won't be BS'd or FOMO'd about it here.And a word on the fieldFrom the outside the industry looks remote and a bit dull. It's neither, and what you find once you're in it is how tightly coupled everything has to be. Problem detection feeds the device state service, which needs the SLA on the contract, which depends on the customer, and which regulation reads differently in each of our four countries. Very little here is a self-contained feature.The software you write changes how someone's day goes on site. You'll see that for yourself during onboarding. It isn't a day-to-day part of the job, but it's the reason the job matters. What we're looking forYou might be a great fit if you:Have 5+ years building and running production software, and have owned something from problem statement to production rather than from ticket to merged PR.Are comfortable across the stack. Not equally strong everywhere, nobody is, but not precious about which layer you're working in this month.Are strong in TypeScript and in modern backend architecture, deeply and conceptually. Which frameworks you learned them in matters much less to us.Care about how things are built as well as whether they work. Software should be useful to someone first, and engineers should still be able to take pride in it.Can talk to a non-technical stakeholder without a PM in the room, work out what they need, and come back with something better than what they asked for.Are at ease working fully remotely, and take the initiative to stay close to people rather than waiting to be pulled in.We don't require experience with our specific stack. If you've never touched NestJS, Angular or React Native but you've built and owned the equivalent elsewhere, we want to talk to you.English is the working language of this role. Bonus points ifYou think like an owner. You've started, run or helped build something of your own, and you judge your work by the impact it had rather than the code you wrote.You've shipped a React Native app that real people used every day, in difficult conditionsYou've worked in an operations-heavy business: field service, logistics, industrial, energy, anywhere the software describes physical things happening in the worldYou've put AI-driven workflows into production and know the difference between a demo and something that holds upYou've built internal tooling, codegen or developer-experience work that other engineers adoptedYou've worked with IoT, telemetry or time-series data at scaleWe don't expect you to have seen all of this already. We do expect you to ramp fast, think clearly, and take ownership quickly. Why this role is differentMost senior engineering jobs give you one of three things: interesting technical problems, ownership, or work that visibly matters to someone. This one has all three, which is what a twenty-person team inside a 350-person operator looks like.The OTIS deal means we get to accelerate on our vision rather than consolidate. There's more we can go after now, and more behind us to do it with. What we need are people who can close the gap between what technology makes possible and what our teams do manually today.And it's full remote, properly. Keeping a remote team healthy takes work, and we put the work in. We live in a virtual office and on Discord, so it's normal to drop in on someone instead of booking a meeting, and the whole team gets together in person at least three times a year.️ How to applyEvery application is reviewed carefully. Tell us who you are, what attracts you to this role, and what you'd like to build with us.We value motivation, curiosity and potential over a "perfect" background.To apply, click the "Apply" button below and answer a few questions in the form. It's quick, and it helps us get to know you better. Katia, our Recruitment Manager, looks after the process from there — including confirming the band for your country by email before we speak, so nobody's time gets wasted.At WeMaintain, we value diversity, encourage personal development, and are committed to inclusion. Whatever your background, story or identity, you are welcome to apply. Recruitment processThree stages. No take-home. We move quickly and we'll keep you posted at every step.An interview with a senior engineer from the team, such as Lionel (Principal Engineer), 60 mins An engineer-to-engineer conversation about what you've built, the calls you've made, and what you'd want to own here.A problem to think about, then a 90-minute discussion with David (CTO) and a senior engineer We send you a problem a few days ahead. Spend 30 minutes on it. No code, no slides, no prep deck. Then we talk it through together. We're interested in how you think, what you ask, and where you push back. The artefact doesn't matter.A final round in a single 90-minute slot: 45 mins with Tim (VP of Engineering), then 45 mins with two or three members of the team With Tim, how you like to work, what you want next, and expectations on both sides. With the team, collaboration style, ownership, and what it's actually like here.Welcome to the team! SalaryAs this is a Europe-wide role, compensation is adapted to the candidate's country of location and aligned with local market benchmarks.70,000 – 95,000 base salary, depending on your country.United Kingdom: 75,000 – 95,000 base salary.The exact package will depend on experience, level of ownership, and demonstrated impact. We'll confirm the specific range for your country before your first interview.