Must-have
- Structured thinking. You can take a messy stream of requests and impose order - categorize, score, sequence, and defend the sequence. This is the single most important trait.
- Strong communication across audiences. You write clear specs, run a clean backlog, and can hold a conversation with a developer and an account manager in the same afternoon without losing either. You're comfortable pushing back and saying "not now" with a reason.
- Ownership and follow-through. You chase blockers, keep things from going silent, and close loops.
- Comfortable operating under direction. You bring structure and a point of view while executing against priorities set by leadership. You want autonomy on how, not final say on what.
- Fluent AI usage. You work AI into your daily workflow - not as a novelty, but as leverage. You understand agents and MCPs (Model Context Protocol), can design and run AI workflows to automate research, spec-writing, triage, and reporting, and can reason about where AI fits (and where it doesn't) in a product process.
Strong bonus
Amazon Advertising knowledge. Familiarity with Sponsored Products/Brands/Display, DSP, bidding strategies, budget/lookback mechanics, ASIN structures, and AMC. This lets you reason about trade-offs independently and is the highest-leverage bonus.
Nice to have
- Technical literacy - enough to talk credibly with engineers about APIs, data models, migrations, and feasibility. You don't need to code, but you shouldn't be intimidated by a technical conversation. Familiarity with SQL/MariaDB, data pipelines, and third-party APIs is a plus.
- German - the dev team is Darmstadt-based and much internal communication is in German; Account Managers are international. Bilingual DE/EN is a practical advantage, not a must
- B2B SaaS product experience, ideally in ad-tech, e-commerce, or the Amazon ecosystem.
- n8n (or similar workflow automation) - hands-on experience building automations in
n8n, Make, Zapier, or comparable tools, especially wiring AI steps into multi-step workflows.
The prioritization mandate
No formal prioritization system exists today — building one is the core deliverable. In your first
weeks we'd expect you to stand up:
- A single intake funnel for requests from Account Managers, clients, leadership, and dev, so nothing lives only in a chat thread.
- A scoring model weighting business impact, reach, effort/feasibility, and strategic fit (a RICE- or weighted-scoring-style framework is a reasonable start).
- A review-and-communicate cadence tied into existing product and Customer Growth rhythms.
- Transparency back to the business so Account Managers and clients can see where a request stands.
Leadership keeps the final call on priorities; you own the machinery that makes those calls fast, consistent, and defensible.
Who thrives hereSomeone unusually organized who writes well and is energized by building order rather than
needing a mature product org to slot into - who has been the connective tissue between
engineering and a commercial team before. This role is roughly 70% execution and ordermaking,
not vision decks. If you love backlog craft, clear specs, and closing loops, you'll do well.