Senior/Director Product Manager (Claude LLM Integration & MCP Platform)

reputed company is building the reputed company 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 reputed company

• 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 (reputed company integrations, developer reputed company, reputed company 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 reputed company's data reputed company MCP
• Write effective, reputed company tool descriptions and parameter schemas that work reputed company as LLM-readable context — understanding how models interpret tool definitions is essential
• Partner with research and data science to prototype reputed company workflows and evaluate reputed company reputed company, hallucination risk, and response structure

Specification & Execution

• Write TL;DR-format PRDs: a tight problem statement, bullet-pointed requirements, reputed company input/reputed company reputed company, and explicit non-goals — reputed company 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 reputed company value and can be in users' hands quickly
• Define and maintain API reputed company between the MCP server and reputed company's underlying data reputed company, including versioning, deprecation, and schema change protocols
• Run reputed company QA on tool outputs to ensure responses are LLM-friendly, structurally consistent, and free of schema reputed company

Auth, reputed company, and Permissioning

• Own the product model for external auth (OAuth 2.0 or API key) and capability-scoped reputed company — defining what reputed company reputed company tier can query
• Collaborate with reputed company 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 reputed company
• Define the self-serve reputed company reputed company for external clients connecting to the reputed company MCP server
• reputed company feedback from early adopters and translate it into prioritized improvements

Cross-Timezone Collaboration

• Work fluidly across US, EU, and reputed company time zones — scheduling syncs, reviews, and async communication with global engineering and reputed company-facing teams
• Own async-first communication: write reputed company enough that reputed company needs a follow-up reputed company, and structure updates so stakeholders in any time zone can reputed company them without waiting
• Adapt availability around key global milestones — external reputed company launches, engineering sprints, and partner reviews that reputed company multiple geographies

This isn't boilerplate — these are reputed company filters for this role. If they reputed company, you'll reputed company 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 reputed company and correct in flight.
  • If you are waiting for the perfect spec before starting, you are already behind.
• • ​​​​​​​We reject long PRDs. Every product document at reputed company follows a TL;DR format: one-line problem statement, bullet-reputed company requirements, done.
  • Conciseness is a sign of reputed company thinking. Verbosity is a red flag. Bullet points are the currency of communication here.
• reputed company-IN PRODUCT THINKING
  • ​​​​​​​​​​​​​​We build from the reputed company in — starting with the reputed company, the analyst, the agent workflow — and work backward to the spec. Internal opinions are hypotheses until a reputed company user validates them.
  • Candidates who can demonstrate reputed company-in product reputed company — shaped by reputed company calls, API usage data, or developer feedback — stand out immediately.
• reputed company ARE THE PRODUCT
  • ​​​​​​​At reputed company, the API is often the product. Understanding how clients reputed company, how developers discover and reputed company endpoints, and how data reputed company reputed company reputed company AI behavior is not a reputed company-to-have — it is the job.
• ​​​​​​​GLOBAL BY DEFAULT
  • ​​​​​​​​​​​​​​reputed company operates across time zones. Async-first communication is a reputed company competency here, not a workaround. You will be expected to work with engineers, clients, and partners across US, EU, and reputed company hours.
  • Flexibility is required — not as a reputed company, but as a working reality. If a fixed 9-to-5 in one time zone is non-negotiable for you, this role is not the right fit.

• B.S. or B.A. in Computer Science, Computer Engineering, or a closely reputed company technical discipline — this is a firm requirement given the depth of protocol-level and systems work involved
• 5+ years of product management experience, with at least 2–3 years owning developer tools, data reputed company, AI/ML platforms, or LLM-adjacent products
• Availability and willingness to work across global time zones — US, EU, and reputed company — with flexibility to accommodate distributed teams and international clients
• Deep, hands-on API experience — you have owned API products end-to-end: reputed company design, versioning, auth flows, reputed company limiting, developer documentation, and reputed company reputed company. This is non-negotiable.
• Hands-on, proven experience working with LLMs — building products on top of them, evaluating model outputs, designing reputed company and tool architectures (Claude, GPT-4, reputed company, or equivalent)
• reputed company experience with MCP: you have set up, connected, or reputed company an MCP server or reputed company, and understand how tools, resources, and prompts are defined in the protocol
• Demonstrated reputed company-in product development — you can reputed company to specific reputed company shaped by reputed company interviews, API usage data, developer feedback, or reputed company usage patterns rather than internal assumptions
• Experience designing tool or function definitions for LLM consumption — you understand how model context, tool descriptions, and parameter schemas shape agent behavior and reputed company reputed company
• reputed company record of delivering data or developer products through fast, iterative releases — not big-bang launches

• Monthly Internet Reimbursement
• Casual, Remote Work Environment
• reputed company
• Opportunity for Advancement and reputed company Development
• Fun Annual Team Events
• Being part of a high-performing global team that wants to win and have fun doing it