Academic snapshot
Marks: 65% or 6.5 CGPA throughout 10th, 12th, graduation
Degree: B.Tech / B.E. / M.Tech / MBA / MCA
Backlogs: None active on most drives
Year: Final-year and recent grads (within ~2 years)
Bajaj Finserv Placement Papers 2026
Bajaj Finserv is a financial services company in the Bajaj Group offering lending, insurance, and consumer finance products. Based in Pune, its technology teams build digital lending platforms, insurance systems, and payment products for millions of customers.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Bajaj Finserv in 2026?
Bajaj Finserv is not a mass NQT hirer and not a FAANG OA. The printed floor is often 65% throughout. The real cut is a timed mix of aptitude, SQL/coding, and finance vocabulary.
Who this hub is for
- For: Students targeting Software Engineer / Full Stack / Data Engineer or Finance Analyst campus and off-campus loops.
- Not the same track: Experienced product-manager searches, sales-only roles, or insurance-advisor field jobs. Those bars do not map to this OA.
- Engineers: Eligible on most tech drives. You still sit the finance MCQs. Skipping KYC because “I am CSE” is how people fail a 90-minute paper they could have cleared.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, college list, sometimes an API or coding filter named on stage | Aptitude + finance flavour |
| Careers / portals | Resume volume | Still expect an OA |
| Referral | Visibility | You still explain a lending journey |
Off-campus does not mean easier EMI questions. It often means more applicants who treat the finance section as optional.
Degree, 6.5, and “is 6.5 enough?”
Is 6.5 CGPA enough? It matches the commonly reported floor. A 6.6 who finishes the aptitude section and can join two tables beats an 8.8 who blanks on KYC. A 7.5 with 62% in 12th still dies if the JD says throughout.
Branches: All listed engineering branches for tech. MBA/B.Com/quant stories for finance. If the college list is CSE-only, read the notice.
Gaps and backlogs: Active backlogs are a usual blocker. Gaps need an honest skills story.
What helps the resume screen: A project with a metric (latency, accuracy, users), any internship that touched APIs or data, and a one-line interest in lending or payments that is not a brochure. See certifications after OA mocks, not instead of them.
Skills they actually filter
Written: Aptitude + SQL/coding + finance MCQs
Tech interview: DSA lite, OOPs, projects
Finance interview: Cases, products, numbers
Tools: Java or Python; SQL is not optional
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 65% or 6.5 | Mailer wins |
| 10th & 12th | Often same throughout rule | Keep scans |
| Degree type | B.Tech / MBA / MCA listed | Role decides |
| Backlogs | None active | Confirm drive |
| Coding | Java/Python/SQL on tech | Finance still sees aptitude |
Who usually fits and who struggles
Good fit: You can time a 90-minute mixed paper, you will learn EMI without becoming an MBA overnight, and you can live with Pune (or the city on the letter).
Harder path: You only grind LeetCode and skip aptitude; you freeze on “what is KYC”; you quote a 25 LPA product CTC in HR; you treat the finance section as a joke.
Bajaj Finserv placement papers - last few years
Download 2026 Bajaj Finserv placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for aptitude and coding filters
Bajaj Finserv does not publish one permanent official paper set. Papers on this site are pattern trainers for aptitude, SQL, light coding, and finance MCQs.
| Round (typical) | What to practice |
|---|---|
| Written / OA | Quant, logic, verbal, SQL/OOPs, EMI/KYC/insurance |
| Coding filter (some) | One clean problem + optional REST POST |
| Technical / finance | Projects, DSA lite or cases |
| HR | Why fintech, city, integrity |
Themes that keep repeating (2024-2026)
- Classic campus OA: ~90 minutes, ~50-60 items. Aptitude (20-25), technical (15-20), financial knowledge (10-15). Student rumours put written pass around 30-40%. Negative marking usually off on this flavour.
- March 2024 Full Stack on-campus (GFG): Practical filter first: build and host a REST API (POST) that splits an array into odd/even/alphabet, then a 90-minute coding round (greedy + calculator UI), then database-heavy technical and HR.
- Data Engineer intern (GFG): Upload name/email/college via an open API (max 10 tries for a success message). Within two hours, HackerEarth (10 MCQs + 1 coding). ~50-minute technical: projects, egg-dropping, Tower of Hanoi pseudocode, Python reverse, SQL joins via Venn diagrams. Telephonic HR asked relocate willingness.
- 2025 SDE notes: LRU cache, rate limiter, merge intervals, lending-journey talk, Java APIs. Finance MCQs did not disappear on mixed campus papers.
- 2026 prep expectation: Keep the three-section OA warm. Add one hosted POST and one HackerEarth-style coding if your PPT names them. Do not assume a pure CAT paper or a pure LeetCode contest.
How to use one paper set in a single sitting
- Timed: 90 minutes, three sections, no phone.
- Untimed: rewrite the three finance items you guessed (EMI, KYC, insurance).
- Three SQL queries from memory, including one broken join.
- One 25-minute coding problem (second largest, reverse, or interval merge).
- If API was named: a 20-minute POST that returns JSON and logs one error.
Related drills
| Theme | Drill next | Why Bajaj Finserv asks it |
|---|---|---|
| Percentages / EMI | Flat vs reducing-balance MCQ | Lending OA |
| Sets / arrangements | Speed without panic | Aptitude slice |
| SQL joins | Venn-diagram explanation | Data + SDE panels |
| LRU / rate limiter | Talk complexity first | 2025 SDE notes |
| REST POST | Host, call, handle bad input | 2024 full-stack filter |
Bajaj Finserv hiring rounds in 2026
Bajaj Finserv hires through campus cells, careers / portals, and referrals. After eligibility, the shape is fintech: mixed OA, role interview, HR. Extras: REST API task, HackerEarth coding.
Application methods
Campus recruitment
Engineering and MBA campuses. Listen for API/HackerEarth language in the PPT.
Online applications
bajajfinserv.in careers or listed portals. Follow the invite for format.
Referrals
Improve screen odds. OA and SQL still happen.
1. Resume / eligibility screen
65% / 6.5 throughout when printed, listed degree, no active backlogs. Gate.
2. Online Assessment (typically 90 min)
Student-reported working map for the mixed campus paper:
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude | 20-25 | ~30 min | Quant, logic, verbal |
| Technical | 15-20 | ~30 min | Programming, DS, SQL, OOPs |
| Financial knowledge | 10-15 | ~30 min | EMI, KYC, insurance, payments |
Pass habit: skip a stuck puzzle in 90 seconds. Do not leave finance for “if time remains.” Sectional cutoffs show up in student rumours. Your invite wins.
HackerEarth extra (some data/SDE): 10 MCQs + 1 coding. Correctness over a clever partial.
REST API extra (some full-stack): POST, host, return the asked split, handle bad input. Ten tries is not ten chances to redesign the universe.
Sample OA flavour (pattern trainers, not a leaked key)
Simple interest doubles in 5 years. When does it become 4 times (flat SI)?
2P = P + PRT/100 → R = 20%. For 4P: 3P = P×20×T/100 → T = 15 years. OA likes the SI trick. Real loans use reducing balance; say so if an interviewer asks.
50 students, 30 like Maths, 25 Science, 10 both. How many like neither?
Union = 30+25-10 = 45. Neither = 50-45 = 5.
EMI for ₹1,20,000 at 12% p.a. for 1 year (flat approximation many MCQs use)?
Interest ≈ 14,400. Total ≈ 1,34,400. Monthly ≈ ₹11,200. Reducing-balance EMI is different; many OA items test the flat idea first.
KYC in digital lending primarily helps with?
Identity verification and regulatory compliance before disbursal. Not interest-rate maths.
Full aptitude bank: Bajaj Finserv aptitude questions.
3. Technical / finance interview (~45 min, sometimes two tech rounds)
Tech: live coding or SQL, OOPs, project. 2025 notes: LRU (HashMap + list), rate limiter, interval merge, lending journey in plain words.
Finance: case, product, a number you can defend.
Pass habit: clarify constraints, talk while you code, connect the project to payments or data. “I need a week of design” is not a close.
4. HR (~30 min)
Why Bajaj Finserv, why fintech (not “I like money”), city, joining, integrity. Know the ₹8-12 LPA tech band or ₹6-9 LPA finance band. The letter wins.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / screen | 3-5 days | Degree + % check |
| OA (+ API/coding extra) | 1 sitting to a few days | Formats vary |
| Role interview | 2-7 days | Virtual common |
| HR | Same day or next | Short |
| Offer | 3-5 days | Written letter wins |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
Lending-journey habit (the explanation people skip)
Disbursal is not “the app gives a loan.” Say: acquire → KYC → underwrite → sanction → disburse → collect. Name one risk (fake KYC, late EMI, collection call quality). Interviewers want the chain, the same way a Fermi estimate needs assumptions.
Weekend mock
Saturday 10:00: 90-minute three-section paper.
Saturday 12:00: rewrite three finance misses.
Saturday 16:00: one SQL join debug + one coding problem.
Sunday 11:00: 20-minute REST POST if named.
Sunday 12:00: HR why-fintech recorded once.
Two weekends of that beat a dump-PDF binge.
Documents pack
10th, 12th, degree, ID, resume one page. Throughout 65% means the 12th PDF matters.
After an OA mock, the only review that matters
Pick the three items you guessed in finance and the two SQL questions you stalled. Rewrite them. Speak one lending sentence to a wall. Re-reading 40 aptitude answers you already got right is how people feel busy and still fail KYC.
Tech track vs finance track (do not mix the mocks)
If the mailer says Software Engineer / Full Stack / Data, your second interview is code and SQL. Finance MCQs still sit in the OA. If the mailer says Analyst / Finance, your second interview is a case and a product. Aptitude still sits in the OA. Students who prepare the wrong second round are the ones who clear OA and then go silent.
Tech interview, 45 minutes, a working map
- Two minutes: project in one metric (p99, accuracy, users).
- Fifteen minutes: one DSA or SQL problem. Talk constraints first.
- Ten minutes: OOPs or Java/Python language check.
- Ten minutes: lending or payments vocabulary at fresher depth.
- Buffer: “what would you rebuild?”
Finance interview, 45 minutes, a working map
- Clarify the goal (profit, NPA, conversion).
- Split into three drivers.
- One calculation (EMI, margin, or funnel).
- Recommendation + one risk.
- What data you would collect next week.
That beats a memorised 3C dump or a system-design lecture the panel did not ask for.
How interviews get scheduled
Campus: PPT → OA (sometimes same day) → shortlist mail in 2-5 days → virtual or onsite technical → HR. Off-campus: more resume noise, same paper flavour. Screenshot the invite. If the PPT never mentioned an API, do not panic-build a Spring Boot course. If it did, host a boring POST the night before and test it once from a second machine.
Proctoring and sectional habits
Mixed papers often lock sections or at least punish bouncing. Treat each 30-minute block as its own exam. Mark and move. A perfect last finance item does not save an empty aptitude grid. Student rumours about 30-40% OA pass are not a promise; they are a reminder that speed plus not-skipping-finance is the whole game.
Preparation resources for Bajaj Finserv
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for Bajaj Finserv this season
If a Bajaj Finserv invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Bajaj Finserv sits around ₹8-12 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Candidate-reported floor is often 65% or 6.5 CGPA across 10th, 12th, and graduation. Degrees commonly listed: B.Tech/B.E./M.Tech/MBA/MCA. Final-year and recent grads (within ~2 years); no active backlogs. Tech drives take most engineering branches; finance roles want commerce/MBA/quant stories. Verify the notice.
What you are training for: Typical campus tech/finance loop: Online Assessment (~90 min: aptitude + technical + financial knowledge) → Technical or Finance interview (~45 min) → HR (~30 min). Some SDE drives add a second technical or a REST-API / HackerEarth coding filter. About 2-3 weeks on many campus batches.
Short version of the prep split: Split time roughly 40% aptitude, 30% coding/SQL/OOPs (tech) or cases (finance), 20% lending/insurance/payments vocabulary, 10% HR and Why Bajaj Finserv. Full plan: /bajaj-finserv/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Bajaj Finserv previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Bajaj Finserv drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Bajaj Finserv usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Bajaj Finserv?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Bajaj Finserv-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Bajaj Finserv story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Bajaj Finserv PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Bajaj Finserv papers on three different days, then interview prep on the leftovers.
How to train for Bajaj Finserv aptitude and finance MCQs
Week calendars live on the preparation guide. This H2 is the focus split.
Time split
| Bucket | Share | What “done” looks like |
|---|---|---|
| Aptitude | ~40% | Timed 30-minute sets, error log |
| Coding / SQL / OOPs (or cases) | ~30% | One join you can debug; one coding close |
| Finance vocabulary | ~20% | EMI, KYC, insurance in your words |
| HR + city | ~10% | Why Bajaj Finserv without a brochure |
If you are a CSE who only codes, stop LeetCode for one week and sit three mixed papers. If you are an MBA who only cases, add SQL so a data-flavoured panel does not strand you.
This week
- One timed OA mock from aptitude questions.
- Ten finance MCQs written out, not glanced.
- Five SQL queries including one broken join.
- One coding problem talked before typed.
- One 8-sentence lending journey.
What not to waste time on
- Ignoring finance because you are CSE
- Staff-level system design for a 45-minute fresher panel
- Quoting 25 LPA in HR
- Building a payments startup on the resume that you cannot explain
- Treating the REST API filter as optional if the PPT named it
Two-week focus if the drive is soon
Week A: daily 45-minute aptitude; 15 finance items; one SQL sheet.
Week B: one full 90-minute mock every other day; one LRU/rate-limiter talk; HR why-fintech recorded twice.
Engineers: cut contest grinding to maintenance (3 problems/week) until the mixed OA is not a panic. Finance candidates: do not skip the five SQL queries even if the PPT never said “coding.”
How to say “why Bajaj Finserv” without a brochure
You want to build lending or insurance products that real customers use, not a generic “fintech passion.” You will relocate to Pune (or the city on the letter). You know the trainee CTC band and you will read the letter. That is enough. “I have always been passionate about leveraging digital transformation in BFSI” is how people sound like a template.
Finance types worth a week, not a lifetime
You do not need a banking diploma. You need representatives:
- EMI / SI vs CI with one reducing-balance caveat
- KYC / AML as identity, not interest
- Life vs general insurance (death risk vs asset/health)
- Disbursal vs collection in the journey
- NPA as a one-line risk, not a RBI essay
For each type, do five MCQs, then explain one to a roommate in 90 seconds. If you cannot explain it, you do not own it.
SQL debug they actually used
Data Engineer notes mentioned joins via Venn diagrams. Practise the boring failures:
JOINon the wrong key (duplicate rows)LEFT JOINthenWHEREon the right table (turns it into inner)GROUP BYmissing a columnCOUNT(*)vsCOUNT(col)with nulls
Write the wrong query, then the fix, aloud.
Night-before checklist
- Charger, ID, resume that matches any API or bot-style form
- One EMI and one KYC sentence on paper
- Five SQL queries including a broken join
- One coding close if HackerEarth was named
- Sleep. Morning panic on aptitude is how 30-40% pass without you
What fintech hiring means here
Bajaj Finserv is not trying to be TCS and not trying to be Google. The finance MCQ brand is real. The 2025 SDE LRU panel is also real. You can be a CSE graduate or an MBA; both still have to time the paper. You cannot outsource KYC to a dump PDF. You cannot skip joins because a senior said “they only do aptitude.” Read your mailer. Then practise both.
If Bajaj Finserv, HDFC Bank, and Paytm all land the same week, compare how heavy SQL vs aptitude vs DSA felt in recent notes, city, and the letter. Do not pick on brand memory from a 2019 cousin story.
Error log that actually shrinks
Keep a two-column note: speed miss vs concept miss. Speed miss: you knew SI but ran out of time. Fix: skip after 90 seconds. Concept miss: you thought KYC sets the interest rate. Fix: write the definition once. Mixing those two columns is how people redo the same 200 questions and still fail the same 10.
Bajaj Finserv fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026).
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer | ₹8-12 LPA | Primary campus tech band |
| Senior SWE (indicative, 2-3 yrs) | ₹12-18 LPA | Not campus default |
| Finance Analyst | ₹6-9 LPA | MBA / commerce flavour |
| Senior analyst (indicative) | ₹9-14 LPA | Experience |
Confirm the written offer. Variable and joining-bonus language varies.
Benefits students actually care about
Health insurance, PF, learning budget, hybrid on some teams, Pune (and other) city norms. Ask HR about joining location. Do not assume Bangalore product-company hours.
How to talk CTC in HR
Know ₹8-12 LPA tech or ₹6-9 LPA finance. Ask how the package splits. One calm question beats a 20 LPA demand copied from a product-company Telegram group.
Offer-stage discipline
- Read city
- 10th/12th/degree % must match
- OA shortlist is not an offer PDF
Recent Bajaj Finserv placement trends
- Finance MCQs remain on mixed campus OAs. CSE cannot skip them.
- API and HackerEarth filters appeared in 2024 full-stack and data notes; treat a hosted POST and one clean coding problem as real skills when named.
- SDE interviews in 2025 notes look more like backend (LRU, rate limit, Java) than a bank GK quiz.
- ₹8-12 LPA is the commonly cited tech band; confirm the letter.
- Hiring still mixes engineering campuses and some MBA/finance loops.
Net for 2026: do not prepare as if this were TCS NQT or a pure product DSA OA. Time the mixed paper. Keep SQL warm. Learn one lending sentence.
Pune vs other cities (and why the letter wins)
Pune is the story hub. Letters still name other locations. Do not memorise one city. Ask HR. If you cannot go, say so before you celebrate a shortlist. Students who “will decide after the offer” stall joining and annoy the next campus cycle. Decide the city on paper this week. Pune traffic and a plant-adjacent finance ops site are not the same commute. Ask the joining location before you post a celebration story.
Common questions about Bajaj Finserv hiring
Papers & process
Can I download Bajaj Finserv placement papers PDF for free?
What is the Bajaj Finserv placement process for freshers?
Typical path: 90-minute mixed OA → technical or finance interview → HR. Some SDE drives add HackerEarth coding or a REST API filter. About 2-3 weeks on many batches.
How many rounds does Bajaj Finserv usually have?
Most fresher loops report 3 after resume. Some SDE notes list two technicals. Count the mailer.
What is the exam pattern?
Student-reported 90 minutes: aptitude, technical, financial knowledge. Details: online assessment.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly 65% or 6.5 throughout; listed B.Tech/MBA/MCA; no active backlogs. Your notice wins.
What is Bajaj Finserv fresher salary in India?
Candidate-reported tech CTC often ₹8-12 LPA; finance analyst often ₹6-9 LPA (as of August 2026). The written offer is the only number that matters.
Are active backlogs allowed?
Usually no at selection. Cleared backlogs are commonly fine. Confirm the JD.
Prep & Bajaj Finserv-specific
How should I prepare?
Roughly 40% aptitude, 30% SQL/coding or cases, 20% finance vocab, 10% HR. Guide: preparation guide.
Do tech candidates need financial knowledge?
Yes on most mixed OAs. EMI, KYC, insurance at MCQ depth. Not a CFA.
What languages can I use?
Java, Python, C++, C are common. SQL is expected on tech panels. Stick to one coding language.
What is the REST API or HackerEarth filter?
2024 full-stack: host a POST that splits an array. Data intern: open API upload then HackerEarth 10 MCQ + 1 coding. Only if your PPT names it.
Bajaj Finserv vs HDFC Bank vs Paytm?
Bajaj Finserv is NBFC/fintech product with a cited ₹8-12 LPA tech band. HDFC is bank-process plus tech. Paytm is payments product. Compare recent write-ups and letters.
Any pro tip that actually changes outcomes?
Finish finance MCQs. Keep SQL joins warm. Talk a lending journey in plain words. Do not wait for a perfect LeetCode rating.
Where can I read real interview experiences?
Bajaj Finserv interview experience plus the GFG notes in the stories section.
Should engineers skip aptitude and only do DSA?
No. The mixed OA still opens the funnel. DSA can help later. Do both at fresher depth.
What recent candidates reported
Full Stack Engineering, on-campus (GFG, updated 27 Mar 2024)
Unusual opener: candidates “were tasked with building and hosting a REST API (Method: POST)” that returns odd/even/alphabet splits from an array, then a 90-minute coding round (greedy + calculator UI) before database-heavy technical and HR. Source: GeeksforGeeks Bajaj Finserv Full Stack.
Takeaway: if the PPT names an API, host it. Do not treat it as a bonus homework.
Data Engineer intern (GFG)
Upload name/email/college via the company’s open API. “A maximum of 10 chances was given to get a success message.” Within two hours, HackerEarth (10 MCQs + 1 coding). ~50-minute technical: projects, egg-dropping, Tower of Hanoi pseudocode, Python reverse, SQL joins via Venn diagrams; telephonic HR checked relocate willingness. Source: GeeksforGeeks Bajaj Finserv Data Engineer.
Takeaway: ten API tries punish sloppy JSON. SQL Venn talk is not optional for data.
Composite SDE notes (2025)
LRU cache, rate limiter, merge intervals, lending-journey discussion, Java APIs. What helped: talking before coding. What hurt: coding before constraints; treating HR as a formality.
After you clear OA
- Re-work every guessed finance item.
- Five SQL queries including a broken join.
- One coding close talked aloud.
- One 8-sentence lending journey.
- Sleep and city answer. Do not open a new CFA course.
Mini lending close you should be able to run cold
NBFC wants to cut first-month bounce on new personal loans.
- Clarify: bounce = EMI unpaid on due date, which product, which city.
- Buckets: underwrite quality, mandate setup, reminder timing, collection script.
- Estimate: 10,000 new loans, 8% first-month bounce, half of that is mandate/reminder fixable.
- Recommend: one NACH/mandate experiment + one reminder timing test, measured weekly.
- Risk: tighter underwrite that also kills good customers.
That is a trainee-level close. A 12-slide “digital transformation” pastiche is not.
API filter rubric (from the 2024 note)
Read the spec once. Implement the POST. Return exactly the keys they asked. Log invalid input. Host it. Call it from curl or Postman. If you have ten tries, use the first two to confirm hosting, not to rewrite the algorithm. The panel may ask how you handled a non-array body. If you cannot answer, you copied a gist.
More narratives: Bajaj Finserv interview experience.
If you’re also targeting…
HDFC Bank · ICICI Bank · Paytm · Goldman Sachs · JP Morgan · Deutsche Bank