Senior Technical PM, Applied AI
Free to start · No card · 5 credits the moment you sign up
Job description
About the Company:
This role is also firmly hands-on. You will work directly with AI labs, understand new model capabilities early, build experiments and prototypes yourself, design evaluations and debug failing agents. You use that hands-on work to make better, faster product decisions.
Product and business ownership
- Business focus: tie the roadmap to measurable business outcomes such as autonomous resolution rate, cost per resolution, CSAT, revenue expansion and competitive wins. Know where Netomi wins and loses against competitors, and shape our position.
- Product strategy and roadmap: own the multi-quarter roadmap for Agents end to end, from problem discovery and prioritization to delivery and outcome tracking. Make and defend hard trade-offs when priorities compete.
- Customer and partner needs: work directly with enterprise customers, Customer Success, Delivery and Sales to find the highest-value problems. Translate them into clear problem statements, PRDs, user stories, success metrics and dependency maps.
- Cross-functional leadership: drive alignment across engineering, research, data science, QA and go-to-market on scope, dependencies and launch readiness, without direct authority.
- Planning and execution: run the cadence of quarterly roadmap inputs, monthly scope lock, weekly execution reviews and launch readiness sign-offs.
- Launch and adoption: own launch checklists (instrumentation, enablement, success criteria), track adoption per capability and publish a monthly Agent Outcomes readout across deployments.
- Post-release learning: run monitoring windows and post-incident reviews, and feed what you learn back into the roadmap.
Product areas you will own
- Agent reasoning and orchestration: multi-step task planning, action selection, retry and fallback logic, and supervisor and sub-agent patterns.
- Tool and API use: reliable, observable, policy-compliant tool calling for CRM, ITSM and custom enterprise systems, including MCP.
- Memory and context: conversation memory, long-running task state and continuity across channels and sessions.
- Human-in-the-loop: clarification, graceful escalation to live agents, approval steps for high-risk actions and hybrid autonomy modes.
- Enterprise governance: guardrails, audit trails, explainable decisions, role-based access, and safe rollout through shadow mode, staged releases and rollback.
Hands-on work
- AI labs and new capabilities: be our product point person with AI labs and model providers. Test new models and features (reasoning, tool use, realtime voice, memory) on our use cases, decide what to build, change or skip, and give labs evidence-based feedback.
- Experiments and prototypes: vibe code prototypes, build agents, and connect them to real systems through APIs and MCP tools. Run offline tests, shadow mode and canary releases with clear decision criteria, and hand engineering a working reference, not just a document.
- Evaluation and quality: define the Agent Readiness Scorecard and Go/No-Go criteria. Design evals for task completion, tool success, policy compliance, latency and cost, and keep regression tests running on every model, prompt or tool change.
- Debugging production failures: read agent traces with engineering, find root causes (wrong action, missed escalation, bad tool call, memory gaps) and make sure each serious failure gets a fix and a test.
- Model choices: inform model selection and routing decisions by weighing quality, latency and cost with real data.
Requirements
- Roughly 4–8 years of relevant experience, ideally from a deeply technical product role, applied AI engineering or research engineering with clear product ownership.
- Proven ownership of a complex technical product area, with features delivered to enterprise customers and measurable business results.
- Strong product judgment: you can prioritize, work with customers and get capabilities shipped.
- Customer-first: you turn enterprise needs into clear, actionable requirements.
- Excellent communicator who can align engineering, research and go-to-market teams and present clearly to executives. Hands-on skills
- Comfortable vibe coding, building agents, connecting APIs and MCP tools, designing evaluations and debugging production failures.
- Deep understanding of LLM reasoning, tool calling, multi-step task execution, orchestration patterns, evaluation methods and production observability for agents.
- Technical fluency with APIs, cloud environments and AI deployment workflows.
Nice to have
- Experience shipping AI agent products at a conversational AI or enterprise AI platform company.
- Direct experience working with AI labs or model providers (early-access programs, model evaluations).
- Familiarity with agent frameworks and protocols (e.g., LangGraph, MCP) and with voice AI.
- Experience in regulated or mission-critical industries (airlines, banking, healthcare, payments) and with large SI partners.
- Public work you can show: a repo, demo, blog post or talk.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Netomi. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.