ketto Product Manager Interview: Questions, Experience & Prep (2026)

Ketto is one of India's largest crowdfunding platforms, connecting millions of donors with people raising funds for medical emergencies, social causes, and personal milestones. The platform operates as a two-sided marketplace (donors and campaign creators), which makes PM roles here genuinely challenging and meaningful.

As of mid-2026, Ketto has 16 open Product Manager roles, reflecting active team growth. The interview process typically spans 3-4 rounds. Candidates report a brief HR or hiring manager screen, a product case study (take-home or live), and a behavioral round with a senior PM or engineering leader. Some candidates also report a final round with business or founding team leadership.

Ketto PMs are expected to blend strong product instincts with sensitivity to the emotional and social context of fundraising. Interviewers typically look for candidates who understand donor psychology, can think carefully about trust and safety, and can balance creator-side and donor-side needs at the same time.

Salary bands across PM levels (LPA, indicative):

Ketto interview questions cluster around three themes: donor experience, campaign creator tools, and trust and safety. Candidates report the following types of questions coming up frequently.

1. How would you improve the campaign discovery experience for a first-time donor on Ketto?
2. A campaign creator says donations have stalled. How would you diagnose and fix this?
3. How would you design a feature to detect and reduce fraudulent campaigns on the platform?
4. Ketto wants to improve repeat donor rates. What metrics would you track, and what experiments would you prioritize?
5. How would you decide between improving the mobile app for donors versus building better tools for campaign creators?
6. Design a feature that helps donors find campaigns matching their personal values and giving history.
7. How would you measure the success of a recurring or systematic donation feature?
8. Walk us through a product you shipped end to end. What went wrong, and what did you learn?
9. How would you grow Ketto's corporate CSR partnerships as a product initiative?
10. Ketto is considering entering a new cause category. How would you decide which one to prioritize?
11. How would you reduce drop-off in the donation checkout flow?
12. Tell me about a time you made a product call with very limited data. What was the outcome?

These are illustrative STAR-format answers. Adapt them to your own experience.

Q: A campaign creator says donations have stalled. How would you diagnose and fix this?

*Situation:* In a previous role at a marketplace product, a seller cohort reported a sudden drop in transactions despite steady traffic to their listings.

*Task:* I needed to identify whether the problem was in traffic, trust, pricing, or conversion, and then propose a targeted fix.

*Action:* I pulled a funnel from listing view through to transaction complete, segmented by campaign age, cause category, and creator verification status. I found that unverified campaigns had a materially lower conversion rate than verified ones, and that the share button on mobile was buried below the fold. I proposed two changes: a prominent verification badge with a tooltip explaining what it means, and moving the share button above the donation call to action on mobile.

*Result:* After a short A/B test, the verification badge change improved donor conversion for new campaigns by a meaningful margin. The share button change also increased organic shares per campaign, based on internal data.

---

Q: Tell me about a time you made a product call with very limited data.

*Situation:* At a consumer startup, we had anecdotal feedback from a handful of large donors that they wanted a private giving option, but no survey data to confirm broader demand.

*Task:* Decide whether to build an 'anonymous donation' feature in the next sprint or deprioritize it.

*Action:* I ran a short in-app survey to a sample of active donors over a few days. A majority in this small sample said they would donate more if they could stay anonymous. I also checked a competitor's public changelog and saw they had shipped a similar feature. I made the call to build a lightweight version: a single checkbox at checkout, with no donor name shown on the campaign page.

*Result:* Within a month, a meaningful share of donations used the anonymous option, and average donation value from anonymous donors was higher than the platform average, based on our internal cohort data.

---

Q: How would you design a trust and verification feature to reduce fraudulent campaigns?

*Situation:* A crowdfunding platform I consulted for saw a spike in user complaints about campaigns that did not deliver on their stated purpose.

*Task:* Design a scalable verification layer that protects donors without adding excessive friction for legitimate creators.

*Action:* I mapped the problem into three stages: pre-launch verification (ID check, document upload), in-campaign signals (withdrawal pattern anomalies, social proof indicators), and post-campaign accountability (a fund utilization report). I proposed a tiered trust badge system where campaigns with full document verification and a linked hospital or NGO got a 'Verified' badge, and campaigns with only ID verification got a 'Basic' badge. I worked with the ops team to define a service level for document review turnaround.

*Result:* The tiered system reduced reported fraud complaints, gave donors a clearer signal before donating, and helped the ops team prioritize their review queue more effectively.

A few frameworks that candidates report finding useful in Ketto PM interviews.

CIRCLES (for product design questions): Comprehend the situation, Identify the user, Report the needs, Cut through prioritization, List solutions, Evaluate trade-offs, Summarize. This works well for questions like 'design a discovery feature for donors.' Always include both donor and creator perspectives when applying it.

North Star plus Input Metrics (for metrics questions): Start by naming one north star (for Ketto, this could be total verified funds disbursed or repeat donor rate within a cohort), then list 3-4 input metrics that drive it. Interviewers at Ketto typically appreciate candidates who choose mission-aligned metrics over vanity engagement numbers.

Jobs To Be Done (for user empathy questions): Frame the donor's job as not just 'giving money' but 'feeling certain my money reaches the right person quickly.' Frame the creator's job as 'raising enough funds before the emergency gets worse.' This framing tends to impress interviewers who prioritize social context.

RICE for prioritization: When asked to prioritize features, score by Reach, Impact, Confidence, and Effort. For Ketto, make a point of weighting trust and safety features higher in your reasoning, since platform credibility is a core product asset.

Ketto PM interviewers typically look for a combination of product rigour and social awareness. Based on what candidates report, here is what matters most.

Mission alignment grounded in metrics. Interviewers want you to care about social impact, but they also want you to ground it in numbers. Saying 'I want to help people' is too vague. Show how you would measure impact: fund disbursement rate, beneficiary-reported outcomes, donor trust scores.

Two-sided thinking. Ketto serves both donors and campaign creators. Candidates who default to only one side in their answers tend to score lower. Always name both user types and acknowledge the trade-offs between their needs.

Trust as a first-class concern. Ketto's entire value proposition depends on donors believing the platform is safe and legitimate. Interviewers pay close attention to whether you raise fraud, verification, or credibility concerns without being prompted. If you skip this, they typically probe.

Comfort with emotional product decisions. Unlike a SaaS tool, Ketto deals with grief, urgency, and hope. Strong candidates show they can design for emotional context without being manipulative.

Execution mindset for a lean team. Ketto is not a large tech company with unlimited engineering resources. Interviewers want PMs who can ship fast, decide with imperfect data, and collaborate closely with engineers and operations teams.

A practical two-week prep plan for Ketto PM interviews.

Week 1: Know the product deeply.
Go through the full donor flow on both mobile and desktop. Create a free account, browse campaigns, and ideally make a small donation. Note every friction point, every trust signal, and every moment you felt unsure. Read any publicly available blog posts or campaign outcome stories on the platform.

Build your story bank.
Prepare 4-5 STAR stories from your own work. Cover: a product you shipped end to end, a prioritization decision you made, a time data changed your mind, a time you managed stakeholder conflict, and a product failure with a clear lesson learned.

Week 2: Practice case frameworks out loud.
Practice answering at least three of the questions from the list above out loud, timed. Aim for structured 5-7 minute answers for case questions. Practice with a peer if possible, not just in your head.

Know the hiring context.
Ketto currently has 16 open PM roles, which signals active growth. Be ready to discuss what that stage means for a PM: more ambiguity, broader ownership, and faster iteration cycles.

Prepare smart questions for your interviewers.
Ask about the PM-to-engineer ratio, how product and ops collaborate on trust decisions, and what success looks like in your first few months. These questions signal that you think beyond just getting through the interview.

Candidates who have interviewed at Ketto share a few recurring mistakes to avoid.

Treating it like a pure tech product interview. Ketto is not a SaaS or enterprise tool. Answers that ignore the emotional and social context of fundraising tend to fall flat. Always bring the human story into your product thinking.

Ignoring the creator side. Many candidates focus entirely on the donor experience. Ketto's business depends equally on campaign creators. If a question is about donors, still acknowledge how your solution affects creators.

Vague metrics. 'I would track engagement' is weak. Name specifics: donation conversion rate, repeat donor rate, average donation value, campaign share rate, fund disbursement time.

Over-engineering solutions. Candidates who propose massive multi-quarter roadmaps for a case question often lose points. Show you can ship a simple version first and iterate based on data.

Skipping clarifying questions. In case rounds, interviewers typically want you to ask 2-3 scoping questions before answering. Jumping straight into your solution signals poor problem-scoping habits.

Not mentioning trust or safety proactively. Most candidates address trust only when explicitly asked. Candidates who raise fraud or verification concerns without prompting tend to stand out in Ketto interviews.