About the Role
<p style="min-height:1.5em"><strong>This role is open only to candidates living in the EU or EEA. We can't consider applications from other locations.</strong></p><p style="min-height:1.5em"></p><h2>If you've built something before, start here</h2><p style="min-height:1.5em">The hardest part of a startup usually isn't the code. It's finding customers who really need what you build and getting them to change how they work. At Scalera, that part is done: manufacturers, suppliers and contractors across Switzerland, Austria and Germany already run their tenders through us every day.</p><p style="min-height:1.5em">What we need now are people who can take the next unsolved problem and turn it into a product customers can't do without. If you've founded a company (whether it worked out or not), been the first engineer somewhere, or built something people paid for, this role was written for you.</p><p style="min-height:1.5em"></p><h2>About Scalera</h2><p style="min-height:1.5em">Scalera is an ETH Zurich spin-off building AI for the €200B+ European construction industry. Large manufacturers and suppliers still run their most document-heavy processes by hand, from reading 300-page tenders to retyping purchase orders into their ERP. We automate them one by one. Our product matching already handles 1,400 tender positions in 16 minutes at 98% precision, work that used to take a sales rep most of a day.</p><p style="min-height:1.5em"></p><h2>What you'll do</h2><p style="min-height:1.5em">You'll be part product manager, part engineer. You'll spend real time with customers and help shape what we build. Sometimes you'll spot the next problem yourself, and sometimes we'll hand you a clear priority to run with.</p><ul style="min-height:1.5em"><li><p style="min-height:1.5em"><strong>Spend real time with customers.</strong> Join calls and site visits, sit with the people who do the work, and understand why they do it the way they do. You'll know their problems firsthand, not from a ticket.</p></li><li><p style="min-height:1.5em"><strong>Shape what to build.</strong> Turn what you hear into a clear problem, a scope and a plan, and push back when the obvious request isn't the real need. When we bring you a priority, you'll own how it gets solved.</p></li><li><p style="min-height:1.5em"><strong>Build it.</strong> Design and build backend services in Go and Python that turn messy tenders, catalogs and purchase orders into data customers can rely on.</p></li><li><p style="min-height:1.5em"><strong>Ship, then check.</strong> Get it in front of customers fast, watch how they actually use it, and iterate.</p></li><li><p style="min-height:1.5em"><strong>Own it in production.</strong> When something breaks at a customer, it's yours to understand and fix.</p></li><li><p style="min-height:1.5em"><strong>Build with AI.</strong> Use AI heavily in how you work, and design systems that agents can use as well as people.</p></li></ul><p style="min-height:1.5em"></p><h2>What success looks like after 3 months</h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">There's a part of the product people now think of as yours, and you're the one deciding what happens to it next</p></li><li><p style="min-height:1.5em">You've spotted a problem nobody asked you to solve, made the case for it, and shipped a first version</p></li><li><p style="min-height:1.5em">You've shipped features from both sources: priorities we set and ideas from your own customer conversations</p></li><li><p style="min-height:1.5em">At least once, you've talked us out of building something customers didn't really need</p></li><li><p style="min-height:1.5em">You've left a part of the platform simpler than you found it</p></li></ul><p style="min-height:1.5em"></p><h2>You'll probably thrive here if</h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You've taken something from zero to one: a company, a product line, or a side project with paying users</p></li><li><p style="min-height:1.5em">You've built and run backend systems in production that other people depend on. We care more about your judgment than your language; you're strong in Go or Python and happy to work in both</p></li><li><p style="min-height:1.5em">You're solid on data modeling, API design and messy real-world data</p></li><li><p style="min-height:1.5em">You'd rather talk to a customer than wait for a spec</p></li><li><p style="min-height:1.5em">You're comfortable with ambiguity. You can make progress while the problem is still half-defined, which at a startup it usually is</p></li><li><p style="min-height:1.5em">You want a large scope of responsibility and are happy to own things well beyond your job title</p></li><li><p style="min-height:1.5em">Rapidly changing requirements don't throw you. When customers or priorities shift, you adapt and keep going</p></li><li><p style="min-height:1.5em">You enjoy direct customer contact and want to be on customer calls</p></li><li><p style="min-height:1.5em">