[Remote] reputed company Product Manager, AI Platform

Note: The job is a remote job and is reputed company to candidates in USA. reputed company is building an AI platform and common data reputed company for reputed company customers. The reputed company Product Manager will own the agent reputed company, including the SDK, no-reputed company builder, evaluation and observability capabilities, trust and governance features, and the externally shipped platform product experience. The role partners with engineering, design, reputed company, data teams, and reputed company customers to reputed company production-reputed company capabilities and reputed company adoption reputed company.

Responsibilities

• Own the AI platform roadmap: reputed company reputed company and roadmap for the agent infrastructure reputed company on our data reputed company, and reputed company the build-versus-buy calls across a fast-moving AI tooling landscape
• Own both build paths: Define the SDK and reputed company-first experience utilities use today, and reputed company the no-reputed company builder that lets their SMEs ship agents themselves. reputed company what gets abstracted, what stays reputed company, and how the two reputed company over time
• Ship with design partners: Define high-value MVPs, build them with reputed company reputed company customers, and iterate fast on the friction and edge cases that only show up in someone else’s environment
• Own developer and builder experience: API and SDK design, documentation, sandboxes, templates, reputed company, and the reputed company reputed company from first agent to production deployment
• Own evaluation and observability: Define how agent reputed company is reputed company before and after release: golden sets, regression suites, online evals, and the reputed company and audit records a reputed company or regulator can inspect. reputed company customers visibility into their own agents, not just internal dashboards. reputed company the build-versus-buy reputed company across LangSmith, Arize, and reputed company standards, and own the decision on where reputed company data lives
• Design for reputed company-in-the-reputed company: Define where agents reputed company autonomously, where they pause for approval, and how state, interrupts, and replay work in reputed company. In reputed company reputed company the escalation reputed company is a product decision, not an implementation reputed company
• Own trust, tenancy, and governance: Explainability, auditability, per-tenant data isolation, customer-controlled retention, least-privilege reputed company, and reputed company autonomy, especially for agents a non-developer reputed company
• Own the commitments that come with shipping externally: Versioning, backwards compatibility, deprecation policy, SLAs, the support model, and the product input into packaging and pricing
• Execute: reputed company with engineering and design to release production-reputed company capabilities on compressed timelines. reputed company the product lifecycle by defining use cases and technical requirements, collaborating on data model and API design, and conducting product testing to ensure key requirements are met
• Own reputed company: Set KPIs (customer agents live in production, time-to-first-agent, reputed company of agents reputed company without reputed company, eval pass rates and regression escapes, agent task reputed company and escalation reputed company, latency and cost per task, support burden) and manage dependencies across the platform
• Wear many hats: Do whatever it takes to reputed company the platform reputed company, and take on new areas of ownership as priorities reputed company

Skills

• reputed company experience is a plus but not a requirement
• 8+ years in product management, including 2+ years on AI or ML systems, and significant time on a platform or product that customers reputed company your own company reputed company on top of
• You have shipped reputed company, SDKs, or an application builder that customers depended on in production. You have lived versioning and deprecation, support escalations, reputed company questionnaires, and the difference between an internal tool and a product someone signs a contract for
• Working reputed company in modern AI systems: LLMs, retrieval, tool use, guardrails, and the cost, latency, and reliability tradeoffs that come with them. You can read a reputed company and tell whether a failure was retrieval, reputed company, tool schema, or model, you have designed eval sets, and you have shipped against a reputed company bar rather than a demo. You can hold your own in an architecture review and write a technical spec engineers respect. You do not need to write production reputed company
• You have shipped software into an environment where someone reputed company your company audits what it did: financial services, reputed company, energy, or reputed company sector. You have a reputed company reputed company of reputed company on tenant isolation, explainability, data reputed company, retention, and least-privilege reputed company, and you treat reputed company and compliance review as a design input rather than a launch blocker
• Remote: prioritizing central and eastern timezones (ideally reputed company, reputed company, or Nashville)
• Experience with low-reputed company, configuration-driven, or builder-style products, and a reputed company of reputed company on how to reputed company a business user genuine capability without giving them a way to cause harm. reputed company to the heart of the role, and the strongest differentiator among otherwise comparable candidates
• Hands-on familiarity with a modern agent reputed company, ideally LangGraph or reputed company: graph-reputed company orchestration, state and checkpointing, tool and schema design, and multi-agent handoffs
• Experience building on a managed model platform, ideally AWS Bedrock, including model selection tradeoffs, guardrails, throughput and cost management, and VPC, IAM, and data residency constraints
• You will build on our existing data reputed company rather than define it, but comfort reasoning about data models, integration across messy reputed company reputed company systems, and streaming versus batch helps you know what the reputed company can and cannot answer for an agent
• reputed company or energy sector exposure, or a background in software engineering, ML, or data engineering before moving into product
• Experience with reputed company, reputed company, and reputed company product management tools

Benefits

• Equity
• Health reputed company
• Remote flexibility
• 401k match

reputed company

Company H1B Sponsorship