Senior/Director Product Manager (Claude LLM Integration & MCP Platform)
About the Role
Pixalate is building the next generation of its data platform — and this role leads it as an individual contributor.
As Director of Product Management for LLM Integrations & MCP Platform, you will own:
MCP Server Product Strategy
- Define the tool taxonomy — which data capabilities become MCP tools, what inputs and outputs they expose, and how they are named for natural language discoverability
- Prioritize tool development based on internal use cases (analyst workflows, research, CS) and external use cases (client integrations, developer access, agentic workflows)
- Own the product roadmap from v1 through GA, including feature gates, versioning, and deprecation policy
LLM Integration & Use Case Development
- Design, document, and validate use cases where LLM-powered clients (Claude, ChatGPT, custom agents) query Pixalate's data via MCP
- Write effective, structured tool descriptions and parameter schemas that work well as LLM-readable context — understanding how models interpret tool definitions is essential
- Partner with research and data science to prototype agentic workflows and evaluate output quality, hallucination risk, and response structure
Specification & Execution
- Write TL;DR-format PRDs: a tight problem statement, bullet-pointed requirements, clear input/output contracts, and explicit non-goals — nothing more. Long documents do not ship; concise ones do
- Champion small, shippable iterations over large releases — break every initiative into the smallest version that delivers real value and can be in users' hands quickly
- Define and maintain API contracts between the MCP server and Pixalate's underlying data APIs, including versioning, deprecation, and schema change protocols
- Run structured QA on tool outputs to ensure responses are LLM-friendly, structurally consistent, and free of schema drift
Auth, Access, and Permissioning
- Own the product model for external auth (OAuth 2.0 or API key) and capability-scoped access — defining what each client tier can query
- Collaborate with security and engineering to ensure external MCP deployments meet compliance and data governance requirements
External Developer Experience
- Own developer-facing documentation: tool reference docs, quickstart guides, example prompts, and integration guides for Claude, ChatGPT, and Cursor
- Define the self-serve onboarding flow for external clients connecting to the Pixalate MCP server
- Gather feedback from early adopters and translate it into prioritized improvements
Cross-Timezone Collaboration
- Work fluidly across US, EU, and APAC time zones — scheduling syncs, reviews, and async communication with global engineering and client-facing teams
- Own async-first communication: write clearly enough that nothing needs a follow-up call, and structure updates so stakeholders in any time zone can act on them without waiting
- Adapt availability around key global milestones — external client launches, engineering sprints, and partner reviews that span multiple geographies
This isn't boilerplate — these are real filters for this role. If they resonate, you'll thrive here. If they don't, this is probably not the right fit.
- SPEED OVER PERFECTION
- We ship early and often. A v1 in users' hands beats a v2 in a doc. We bias toward momentum and correct in flight.
- If you are waiting for the perfect spec before starting, you are already behind.