EU remote
Senior Software Engineer
About this role
Large organisations consistently make important decisions without the intelligence they already own — because they can't find what they have, can't see what they're missing, and can't act on it fast enough to matter. We are Stravito and this is the problem we solve. Stravito transforms how Consumer Insights professionals and Brand Managers work by building AI that automates their core workflows. We help world-leading organizations accelerate strategic decision-making by turning millions of market research documents into intelligent systems that generate reports, discover insights proactively and synthesize knowledge across vast content libraries.
We really mean it when we say we're a diverse and international team as our team of 100 has more than 30 different nationalities! We are guided by our operating principles: simplicity first, an “own it, do it” mentality, embracing different perspectives, and enjoying the journey together. We're now looking for a Senior Software Engineer to join our Continuity team. The mission Make the seam invisible. Stravito has two sides: the evidence base that insights teams build and govern, and the decision tools that commercial teams use to act on it.
Continuity is the team in between. We own everything both sides meet. As a Senior Software Engineer in Continuity, you'll own the services behind those surfaces and build the frontend on top of them. You'll keep today's product stable and fast while new spaces go up alongside it, and make sure a user moving between them never notices where one team's work ends and another's begins. What makes this role unique The whole product is your canvas.
Continuity touches nearly every screen a user sees, so your work shapes the experience of every Stravito customer, not one feature. Full ownership, end to end. You'll take a capability from data model to API to UI, without handing it over a wall. Platform thinking with a product lens. Several of our areas are shared pieces other teams build on. You'll design them so other teams can plug in cleanly. What you'll do Own the library backend: evolve the services and data models behind the features owned by the team, and keep them reliable as usage grows.