Product Lead

Requirements

Product Lead - Purpose & Role Description

What'd you be responsible for:

• Conducting user research and driving product discovery, with a goal of validating at least 3 user problems per quarter that eventually lead to successful product outcomes
• Launching and managing product or feature rollouts, ensuring that at least 80% of these achieve their intended usage and adoption metrics
• Coordinating with the tech and domain teams for execution, with the aim of delivering 90% or more of all projects within agreed timelines
• Enhancing internal team workflows through product solutions, targeting a 30% or greater improvement in time or effort saved across at least two core workflows per quarter
• Owning user satisfaction with product tools, as measured by stakeholder surveys and interviews, with an expectation of achieving high feedback scores.
  

Some of your Monthly Outcomes for the first 3 months in this role:

Month 1

• Build deep understanding of Kraftshala's products and user segments
• Conduct user interviews and internal stakeholder discussions
• Review existing product backlog and identify early wins
• Identify and validate at least 2 high-potential product opportunities
• Establish alignment with tech lead and set up rituals
• Ship 1 small feature or integration
  

Month 2

• Own sprint planning with the tech team
• Drive discovery and solution design for 1-2 validated problem areas
• Coordinate the rollout of a new internal tool or workflow upgrade
• Maintain >90% project delivery alignment with engineering timelines
  

Month 3+

• Consistently deliver 2-3 high-impact product releases per quarter that solve validated problems and drive adoption
• Establish a structured, problem-first product roadmap prioritizing outcomes over features
• Become the go-to problem solver for internal teams and student-facing experiences by combining product thinking with business empathy
  

Top Grading:

• Problem Solving: An A-player proactively identifies problems that others miss and crafts simple, creative solutions. A B-player tends to wait for direction or defaults to the most obvious fixes without deeper investigation
• Execution: An A-player drives execution across functions and consistently ships on time. In contrast, a B-player often struggles with delays, unclear specifications, and scope creep that impact delivery
• Collaboration: A-players anticipate stakeholder needs and communicate transparently throughout the product lifecycle. B-players, however, tend to wait for others to surface blockers and often face challenges aligning teams
• User Obsession: A-player product managers seek direct feedback from users regularly and iterate quickly based on that input. A B-player prioritizes tasks without proper user validation or incorporating structured feedback loops
• Metrics Focus: A-players define clear success metrics before launch and rigorously review impact afterward. B-players ship without setting measurable goals and rarely conduct post-launch analysis
• Technical Fluency: A-players work deeply with engineers, leveraging automation or AI tools like GPTs wherever useful. B-players may struggle to understand technical trade-offs or engage meaningfully in implementation conversations.
  

Must Haves:

• 3 - 4 years of hands-on product management experience (We're not fussed about the exact years of experience, as that's just a proxy for your skill level.)
• Comfort working with engineers, designers, APIs, and no-code tools
• Familiarity with Agile development
• Willingness to learn quickly, adapt to new domains, and continuously improve both the product and yourself.
  

Good-to-haves:

• Experience building or customizing GPTs, AI bots, or using LLMs to streamline processes