Technical Product Manager; Integrations & Connectors

• Get to know our customers. Your first weeks are all about listening. You’ll talk to customers and find out what it takes for our REST API and connectors to become part of their daily work. Together with Engineering, Customer Success and Sales, you’ll turn those insights into a clear roadmap. You’ll also set up the tracking that shows how much of our customers’ work flows in through integrations
• Launch the first API improvements and our first MCP server. You’ll shape both, write the engineering tickets and roll them out to our first pilot customers, all within your first few months
• Decide what comes next. Once real usage data and pilot feedback come in, you’ll make clear recommendations on what to build and decide on the way forward together with our CTO and Head of Product
• Make integrations the norm. By the end of your first year, far more of our customers will run Cosuno connected to the tools they rely on, and you’ll be the one who made it happen
• It’s an ambitious plan, and that’s what makes it fun: you’ll see the impact of your work directly in our customers’ day-to-day
• Full ownership:
  You own integrations end to end, from the first customer conversation to the shipped feature. Engineering takes care of the implementation
• Close to the customer:
  You’ll talk to customers constantly, mostly remotely, sometimes on-site across Germany
• Technical by nature:
  You’ll read API docs, test endpoints yourself and discuss data models with engineers. You don’t write production code
• AI-first:
  We use AI deeply in our product and in our daily work, and we expect you to do the same

• Working fully remote or from our office in Berlin
• Modern work equipment
• Company offsites and regular team events (offline and online)
• Flexible working hours
• Possibility to do workations

You write tickets engineers love. Clear scope, clear acceptance criteria, and a clear line on what’s out of scope. You prioritize by impact, not by who shouts loudest

You’re technical enough to go deep with engineers. Webhooks vs. polling, pagination, rate limits, OAuth: you can discuss trade-offs, and you test APIs yourself

You live AI. You use LLM assistants and MCPs every day, and you’ve built your own automations

You keep growing. You actively build your skills, and you seek and act on feedback

You’ve shaped an API from the product side. You’ve defined, together with customers and engineering, what a public API or integration of a SaaS product exposes: endpoints, data models, auth, permissions

You find the real need. You’ve worked directly with customers, separated what they ask for from what they really need, and found what it takes for them to use an integration

Bonus points if you’ve helped build an MCP server that customers use, or if you know construction tech, ERP or estimating systems (e.g. RIB iTWO, SAP, Nevaris)
You’re fast. You ship in weeks, not quarters, and you build, learn and iterate in parallel

Based in Germany and open to traveling to customers across the country

Fluent German and English. Our customers are German construction companies who work in German. Our engineering team works in English You explain complex things simply, to a construction company’s project manager as well as to internal stakeholders like our commercial teams or our management