> Markdown version of [/jobs/ext/2893885-associate-product-owner](https://www.wearedevelopers.com/jobs/ext/2893885-associate-product-owner). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Associate Product Owner - **Company:** GlassDollar - **Location:** Berlin, Germany - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Spreadsheets, Restful APIs, Api Management - **Published:** September 14, 2026 - **Apply:** https://www.adzuna.de/details/5881156524 ## About the Role You have personally written the tickets. 3+ years in a product company, where scoping and ticket-writing were actually your job rather than something you handed off. You are technical enough to argue with engineers. AI models, API contracts, estimates, sequencing. You push back with reasons, and you change your mind when the reasons coming back are better. You can write. A spec is a piece of writing. We will ask for a sample where the reasoning is visible, polish second., * 3+ years in a product company, where you personally wrote the tickets * Technical enough to understand a data model, an API contract, and estimation * Demonstrable writing ability, be ready to share a spec, PRD or decision doc Nice to have: * B2B enterprise SaaS background * Familiarity with venture clienting, corporate innovation, or startup-scouting workflows * Notion fluency ## Description The valuable ones pull three threads together: where the product is going, what clients are actually telling us, and the knowledge already sitting in the team. You gather all three before you write, so what lands on the board is specific enough to build and pointed enough to matter. You know what looks good. You have a great sense of design and what feels good for users. We will ask you to build a prototype with AI and illustrate the specs visually. You have worked somewhere small enough that there was nowhere to hide. No layers between you and the consequences of a bad spec. You want to be coached hard. Direct feedback, weekly, on your actual work. You will scope alongside the product lead until you are doing it alone, and the goal is that this happens fast. You are fluent with AI tooling, day to day. We want to see the workflow, not hear it described. You want the scope to grow. The people who do best here end up owning areas outright: the major initiatives, the roadmap arguments, and the questions everyone else brings their doubts to. That is earned, and it is genuinely available. What you`ll do Your job: turn validated opportunities into work an engineer can start on Monday. * Turning opportunities into scoped, sequenced, estimable work: specs, acceptance criteria, edge cases, dependencies * Running the backlog: grooming, prioritisation input, keeping the board honest about what is in flight, blocked, or quietly drifting * Being the interface between customer signal (support threads, CS conversations, call notes) and the engineering queue * Coordinating releases and checking that what shipped matches what was scoped * Presenting product decisions to varied stakeholder groups, from engineers to enterprise clients What you'll be scoping over your first year: * Deep integrations into our customers' organisations. Their systems, their data, their identity stack. This is the work that turns GlassDollar from a tool people visit into infrastructure they run on. * Public REST APIs and MCP servers, so our customers' engineers and their AI agents can build on top of us. * AI embedded across the product, inside the surfaces people already work in. * Workflow automation inside the platform, so the work that used to take six meetings and a shared spreadsheet runs itself. You will need to understand each of these well enough to write the spec and defend it in the room. This is a doing role rather than a people-management one. Mid-to-senior individual contributor.