Respo Financial Capital Product Manager Interview: Questions, Experience & Prep (2026)

Respo Financial Capital is a financial services company focused on lending and capital allocation. As of July 2026, the company has 1 open Product Manager role listed on knok jobradar, making this a focused opportunity rather than a mass hiring cycle. PM interviews at lending and NBFC-type firms typically cover product thinking, fintech case studies, and behavioural rounds, though candidates report the exact structure can vary by team and seniority level.

The PM role at a company like this sits at the intersection of borrower experience, credit risk, and regulatory compliance. Interviewers will expect you to understand the loan lifecycle, from application and KYC through to disbursal and repayment, and to show that you can make product decisions within the constraints that financial services brings.

For context, knok jobradar shows 2009 open PM roles across India as of July 2026. Bangalore leads with 271 openings, Delhi follows with 177, and Mumbai has 56. Salary bands, based on industry surveys, run from 12-20 LPA for Associate PMs up to 55-90+ LPA for Group or Principal PMs.

These questions reflect patterns in fintech and financial services PM interviews. Candidates report that lending-focused firms go deep on product metrics, regulatory awareness, and cross-functional trade-offs.

1. Walk us through a financial product you have built or improved end to end. What metrics did you use to measure success?
2. How would you design the onboarding experience for a first-time personal loan applicant? What would your north star metric be?
3. A significant share of users drops off during the KYC or income verification step. How do you diagnose the problem and what would you do?
4. How do you balance speed-to-market with RBI or regulatory compliance when prioritising a new feature?
5. Tell us about a time you pushed back on a request from a senior stakeholder or founder. How did you handle it?
6. How would you prioritise between improving the borrower experience and improving the lender or capital partner experience on the same platform?
7. Design a credit underwriting dashboard for the risk team. What data would you surface, how would you structure it, and what would you leave out?
8. Our repeat borrower NPS is lower than our first-time borrower NPS. How would you investigate and address this gap?
9. How would you reduce loan processing time from application to disbursal? Walk us through your approach step by step.
10. Describe a product decision that turned out to be wrong. What did you learn and what would you do differently?
11. How do you stay current with changes in NBFC regulations and fintech policy, and how do these feed into your product roadmap?
12. If you had to pick one feature to ship this quarter to improve loan repayment rates, what would it be and why?

Q: Walk us through a financial product you built or improved end to end.

*Situation:* At my previous company, our personal loan product had a high drop-off rate at the income verification step, a publicly reported pain point across digital lending apps in India.

*Task:* I was given ownership of the KYC and income verification flow with a clear goal to improve completion rates and reduce inbound support volume.

*Action:* I started with user interviews and session recordings to map exactly where and why users were stopping. I identified three friction points: confusion about which documents were acceptable, anxiety around sharing bank credentials, and a slow manual review loop. I worked with engineering to integrate an account aggregator API for bank statement fetch, added plain-language tooltips explaining each step, and built a fallback manual upload path with a clear document checklist. I also set up a weekly funnel review with the data team to catch regressions early.

*Result:* After launch in 2025, completion at that step improved noticeably, support tickets related to income verification dropped, and the project became a template for improving other steps in the same flow.

---

Q: Tell us about a time you pushed back on a senior stakeholder.

*Situation:* A senior leader wanted to fast-track a new loan feature ahead of a quarterly deadline by skipping the standard compliance review process.

*Task:* As the PM, I was responsible for both delivery speed and making sure we did not create regulatory exposure for the company.

*Action:* I requested a direct conversation and came prepared with a short document outlining the specific regulatory clauses that applied, the risk of a non-compliant launch, and a revised timeline that cut the delay to two weeks by running the compliance review in parallel with engineering work. I framed it as 'how do we get there safely and quickly' rather than a flat refusal.

*Result:* The stakeholder agreed to the revised plan. The feature shipped on the adjusted timeline with full compliance sign-off, and the parallel review approach I introduced was later adopted as standard practice by the team.

---

Q: Describe a product decision that turned out to be wrong.

*Situation:* At a previous lending platform, I pushed to add a loan top-up prompt immediately after a borrower made their first EMI payment, expecting it to drive upsell.

*Task:* I owned the feature from ideation through launch, including defining the success metrics and rollout criteria.

*Action:* I ran a quick test with a limited cohort, saw an initial uptick in top-up applications, and recommended a full rollout based on that early signal alone.

*Result:* Within two months, borrowers who received the early top-up prompt showed higher default rates in later EMIs, a pattern consistent with publicly reported findings on aggressive upsell in consumer lending. The feature was rolled back. My key takeaway: in lending, short-term conversion metrics do not always align with long-term borrower health. I should have required a commonly cited 30-day repayment behaviour gate before showing any upsell offer.

The Borrower Lifecycle Lens
For product design or improvement questions, structure your answer around the borrower journey: awareness, application, verification, approval, disbursal, repayment, and renewal. Show which stage has the most friction and why you are prioritising it over others.

Metrics Hierarchy for Fintech PMs
Lead with your north star metric (such as loan completion rate or on-time repayment rate), then your input metrics, then your guardrail metrics (fraud rate, compliance flags, early default rate). Interviewers at financial services companies want to see that you do not optimise conversion at the cost of risk.

Prioritisation with Impact, Effort, and Risk
For roadmap questions, structure your answer as: what is the problem, who does it affect, what is the estimated impact, what is the effort, and what is the risk. At Respo Financial Capital, 'risk' includes both product risk and regulatory risk, so name both explicitly rather than treating them as one category.

The 'Why Now' Test for Regulatory Questions
When discussing compliance or policy changes, use a simple three-part structure: what changed (the regulation or guideline), why it matters to the product (borrower or lender impact), and what you would prioritise on the roadmap as a result.

Financial services PMs are expected to be commercially grounded, not just product-fluent. Interviewers at lending companies typically look for four qualities.

Domain depth. You do not need an NBFC background, but you should understand how credit decisions are made, what drives repayment behaviour, and why compliance is non-negotiable. Candidates who can speak naturally about underwriting logic or KYC requirements stand out immediately.

Data fluency. Be ready to discuss funnels, cohort analysis, and A/B testing in concrete terms. Interviewers want to hear how you have used data to make a product call, including times the data surprised you or changed your direction entirely.

Cross-functional range. Lending PMs work closely with risk, compliance, and finance teams in addition to engineering and design. Show that you know how to move work forward across these functions without cutting corners on the ones that carry the most regulatory weight.

Ownership and honesty. Candidates report that interviewers at smaller financial firms pay close attention to whether you take genuine ownership of mistakes or deflect blame onto others. The STAR format works especially well here because it forces you to be specific about what you personally did and what actually happened.

Week 1: Build domain fluency.
Read up on how NBFCs operate, what account aggregators do, and how digital KYC works in India. Familiarise yourself with publicly reported coverage of RBI digital lending guidelines from 2024-2026. You do not need to become a compliance expert, but you should be able to discuss these topics without needing prompts from the interviewer.

Week 2: Practice product cases.
Pick two or three questions from the list above and write out full answers using the STAR format. Focus especially on the metrics and trade-offs sections. Ask a peer to role-play as the interviewer and push back on your answers, particularly on how you would measure success and what signal would cause you to roll back a feature.

Week 3: Research Respo Financial Capital.
Look at any publicly available product, app, or news coverage from the company. Think about one or two genuine questions you would ask at the end of the interview. Candidates report that showing specific curiosity about the company's target borrower segment or current product priorities is well received by interviewers.

The day before.
Review your STAR stories. Make sure you are not relying on specific numbers you cannot substantiate. Prepare a concise two-minute 'tell me about yourself' that connects your background directly to financial product management.

Knok checks 150+ job sites nightly, applies to roles matching your resume, and messages HR on your behalf, so you can focus your prep time on substance rather than tracking job boards manually.

Treating it like a consumer product interview.
Lending PMs deal with regulatory constraints, risk teams, and capital partners. If all your answers focus on 'delighting the user' without mentioning compliance or risk, interviewers will question your fit for a financial services context.

Describing what you built without explaining how you knew it worked.
Candidates often walk through features in detail but cannot answer 'what was your success metric?' or 'what would have caused you to roll this back?' Be ready with both the signal for success and the signal for failure for every product you discuss.

Claiming specific numbers you cannot substantiate.
If you mention that conversion improved by a particular figure, be ready to explain the sample size, the time period, and any confounding factors. Vague or inflated metrics hurt credibility in a data-aware financial services environment.

Not asking questions at the end of the interview.
Candidates report that interviewers at smaller firms appreciate genuine curiosity. Asking about the biggest product challenge the team is currently working on, or how the PM function works with the risk team, shows you are already thinking like a member of the organisation.

Framing compliance as a blocker rather than a design constraint.
The strongest candidates treat regulatory requirements as inputs to the design process, not obstacles to route around. Show that you can find creative solutions within guardrails rather than looking for ways to skip them.