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

CASHe is a Mumbai-based digital lending NBFC that offers instant personal loans to salaried millennials. Its core technology is an AI-driven credit scoring system called the Social Loan Quotient (SLQ), which factors in social and behavioural data alongside traditional financial signals. Product Managers here work at the intersection of consumer credit, mobile UX, regulatory compliance, and data-driven product design, making the role both broad and technically demanding.

As of July 2026, knok's job radar shows 1 open Product Manager role at CASHe. PM salary bands across India, based on knok data, currently look like this:

Candidates typically go through multiple rounds covering product sense, data analysis, and behavioural competencies. The process is reported to be thorough, with strong emphasis on fintech domain knowledge and familiarity with CASHe's specific business model and regulatory context.

These questions come up consistently in CASHe PM interviews, based on what candidates report:

1. CASHe's SLQ model uses social and behavioural signals for credit scoring. How would you improve it to reduce defaults without significantly cutting approval rates?
2. Walk us through how you would define and track success metrics for CASHe's loan disbursement funnel.
3. A new RBI circular caps interest rates on short-term digital loans. How do you adapt CASHe's product and pricing model?
4. CASHe's repayment rates drop noticeably every Q3. How do you diagnose the root cause and what product interventions would you consider?
5. How would you design a feature to increase repeat borrowing among users who repaid their first loan on time?
6. CASHe is evaluating a buy-now-pay-later product for e-commerce. How do you decide whether to build it in-house or partner?
7. A well-funded competitor launches zero-interest loans for first-time users. How does CASHe respond at the product level?
8. You have three roadmap candidates: improving credit limit upgrades, adding a savings product, and reducing KYC drop-off. How do you prioritise?
9. How would you design an A/B test to measure whether a 'loan protection' upsell increases or hurts overall conversion?
10. If CASHe wanted to expand into Tier-2 and Tier-3 cities for the first time, what product and UX changes would you propose?
11. Describe a time you worked with a risk or data science team on a product. How did you manage model-related requirements?
12. CASHe's NPS among first-time borrowers is low. How do you investigate root causes and what would you fix first?

Three STAR-format sample answers. Use these as templates and adapt the specifics to your own experience.

---

Q: How would you reduce defaults on CASHe's SLQ model without significantly lowering approval rates?

*Situation:* At my previous company, our consumer lending product was seeing rising default rates in one borrower segment even though their model scores looked healthy.

*Task:* I was asked to work with the risk team to identify what signals the model was missing and propose product-level interventions.

*Action:* I pulled cohort data and found that defaults clustered among users who had switched jobs in the three months before applying. The model did not capture job tenure recency. I proposed adding an employer verification step at onboarding and worked with the data team to include tenure as a model feature. I also introduced a 'soft limit' tier where borderline users received a smaller first loan with a clear upgrade path after clean repayment.

*Result:* Defaults in that segment came down over two quarters. The soft-limit tier also improved repeat borrowing, adding revenue that offset the tighter approvals on riskier profiles.

---

Q: CASHe's Q3 repayment rates drop every year. How do you diagnose and address this?

*Situation:* At a previous payments product role, we noticed a seasonal spike in payment failures around the same period each year.

*Task:* My job was to identify the driver and recommend a fix before the next cycle.

*Action:* I segmented repayment data by borrower profile, loan tenure, and EMI due date. I found that a large share of defaulters had EMI dates in the first few days of the month, a period when many salaried users had not yet received that month's salary. I cross-referenced this with payroll cycle patterns and confirmed a consistent mismatch. I proposed letting users shift their EMI date to mid-month after salary confirmation, and set up push reminders a few days before the due date showing the exact amount owed.

*Result:* Candidates report that similar interventions on comparable lending products produced meaningful drops in early-month defaults. In our test cohort, the reminder campaign improved on-time payment rates noticeably over the following quarter.

---

Q: You have three roadmap items: credit limit upgrades, a savings product, and reducing KYC drop-off. How do you prioritise?

*Situation:* I faced a very similar call at a fintech startup where engineering bandwidth was tight and three initiatives were competing for sprint capacity.

*Task:* I needed to present a prioritised roadmap to leadership with a clear rationale.

*Action:* I scored each initiative on three dimensions: near-term revenue impact, user retention, and engineering effort. KYC drop-off reduction scored highest because it is a top-of-funnel problem where each improvement directly expands the verified user base at low build cost. Credit limit upgrades ranked second because they drive repeat borrowing from already-verified users, the most valuable cohort for a lending business. The savings product, while strategically interesting, carried high build cost, regulatory complexity, and no clear near-term revenue path, so I pushed it to the next planning cycle.

*Result:* Leadership aligned on the prioritisation. Fixing KYC drop-off unlocked more borrowers from existing marketing spend, improving unit economics of acquisition.

Three frameworks that map well to CASHe PM interview questions:

For metrics and diagnostic questions, use a funnel-segmentation approach. Start by naming the north star metric (disbursements, repayment rate, repeat borrowing). Break it into funnel components: awareness, onboarding, first loan, repayment, repeat borrow. Identify where the gap sits, form a hypothesis, and name the specific data you would pull to validate it. This shows structured thinking rather than jumping to solutions.

For strategy and build-vs-partner questions, frame your answer around four questions: What is the user problem? What is CASHe's moat in solving it (credit data, distribution, NBFC license)? What is the risk of getting it wrong? What is the fastest way to validate the bet? This signals business judgment and an understanding of CASHe's competitive position, not just product instinct.

For prioritisation questions, use a simplified RICE or impact-vs-effort grid. State your scoring dimensions out loud: reach, revenue impact, effort, and strategic fit. Fintech interviewers at companies like CASHe typically want to see you weigh regulatory risk and unit economics alongside user impact, not just engagement metrics. Naming credit risk or compliance as a dimension in your prioritisation will stand out clearly.

CASHe PM interviewers are typically looking for five things:

Fintech and credit literacy. You do not need to be a credit risk expert, but you should know what an NBFC does, why RBI digital lending guidelines shape product decisions, and how a lending funnel differs from an e-commerce one.

Comfort with data and ambiguity. CASHe is a data-heavy business. Interviewers want to see you reach for metrics before opinions. When you do not have data, name the data you would collect rather than guessing.

User empathy for the salaried millennial. CASHe's core user is a young professional who needs quick credit and is often anxious about financial products. Showing that you understand their context, including salary cycles, financial stress, and trust in digital apps, signals strong product thinking.

Risk and growth balance. Every product decision at a lending company carries a credit risk implication. Interviewers want to see you consider both sides, not just optimise for growth.

Execution clarity. Can you take a fuzzy problem, structure it, and describe what you would actually ship in the first sprint? Strong candidates name the specific metric they would move and the specific feature they would build, not just a broad strategy.

A focused two-to-three week plan for the CASHe PM interview:

Week 1: Know the product and domain.
Download and use CASHe's app yourself. Go through onboarding, explore the loan application flow, and note where the UX is smooth or broken. Read up on RBI's digital lending guidelines (publicly available and widely covered in fintech media). Understand what an SLQ-style credit scoring system tries to solve and why alternative data matters for thin-file borrowers.

Week 2: Practice structured problem-solving.
Pick four or five questions from the list above and write out full answers: STAR format for behavioural questions, funnel-segmentation or RICE for analytical ones. Practice saying your answers out loud. Aim to keep each answer under three minutes.

Week 3: Mock interviews and CASHe-specific angles.
Ask a peer to run you through a full mock interview. Focus on answering the 'so what' at each step: so what does that metric tell you, so what would you build, so what would you measure. For every answer, add one CASHe-specific angle referencing their SLQ model, their salaried user segment, or their NBFC regulatory context.

Before each round, check CASHe's LinkedIn page, any recent news, and their app store reviews. Being able to cite specific observations from the product consistently impresses interviewers. While you prep, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf so you do not miss any new CASHe openings.

Treating it like a generic PM interview. CASHe is a credit product company. Candidates who give answers with no reference to credit risk, repayment rates, or regulatory constraints come across as unprepared for the domain.

Using vague metrics. Saying 'I would improve engagement' is not enough. Name the metric (repeat loan rate, KYC completion rate, EMI on-time payment rate) and explain why it is the right proxy for business health.

Skipping the regulatory angle. RBI's digital lending guidelines directly shape what CASHe can and cannot build. Not mentioning this when answering a product strategy question is a visible gap to a fintech interviewer.

Overcomplicating the solution. CASHe is a lean fintech. Interviewers tend to prefer a candidate who can scope a focused MVP and measure it over one who proposes a months-long platform rebuild.

Not asking sharp questions. Candidates who ask pointed questions at the end of each round, about the roadmap, the risk-product team relationship, or how success is measured at CASHe, tend to leave a stronger impression than those who ask nothing or ask about culture in vague terms.