Senior Product Manager
Leena AI
Product
Gurugram, Haryana, India
Posted on Jun 9, 2026
About Leena AI
Leena AI is a leader in Agentic AI for the enterprise. We are building an iconic company, delivering AI Colleagues that transform back-office functions and accelerate the full promise of Generative AI - unlocking real productivity gains, cutting costs, and delighting employees at scale.
Leena AI provides the most forward-looking, open, and scalable Agentic AI architecture for the enterprise - it empowers CIOs and CTOs to develop, deploy, and manage AI Colleagues for the back office at scale. Built with full governance, compliance, security, and auditability at its core.
Leena AI integrates with 1000+ applications, including SAP, Salesforce, ServiceNow, Workday, and Microsoft Office 365. We are proud to be trusted by 500+ global enterprises and 20 million+ employees, including leading brands such as Nestlé, Puma, Coca-Cola, Sony, and Etihad Airways.
Founded in 2018 and headquartered in New York, Leena AI has secured over $40M in financing from top-tier investors including Greycroft, Bessemer Venture Partners, B Capital, and Y Combinator.
About The Knowledge Management POD
The KM POD owns the end-to-end knowledge layer: connectors and sync from SharePoint, ServiceNow KB, Confluence, Google Drive, and dozens of other sources; ingestion and chunking; retrieval quality; admin workflows for curating and governing knowledge; and the analytics that tell admins where their KB is failing.
What You Will Own
You have run a product area where weekly decisions routed through four to six senior stakeholders - Eng leadership, CS, Sales, founders. You can walk us through a specific case where you held a line under pressure, or built alignment on a contested direction, and explain why it held. We are not looking for someone who routes; we are looking for someone who decides and carries the room.
End-to-end systems thinking
You reason about backend scalability (indexing cost, sync throughput, retrieval latency at 10M+ documents across hundreds of tenants) and admin-facing DIY experience (what the Builder sees when KB coverage drops, how they fix it themselves) as one problem, not two. We have been burned by PMs who optimized one end at the expense of the other; we will probe for this in a live design exercise.
Metric decomposition and structured bets
You do not just recite the north star — you break it down. Given "knowledge-grounded resolution rate," you should be able to sketch the input tree (ingestion coverage × retrieval precision × answer grounding × admin remediation loop), identify the two or three highest-leverage inputs for the next quarter, and propose a sequenced set of bets with expected movement. If your answer to "how will you improve the metric" is a list of features rather than a model of the metric, this role is not for you.
Focus under heavy context switching
The KM POD sits at the intersection of enterprise integrations, RAG infrastructure, admin UX, and live customer escalations. In a single afternoon you will be pulled into a connector bug, an RFP security response, and a roadmap review. We want to hear how you protect deep work, sequence what matters, and resist becoming a router for everyone else's urgency.
Structured external communication
You can run a QBR, a technical deep-dive, or an escalation call with a Fortune 500 CIO's team and leave the room with decisions, not just sentiment. You separate "what we heard" from "what we will do," you commit specifically without over-promising, and you sound like a peer writing to a CIO, not a vendor writing to a customer. We will test this directly in the assessment — in writing and live.
CIO fluency
You have shipped to CIO buyers. You understand that "trust" for a CIO means data residency, audit trails, sub-processor transparency, and the ability to explain a wrong answer — not just model quality.
Experience
Leena AI is a leader in Agentic AI for the enterprise. We are building an iconic company, delivering AI Colleagues that transform back-office functions and accelerate the full promise of Generative AI - unlocking real productivity gains, cutting costs, and delighting employees at scale.
Leena AI provides the most forward-looking, open, and scalable Agentic AI architecture for the enterprise - it empowers CIOs and CTOs to develop, deploy, and manage AI Colleagues for the back office at scale. Built with full governance, compliance, security, and auditability at its core.
Leena AI integrates with 1000+ applications, including SAP, Salesforce, ServiceNow, Workday, and Microsoft Office 365. We are proud to be trusted by 500+ global enterprises and 20 million+ employees, including leading brands such as Nestlé, Puma, Coca-Cola, Sony, and Etihad Airways.
Founded in 2018 and headquartered in New York, Leena AI has secured over $40M in financing from top-tier investors including Greycroft, Bessemer Venture Partners, B Capital, and Y Combinator.
About The Knowledge Management POD
The KM POD owns the end-to-end knowledge layer: connectors and sync from SharePoint, ServiceNow KB, Confluence, Google Drive, and dozens of other sources; ingestion and chunking; retrieval quality; admin workflows for curating and governing knowledge; and the analytics that tell admins where their KB is failing.
What You Will Own
- The KM roadmap, from connector breadth to retrieval quality to admin DIY tooling.
- A clearly articulated north star (e.g., knowledge-grounded resolution rate) with a decomposed tree of input metrics, owners, and quarterly movement targets.
- The DIY admin experience — how a Builder at a Fortune 500 onboards, curates, monitors, and improves their KB without raising a ticket with us.
- Cross-functional alignment with Engineering, Design, CS, Solutions, and Sales on a single prioritized backlog.
- Customer-facing presence in pre-sales, QBRs, and escalations where KM is the topic.
You have run a product area where weekly decisions routed through four to six senior stakeholders - Eng leadership, CS, Sales, founders. You can walk us through a specific case where you held a line under pressure, or built alignment on a contested direction, and explain why it held. We are not looking for someone who routes; we are looking for someone who decides and carries the room.
End-to-end systems thinking
You reason about backend scalability (indexing cost, sync throughput, retrieval latency at 10M+ documents across hundreds of tenants) and admin-facing DIY experience (what the Builder sees when KB coverage drops, how they fix it themselves) as one problem, not two. We have been burned by PMs who optimized one end at the expense of the other; we will probe for this in a live design exercise.
Metric decomposition and structured bets
You do not just recite the north star — you break it down. Given "knowledge-grounded resolution rate," you should be able to sketch the input tree (ingestion coverage × retrieval precision × answer grounding × admin remediation loop), identify the two or three highest-leverage inputs for the next quarter, and propose a sequenced set of bets with expected movement. If your answer to "how will you improve the metric" is a list of features rather than a model of the metric, this role is not for you.
Focus under heavy context switching
The KM POD sits at the intersection of enterprise integrations, RAG infrastructure, admin UX, and live customer escalations. In a single afternoon you will be pulled into a connector bug, an RFP security response, and a roadmap review. We want to hear how you protect deep work, sequence what matters, and resist becoming a router for everyone else's urgency.
Structured external communication
You can run a QBR, a technical deep-dive, or an escalation call with a Fortune 500 CIO's team and leave the room with decisions, not just sentiment. You separate "what we heard" from "what we will do," you commit specifically without over-promising, and you sound like a peer writing to a CIO, not a vendor writing to a customer. We will test this directly in the assessment — in writing and live.
CIO fluency
You have shipped to CIO buyers. You understand that "trust" for a CIO means data residency, audit trails, sub-processor transparency, and the ability to explain a wrong answer — not just model quality.
Experience
- 6–9 years in product management, with at least 3 years shipping enterprise SaaS to CIO, CTO, or CHRO buyers.
- Prior ownership of a platform area involving integrations, retrieval/search, or knowledge systems.
- Comfort reading code, logs, and SQL — this POD lives close to the infrastructure.
- You have rewritten a PRD after a week because the first version was not a real bet.
- You can name the three metrics your last product lived or died by, and what moved them.
- You have said no to a large customer and kept the account.
- Engineering degree from tier 1 university
- Background in RAG, hybrid search, ranking, or enterprise knowledge graphs.
- Hands-on experience with HRIS/ITSM ecosystems (ServiceNow, Workday, SharePoint, Confluence).