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

Sahi is an Indian fintech company focused on digital credit and lending for underserved borrowers. As of mid-2026, Sahi has 3 open Product Manager roles, which points to active team growth. Candidates typically report going through multiple interview rounds covering product design thinking, analytical ability, and cultural fit. Because Sahi operates in the regulated lending space, interviewers pay close attention to how well you understand compliance constraints and user empathy for first-time credit users.

The broader PM market had 2,009 active roles as of July 2026. Top hiring cities were Bangalore (271 roles), Delhi (177), and Mumbai (56). PM compensation in India ranges from 12-20 LPA at the Associate level up to 55-90+ LPA for Group or Principal PM positions. Competition for fintech PM seats at growth-stage startups is real, so preparation needs to go beyond generic PM interview content.

1. How would you redesign the loan application flow to reduce drop-off for first-time borrowers on a low-end Android device?

1. Walk us through a product decision you made using data. What did the data show and what did you decide?

1. A key metric in the loan repayment funnel drops sharply week-over-week. How do you investigate the root cause?

1. How do you prioritise between a feature that increases loan approvals and one that reduces defaults, when engineering bandwidth is limited?

1. Tell us about a product you shipped that did not perform as expected. What did you do next?

1. How would you measure whether a new EMI reminder feature is actually working?

1. How have you worked with compliance or legal teams when building a product that touches user data or financial transactions?

1. Describe a situation where you had to convince a senior stakeholder to change direction on a roadmap item.

1. How would you design an in-app credit health dashboard for a borrower who has never used a credit card?

1. If Sahi wanted to expand into a new borrower segment, such as gig workers, how would you validate that opportunity before building anything?

1. What would your first 90 days look like as a PM at Sahi?

Q: Tell us about a product you shipped that did not perform as expected.

*Situation:* At my previous company, we launched a push notification feature to nudge users to complete their KYC after starting a loan application. We expected strong completion rates, consistent with what industry surveys commonly cite for similar notification campaigns.

*Task:* I was the PM responsible for the feature from spec through post-launch review. When numbers came in flat after two weeks, I owned the investigation.

*Action:* I pulled the funnel data and found that most users who tapped the notification were dropping at the document upload step, not before it. I spoke with a small sample of users and found the camera permission prompt was confusing them. I worked with engineering to simplify the permission copy and added a one-screen explainer before the upload step. We shipped the fix in the next sprint.

*Result:* KYC completion improved in the following two weeks. More importantly, I made testing the full journey on a low-end device a standard step before every future feature launch.

Q: How have you worked with compliance or legal teams when building a fintech product?

*Situation:* We were building a feature that showed a personalised credit limit to users before they completed their application. Legal flagged it as potentially misleading if the displayed amount differed from the final approved amount.

*Task:* My job was to find a solution that kept the feature commercially valuable while satisfying the compliance requirement.

*Action:* I set up a working session with legal, design, and the head of credit risk. Instead of defending the original design, I asked them to define exactly what language would make them comfortable. We agreed on showing a range rather than a single number, with a clear note that final approval was subject to verification. I wrote the spec with their exact approved copy so there was no back-and-forth during review.

*Result:* The feature launched on schedule. The process we used became a template for future compliance reviews, cutting the delays our team had typically seen on earlier projects.

Q: Describe a situation where you had to convince a senior stakeholder to change direction.

*Situation:* The VP of Growth wanted to run an aggressive re-engagement campaign targeting lapsed borrowers with pre-approved loan offers. I had data suggesting a portion of those users had missed payments due to income shocks, not disengagement.

*Task:* I needed to make the case that a blanket push could hurt both users and the loan portfolio, without appearing to block a business priority.

*Action:* I prepared a one-page analysis splitting lapsed users into two segments based on repayment history. One segment (users with a clean history who had gone quiet) was a strong target. The second segment (users who had previously defaulted) would likely produce higher delinquency if re-activated with pre-approval messaging. I proposed a modified campaign targeting only the first segment, with a different message for the second.

*Result:* The VP approved the segmented approach. The campaign ran on schedule, and the default rate on re-activated users came in below our overall portfolio average, which I shared in the following month's review.

For product design questions, start by clarifying the goal (is this about growth, retention, or reducing drop-off?), identify the user (who is the borrower, what device are they on, what is their financial literacy level?), list the key pain points, propose two to three solutions, and recommend one with a clear reason. Avoid jumping to a solution before you have framed the problem.

For metric drop questions, use a top-down breakdown: start at the headline metric, split it into components (volume and conversion rate, for example), find which branch fell, then look at internal causes (a product change, a bug, a recent campaign) versus external causes (seasonality, competitor action, a macro event). Always ask whether anything changed in the product or environment around the time of the drop before diving deeper.

For prioritisation questions, use a simple impact-effort or RICE-style reasoning out loud. State your assumptions, rank the options, and explain the trade-offs clearly. At a startup like Sahi, also factor in regulatory risk and user trust, which standard prioritisation templates often leave out.

For stakeholder influence questions, follow STAR but make sure the 'Action' step shows that you first sought to understand the other person's concern before presenting your counter-view. Interviewers at growth-stage companies want evidence that you can bring people along, not just win an argument.

Sahi interviewers, based on what candidates typically report, look for a few specific qualities beyond standard PM skills.

Fintech context awareness is table stakes. Know how digital lending works in practice: KYC, credit bureau checks, disbursement, EMI collection, and default management. You do not need to be a credit risk expert, but these terms should not be new to you on the day of the interview.

Empathy for the Bharat user carries real weight. Sahi's borrower base commonly includes first-time credit users in Tier 2 and Tier 3 cities, using mid-range or entry-level Android phones. Interviewers notice when a candidate designs solutions that assume a high-literacy, urban, premium-device user without questioning that assumption.

Data fluency without data paralysis. Talk about metrics, funnels, and experimentation confidently, but show that you can also make a call when data is incomplete or ambiguous. Defaulting to 'I would run an A/B test' for every scenario reads as hesitation rather than rigour.

Speed with responsibility. Fintech moves fast but operates in a regulated space. Interviewers want to see that you take compliance seriously without treating every constraint as a blocker.

Week 1: Domain and product context

Start by experiencing Sahi's product directly. Download the app, go through the onboarding and loan application flow as far as you can without actually applying, and note every point of friction. Read up on the digital lending space in India, including RBI guidelines on digital lending, and understand how credit-line products differ from traditional personal loans.

Days 4-5: Metrics and analytical prep

Practise walking through a funnel metric drop from first principles. Pick a fintech funnel (application, KYC, credit check, disbursal, repayment) and break it down out loud until the reasoning feels fluent. Build your own structure for metric-drop questions so you are not improvising on the day.

Days 6-7: Behavioural prep

Prepare four to five STAR stories from your own experience. Cover at least: a product that underperformed, a time you used data to change a decision, a time you navigated a compliance or legal concern, and a time you influenced a senior stakeholder. Write each story in bullet form and practise saying it out loud, aiming for two to three minutes per story.

Final days: Mock and sharpen

Do at least one mock interview with someone who can give honest feedback, or record yourself and review it. Also revisit salary benchmarks so you walk into any compensation conversation informed: PM roles in India range from 12-20 LPA at the Associate level to 40-60 LPA for Senior PM roles, based on the knok jobradar dataset.

If you are applying to other roles in parallel, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf, so you do not miss new fintech PM openings while you are focused on prep.

Treating it like a generic PM interview. Sahi is a fintech company with a specific user base and regulatory environment. Candidates who bring only e-commerce or SaaS examples without connecting them to credit or payments context tend to struggle. Practise translating your past experience into fintech analogies before you walk in.

Ignoring the low-end Android user. Many candidates design solutions that assume strong connectivity, a large screen, or high financial literacy. In a product discussion for Sahi, always ask about the target user's device and internet reliability before proposing a solution.

Over-relying on data to avoid a decision. 'I would run an A/B test' is a valid answer to some scenarios, but saying it to every question reads as decision-avoidance. Show that you can make a reasoned call even when data is incomplete or the timeline does not allow a full experiment.

Not knowing what Sahi actually does. Some candidates describe Sahi's product incorrectly or confuse it with another brand. Spend time on the app and their public-facing content before the interview so your examples feel grounded.

Vague STAR results. The most common issue is ending a story with 'the stakeholder was happy' or 'the feature launched.' Practise closing every story with a concrete, honest outcome. Partial wins with clear learnings are perfectly acceptable to share.