<div class="content-intro"><p>Mentimeter is an engagement company with a simple goal: to make every leader better. Through interaction, insights and recommendations, its platform helps organizations turn participation into better understanding and stronger performance.</p> <p><br>Founded in Stockholm in 2012, Mentimeter is used by 20 million people each month across 1.3 million organizations. At Mentimeter, we believe better leadership starts with listening and that the strongest results are achieved together. That’s why we foster a culture built on curiosity, collaboration and shared ownership. By joining us, you’ll help leaders turn participation into deeper understanding and stronger performance, advancing our ambition to help more than one billion people listen, learn and work better together.</p></div><p>Mentimeter serves hundreds of millions of users with services that we deploy roughly 40 times a week. With transaction loads up to hundreds of votes per second, we have to be sure we can scale while still delivering a fast and smooth experience.</p> <p>We work in small, independent, cross-functional and self-organizing teams. The team's product manager, designer and the product engineers work together to organize and plan the team's backlog with a focus on continuously delivering value to our users.</p> <p>Please note that we are an English-first company, meaning you don't have to know Swedish to work here. Make sure your application and relevant documents are in English.</p> <h3><strong>What you'll do</strong></h3> <ul> <li>Which team you join is something we work out together during the process, based on where you'll have the most impact. The area spans products at real scale and products that barely exist yet.</li> <li>2026 was about proving a multi-tool suite works at all. 2027 is about whether it compounds:</li> <ul> <li>Getting what we launched to a standard we would defend.</li> <li>Adding new ways for a leader to engage a room.</li> <li>Making Menti reachable from wherever people plan their work, including from agents rather than only from our own editor.</li> </ul> <li>That is a lot of surface, a lot of real users, and a lot of decisions that are not made for you.</li> <li>You'll own initiatives that span several components and often several teams, from framing the problem to reading the data afterwards.</li> <li>You'll take an ambiguous product problem and leave the room with success criteria you can measure.</li> <li>You'll name the trade-offs between speed, quality, scalability and risk instead of letting them sit implicit.</li> <li>You'll spend real time with users: joining interviews, reading tickets, watching a session go wrong, and letting that change what gets built.</li> </ul> <h3><strong>Who you are</strong></h3> <ul> <li>You own outcomes, not tickets. You've led work across multiple components and teams, you shape technical direction beyond your own backlog, and you can hold a strong opinion in a design discussion without needing to win it.</li> <li>You care about quality and testing without being precious about the code.</li> <li>The part we're most serious about: we hire product engineers. Right now it matters more that you build the right thing than that you build the thing the right way. Both matter. But we want someone who asks who this is for before asking how to build it, and who treats "the PM will figure that out" as a missed opportunity rather than a division of labour.</li> <li>Working with AI is a requirement here, not a bonus. We're building our own agentic development lifecycle, from intent through to production, and engineers work with agents daily across research, design, implementation and review.</li> <li>You should already be doing this: real opinions on what works and what doesn't, output you read critically rather than ship, and the instinct to push the rest of us forward instead of waiting for a rollout. Autocomplete is not what we mean.</li> <li>Beyond that: excellent communication, comfort working independently and in a team, and an openness to learning and sharing what you find.</li> </ul> <h3><strong>This role might NOT be for you if</strong></h3> <ul> <li>You prefer work to arrive fully specified, with someone else deciding the customer problem, success criteria and trade-offs.</li> <li>You believe product discovery is the PM’s job and engineering starts once the requirements are written.</li> <li>You see your role primarily as implementing a solution, rather than helping decide whether it is the right solution.</li> <li>You consider the job done when high-quality code ships — rather than when you understand whether it changed something meaningful for users or the business.</li> <li>You are not comfortable saying: this is not the problem worth solving, this is too much solution for the evidence we have, or this will not change the user behaviour we need it to change.</li> <li>You want to stay narrowly within one technical layer, or avoid the ambiguity that comes with early-stage product work.</li> </ul> <p>We need engineers who can move between user needs, product choices, technical constraints and production reality and take responsibility for improving all of them. If that is not how you want to work, you will probably find this role frustrating.</p> <p> </p> <h3><strong>The actual coding</strong></h3> <p>TypeScript is the centre of gravity. Our frontend is React with Next.js, and our backend has historically been Ruby but