Capri Global Capital Data Analyst Interview: Questions, Experience & Prep (2026)

Capri Global Capital is a Mumbai-headquartered NBFC focused on MSME lending, affordable housing finance, and two-wheeler loans. Data Analysts here typically work on loan portfolio analytics, collections performance dashboards, credit risk reporting, and branch-level business reviews. The company has 17 open roles across functions as of July 2026 (knok jobradar), signalling an active hiring phase.

Across India, knok jobradar tracked 319 Data Analyst openings as of July 2026. Bangalore leads with 41 open roles, followed by Delhi (22) and Mumbai (19). Salary bands for Data Analysts range from 5-10 LPA at entry level (0-2 years), 10-18 LPA at mid-level (3-5 years), 18-30 LPA at senior level (6-9 years), and 28-45+ LPA for lead roles.

Capri Global's interview process typically includes an HR screening call, a technical round covering SQL and Excel or Python, and a business or managerial discussion. Candidates report that knowing basic NBFC concepts such as DPD, EMI schedules, and portfolio quality metrics makes a strong impression across all rounds.

These questions are drawn from publicly shared interview experiences and Capri Global's Data Analyst job descriptions. Prepare a clear, specific answer for each before your interview.

1. Walk me through how you would build a collections efficiency dashboard for a branch network.
2. How do you handle missing or inconsistent values in a loan portfolio dataset?
3. Explain what DPD (Days Past Due) means and how it is used in portfolio reporting.
4. You have raw disbursement data from multiple branches with different naming conventions. How do you clean and consolidate it?
5. How would you identify early warning signals of credit stress in a borrower segment?
6. Tell me about a time your analysis directly changed a business decision.
7. How do you write or optimise a SQL query running on a large transactional table?
8. What key metrics would you track to measure the health of an MSME loan book?
9. How would you present repayment trend data to a leadership audience that is not technical?
10. Capri Global operates heavily in Tier 2 and Tier 3 cities. How does that shape your data analysis approach?
11. How do you validate a new data source before including it in a production report?
12. If three business teams each send you urgent data requests on the same day, how do you decide what to work on first?

Use the STAR format (Situation, Task, Action, Result) for every behavioural question. Three worked examples below, set in an NBFC context.

---

Q: Tell me about a time your analysis directly changed a business decision.

*Situation:* At my previous role, the collections team treated all overdue accounts with equal priority, regardless of outstanding balance or how long the account had been past due.

*Task:* I was asked to analyse the overdue portfolio and recommend a better way to focus the team's calling effort.

*Action:* I segmented overdue accounts by DPD bucket and outstanding principal, then built a priority matrix in Excel and wrote SQL queries to refresh it each week. While doing this, I spotted a cluster of mid-ticket accounts that had shifted from an early DPD bucket to a later one over the previous two months, suggesting that the standard follow-up approach was not effective for that group.

*Result:* The team restructured their calling schedule based on the matrix. The manager reported improved resolution in the flagged accounts within the following month, and the weekly refresh became a standing operations report.

---

Q: How do you handle missing or inconsistent data in a loan portfolio dataset?

*Situation:* During a branch-level performance project, I received disbursement files from several branches where the customer ID format differed and some EMI fields were blank.

*Task:* My task was to produce a clean, consolidated report for the monthly business review.

*Action:* I documented every inconsistency before touching the data. I standardised customer IDs using a mapping table and, for blank EMI fields, cross-referenced the loan master file to fill values where possible. Where data could not be reconciled, I flagged those rows separately rather than silently dropping them.

*Result:* The final report clearly separated 'confirmed data' from 'pending verification' rows. The business team found it more trustworthy than a report that hid the gaps, and branch teams were asked to correct the source entries going forward.

---

Q: How would you optimise a slow SQL query on a large transactional table?

*Situation:* A daily repayment report at a previous employer ran slowly each morning, delaying the operations team's start-of-day review.

*Task:* I was asked to investigate and fix the query so the report was ready before the team's morning standup.

*Action:* I used EXPLAIN to examine how the database was processing the query. I found a full table scan on a large repayment table and a redundant subquery that ran once per row. I worked with the DBA to add an index on the repayment date column, rewrote the subquery as a CTE, and moved the date filter earlier in the query.

*Result:* The query ran significantly faster after the changes. The operations team could access the report on time, and the same index-and-CTE approach was later applied to two other reports with similar performance problems.

For technical SQL or Python questions: State your approach first ('I would start by...'), walk through the logic step by step, and close by mentioning edge cases or performance considerations. Interviewers want to see structured thinking, not just a correct answer.

For NBFC domain questions (DPD, EMI, collections): Show that you understand the business purpose behind the metric, not just the definition. If asked about DPD, explain what it means for the business when an account moves to a worse DPD bucket, not just what the acronym stands for.

For prioritisation questions: Use a simple three-part framework out loud: urgency (deadline), impact (who is affected and how badly), and effort (how long will it take). Stating the framework before giving your answer signals analytical maturity.

For 'tell me about a time' questions: Always use STAR. Keep the Situation and Task portions brief, two or three sentences each. Spend most of your answer on the Action, because that is where interviewers evaluate your skills. Close with a Result: if you do not have a precise number, a clear qualitative outcome is still credible.

For presentation or stakeholder questions: Capri Global works with branch managers and senior leadership who are not always data experts. Mention that you lead with the business insight rather than the methodology, adapt the level of detail to your audience, and use simple visuals that make the key finding immediately obvious.

Based on the role and publicly shared interview reports, Capri Global Capital interviewers typically look for three things.

Domain awareness. They want to see that you understand the NBFC business, not just generic data skills. Knowing what DPD means, how EMI schedules work, and why portfolio quality matters will set you apart from candidates who only know tools.

Hands-on SQL and Excel skill. Candidates report that technical rounds focus on SQL joins, aggregations, and window functions, alongside Excel pivot tables and basic formulas. Python is a plus at mid-to-senior levels but is not always a strict entry-level requirement.

Clear communication. Because Data Analysts at Capri Global work closely with collections, credit, and operations teams, interviewers want evidence that you can explain findings to non-technical colleagues. Practice talking through your thought process out loud, not just writing or typing the answer.

A focused two-week plan for the Capri Global Capital Data Analyst interview.

Week 1: Build the Foundations

Days 1-2: Revise core SQL (joins, GROUP BY, window functions, subqueries vs CTEs). Practice on a free platform such as HackerRank or Mode Analytics.

Days 3-4: Review Excel pivot tables, VLOOKUP or XLOOKUP, and basic conditional formulas. Build one mock dashboard using a sample loan dataset.

Days 5-7: Study NBFC fundamentals. Learn what DPD means and how standard DPD bucket groupings are used in lending, how an EMI schedule is structured, and the difference between Gross NPA and Net NPA. Capri Global's annual reports and investor presentations are publicly available and give real business context.

Week 2: Practice and Mock Rounds

Days 8-9: Write out STAR answers for all twelve questions listed above. Record yourself answering two or three of them to check pace and clarity.

Days 10-11: Attempt two or three short case studies around portfolio segmentation or collections prioritisation. Use Excel or even paper, no special tools needed.

Days 12-14: Do a full mock interview with a friend or peer, focusing on explaining your reasoning out loud. Review Capri Global's recent news (branch expansion, new product launches) so you can ask informed questions at the close of the interview.

Using generic answers. Saying 'I cleaned the data and built a dashboard' without any NBFC context signals you have not prepared for this company. Tie every answer to lending, collections, or credit wherever possible.

Skipping the business impact. Interviewers at financial services firms care about what changed because of your work. Always close STAR answers with a result. Even a qualitative outcome ('the team used this report every week') is better than trailing off.

Overcomplicating technical answers. Candidates sometimes reach for machine learning when the interviewer only asked for a basic SQL approach. Match the complexity of your answer to what was actually asked.

Not asking any questions. Capri Global is growing its analytics function. Asking about team structure, current tools, or the analytics roadmap shows genuine interest and initiative.

Fumbling on NBFC terminology. If you are unsure what a term means (NPA, FLDG, co-lending), say so and ask for clarification. Guessing incorrectly is a red flag in a data role where accuracy matters.

While you prepare, knok checks 150+ job sites nightly, applies to Data Analyst roles that match your resume, and messages HR on your behalf. That way you stay active in the hiring pipeline even during a focused prep week.