Senior Product Manager, AI Platform & Ecosystem
.png)
Role overview
Inside Wrike, the Work Intelligence Unit is laying the groundwork for a work delivery platform that serves both people and AI agents. MCP handles permission-aware, secure agent access to Wrike; Skills teach assistants to use it well; and GraphQL supplies the structured layer for reading and changing work data. This Senior PM sets the product direction across all three, with the goal of making Wrike simpler for agents to understand, use and extend.
It is a platform role with wide leverage. You will run the core MCP team directly, give the GraphQL engineering team clear direction on how its capabilities should evolve, and help other Wrike teams ship MCP tools and Skills for the domains they know best. You will also own publication and continuing quality of Wrike's MCP plugin in the AI marketplaces run by OpenAI, Anthropic and Microsoft, working alongside Architecture, Security and customer-facing teams. The posting notes hands-on coding is not required.
What you will do
- Lead the core MCP team and set the roadmap for how outside AI assistants and agents interact with Wrike securely.
- Define MCP standards and equip other Wrike teams to build well-made tools for the domains where they hold expertise.
- Drive discovery and build-out of Skills so agents use Wrike effectively, and codify standards other teams can reuse.
- Give the GraphQL engineering team product direction so its capabilities and the tooling built on it widen the coverage of Wrike Core.
- Own how Wrike's MCP plugin is published, maintained and evolved in AI marketplaces such as Microsoft, OpenAI and Anthropic.
- Set out a clear approach to developer experience, documentation, governance, reliability and quality for MCP.
- Collaborate with internal teams, partners and customers to find the highest-value agent workflows, then refine them using feedback and usage data.
- Turn engineering trade-offs into crisp product calls; writing code is not part of the job.
What the employer is looking for
- 5+ years of product management in enterprise, developer, AI, platform or technical software.
- Working knowledge of MCP and Skills, including how agents rely on tools and guidance to act well.
- Technical fluency across developer experience, reliability, permissions, Skills, MCP and AI agents, without needing to write code yourself.
- Ability to set priorities from feedback, experiments, adoption data and customer research.
- Skill at explaining complex technical ideas plainly to senior stakeholders, partners, customers and engineers.
- Proactive ownership: solve problems as they appear and adjust as you learn.
Good to have
- GraphQL experience and a grasp of structured product data, which the posting calls a major advantage.
Benefits and compensation
- 25 calendar days of paid vacation plus 5 paid uncertified sick days.
- Parental leave of 18 weeks maternity and 4 weeks paternity.
- 2 volunteer days a year.
- Medical insurance for employees and dependents.
- School allowance of up to €600 per month for school-aged children.
- SIM card with unlimited internet, and a lunch allowance (Wolt) at the office on Wednesdays and Thursdays.
About Wrike
Wrike is a work management platform that pulls teams and their work into one place to cut complexity and raise productivity. It operates as a distributed company of more than 1,000 people across nearly every time zone, organised around ten hubs spanning the United States, Japan, Ireland, India, France, Estonia, Czechia, Cyprus, Costa Rica and Australia. Working models span remote, hybrid and co-working, and the company describes its culture as customer-focused, collaborative, creative and committed.
Quick answers
Is this Wrike product manager role remote?
The posting lists the role as Cyprus - Remote and says it can be done remotely from anywhere in the EU, with Prague and Cyprus preferred. Wrike also notes that staff near hubs such as Nicosia typically come into the office around two to three days a week.
What experience does Wrike expect?
At least five years of product management across enterprise, developer, AI, platform or technical software, with working knowledge of MCP and Skills and fluency in agents, permissions, reliability and developer experience. GraphQL experience is a major advantage, and hands-on engineering is not required.
What does the interview process look like?
Four stages: an introduction call with a recruiter, a conversation with the AI Product Director, an interview with Product, Engineering and Architecture representatives, and a final interview with the CPO and HRBP.

DigitalAPI's read on this role
Why this AI Platform & Ecosystem PM role matters in today's APIM market
DigitalAPI's leadership team has run API programmes for Fortune 100 companies and now builds the platform behind them. Here is their take on what this opening really asks for.
What this role says about the market
Wrike is treating its MCP server as a product with its own roadmap, quality bar and marketplace distribution, and that is the pattern DigitalAPI's leadership team expects to spread across SaaS. The interesting part of this brief is federated governance: one team owns the core MCP surface and standards while domain teams contribute their own tools and Skills. That is the same sprawl-and-governance problem API platform teams have faced with gateways for years, now applied to agent tooling. Permission-aware access, reliability and developer experience are named explicitly, and marketplaces such as OpenAI, Anthropic and Microsoft are becoming the developer portal through which agents discover a product.
What to emphasise in your application
- Hands-on experience with MCP servers or Skills, and a clear view of how agents choose and use tools in practice.
- A platform you ran as a product, with standards other teams followed and a mechanism for keeping contributed tools at quality.
- Permission and security thinking: how you gave agents access to enterprise data without breaking existing entitlements.
- Evidence of prioritising from adoption data, experiments and customer feedback rather than internal opinion.
- GraphQL or structured data modelling experience, since the posting singles it out as a major advantage.
For hiring managers
DigitalAPI's leadership team would advise screening for candidates who can describe an MCP tool catalogue the way a good API PM describes a developer portal: discoverable, permission-aware, versioned and measured. Ask how they would stop ten domain teams from shipping ten inconsistent tools, how they would decide what belongs in a Skill versus a tool, and how they would measure whether an agent workflow is actually delivering value. Marketplace listing is distribution; the harder job is governance that scales without a review board.
Our view is that agents are the newest consumer of every API programme, and the portal, or in this case the MCP plugin and gateway behind it, is where that access becomes a product. Wrike's brief is a concrete example of that shift being staffed.
About DigitalAPI
DigitalAPI is the gateway-agnostic command centre for APIs and AI agents. It connects to the gateways an enterprise already runs, Apigee, Kong, AWS API Gateway and Azure API Management, and turns everything behind them into one governed, self-serve catalogue for developers, partners and AI agents. API Gateway, API Portal, API Catalog, API Marketplace, MCP Gateway and MCP Portal ship as one platform.
The company grew out of an API consultancy founded in Bangalore in 2015 that became an Apigee-Google partner in 2017, then built its own cloud-agnostic, AI-powered platform in 2020 after seeing how fragmented gateways and duplicate APIs blocked its clients. More than 240 API teams now use it, with customers such as Zurich, Canara Bank, HSBC, Fiserv and Mahindra Finance. DigitalAPI has offices in the USA, UK and India, 130+ people, and recognition from Gartner and Deloitte.









.avif)
