Product Manager at Hevodata in Bengaluru, Karnataka, India

Product Manager - Hevo The Hard Thing About Data Most companies that claim to have a "data platform" have a dashboard with some charts and a dream. Hevo has something different. Something that took eight years to build and can't be bought. Over 2,000 companies send us their most sensitive data every single day. 100 billion events a month. Raw. Unfiltered. Before transformation, before aggregation, at the exact moment truth is created. That's not a product feature. That's trust, earned one customer at a time, over eight years, by not screwing up. That position is now the foundation for something much bigger. We're building an Intelligence Layer on top of it, a system that reads across every data source a company runs, connects the signals that matter, and tells people what to do before they have to go looking for answers. We call it the Context Graph. It's real enough to show results. Early enough that the person who joins now defines what it becomes. This is the moment. Not the moment after it's obvious. Now. What You're Walking Into You'll own a product pod. SaaS integrations, database connectors, or the Intelligence Layer, depending on where the biggest need is when you join. You own the backlog. More importantly, you own the why behind everything that gets built. You report directly to the CEO. In the first 3-6 months, your job is to make the foundation bulletproof, find the gaps in the platform, close them, and make the product sharper than it's ever been. After that, you move into the Intelligence Layer and help define what Hevo becomes in its next chapter. What This Job Actually Is Let's be honest about what great PMs do, and what mediocre ones do instead. Mediocre PMs write specs and hand them off. They synthesize feedback from CSMs and call it customer insight. They sit in architecture meetings and nod. They measure their own output in documents shipped, not outcomes delivered. That's not this job. This job is three things, done well, simultneously. First: technical ownership. You will be in the room when architecture decisions get made. Not watching. Contributing. Pushing back. Asking the questions that change the direction of the decision. You need to understand how data pipelines work at a systems level, CDC, connectors, streaming, schema management, failure modes. If you can't hold your own in that room, engineering will stop inviting you to it. And they'll be right to. Second: direct customer engagement. You talk to customers yourself. No intermediary. No secondhand summary. You hear the problem in the customer's own words, you sit with the complexity of it, and you own the translation into product decisions. If you're relying on a CSM to tell you what customers need, you will always be one step behind. Third: making complexity simple. Hevo's product is deeply technical. The people who sell it and support it are not always. A big part of your job is taking complex system behavior and making it crisp and understandable, for Support, for CS, for Solutions Engineering, so they can represent the product confidently to customers. If internal teams are confused, customers will be too. Who We're Looking For 6-8 years of product experience. Meaningful time on platform or infrastructure products at B2B companies. Not optional. Strong technical depth. CS degree or equivalent engineering background. You should be able to hold a real conversation about system design, data architecture, API design, and engineering tradeoffs, not a surface level one. Proven ability to engage directly with customers. Not customer research. Not user interviews handed to you by a researcher. Direct engagement, gathering requirements, presenting product direction, handling objections in real time. Clear, structured communication. Written and verbal. You can make a complex system understandable to a non-technical audience without sacrificing accuracy. This is rarer than it sounds. High ownership. You don't wait for conditions to be perfect. You move. You iterate. You follow through. When you say you'll do something, it gets done. Nice to have: Engineer-turned-PM. Experience at a Series A-C company where you had to balance speed with quality. Familiarity with the data integration and pipeline landscape. What Good Looks Like in Year One After 12 months, a great hire will have: Full, unambiguous ownership of their pod's backlog, with a defensible point of view on priorities that's grounded in customer reality and business impact. Identified and closed the most critical gaps in their product area, with improvements that customers and internal teams can actually feel. Built enough technical depth to shape architecture decisions, not observe them. Become the person in the company most connected to what customers actually need from their product area. Made internal teams measurably better at representing the product. Started actively shaping the Intelligence Layer, contributing product thinking and customer insight as Hevo moves into its next chapter. The Moment Hevo spent eight years building both a product and a business simultaneously, and the foundation is real. The Intelligence Layer is early. The window to define what it becomes is open right now. Most people will look at this moment in five years and wish they'd been here for it. If you're one of the people who wants to be here for it, let's talk. Product Manager - Hevo The Hard Thing About Data Most companies that claim to have a "data platform" have a dashboard with some charts and a dream. Hevo has something different. Something that took eight years to build and can't be bought. Over 2,000 companies send us their most sensitive data every single day. 100 billion events a month. Raw. Unfiltered. Before transformation, before aggregation, at the exact moment truth is created. That's not a product feature. That's trust, earned one customer at a time, over eight years, by not screwing up. That position is now the foundation for something much bigger. We're building an Intelligence Layer on top of it, a system that reads across every data source a company runs, connects the signals that matter, and tells people what to do before they have to go looking for answers. We call it the Context Graph. It's real enough to show results. Early enough that the person who joins now defines what it becomes. This is the moment. Not the moment after it's obvious. Now. What You're Walking Into You'll own a product pod. SaaS integrations, database connectors, or the Intelligence Layer, depending on where the biggest need is when you join. You own the backlog. More importantly, you own the why behind everything that gets built. You report directly to the CEO. In the first 3-6 months, your job is to make the foundation bulletproof, find the gaps in the platform, close them, and make the product sharper than it's ever been. After that, you move into the Intelligence Layer and help define what Hevo becomes in its next chapter. What This Job Actually Is Let's be honest about what great PMs do, and what mediocre ones do instead. Mediocre PMs write specs and hand them off. They synthesize feedback from CSMs and call it customer insight. They sit in architecture meetings and nod. They measure their own output in documents shipped, not outcomes delivered. That's not this job. This job is three things, done well, simultneously. First: technical ownership. You will be in the room when architecture decisions get made. Not watching. Contributing. Pushing back. Asking the questions that change the direction of the decision. You need to understand how data pipelines work at a systems level, CDC, connectors, streaming, schema management, failure modes. If you can't hold your own in that room, engineering will stop inviting you to it. And they'll be right to. Second: direct customer engagement. You talk to customers yourself. No intermediary. No secondhand summary. You hear the problem in the customer's own words, you sit with the complexity of it, and you own the translation into product decisions. If you're relying on a CSM to tell you what customers need, you will always be one step behind. Third: making complexity simple. Hevo's product is deeply technical. The people who sell it and support it are not always. A big part of your job is taking complex system behavior and making it crisp and understandable, for Support, for CS, for Solutions Engineering, so they can represent the product confidently to customers. If internal teams are confused, customers will be too. Who We're Looking For 6-8 years of product experience. Meaningful time on platform or infrastructure products at B2B companies. Not optional. Strong technical depth. CS degree or equivalent engineering background. You should be able to hold a real conversation about system design, data architecture, API design, and engineering tradeoffs, not a surface level one. Proven ability to engage directly with customers. Not customer research. Not user interviews handed to you by a researcher. Direct engagement, gathering requirements, presenting product direction, handling objections in real time. Clear, structured communication. Written and verbal. You can make a complex system understandable to a non-technical audience without sacrificing accuracy. This is rarer than it sounds. High ownership. You don't wait for conditions to be perfect. You move. You iterate. You follow through. When you say you'll do something, it gets done. Nice to have: Engineer-turned-PM. Experience at a Series A-C company where you had to balance speed with quality. Familiarity with the data integration and pipeline landscape. What Good Looks Like in Year One After 12 months, a great hire will have: Full, unambiguous ownership of their pod's backlog, with a defensible point of view on priorities that's grounded in customer reality and business impact. Identified and closed the most critical gaps in their product area, with improvements that customers and internal teams can actually feel. Built enough technical depth to shape architecture decisions, not observe them. Become the person in the company most connected to what customers actually need from their product area. Made internal teams measurably better at representing the product. Started actively shaping the Intelligence Layer, contributing product thinking and customer insight as Hevo moves into its next chapter. The Moment Hevo spent eight years building both a product and a business simultaneously, and the foundation is real. The Intelligence Layer is early. The window to define what it becomes is open right now. Most people will look at this moment in five years and wish they'd been here for it. If you're one of the people who wants to be here for it, let's talk.