Bajaj Finserv splits by track. Tech needs programming + aptitude; finance tracks need product/lending basics. Read your JD before copying a FAANG plan.
What actually rejects people
Zero finance vocabulary for finance roles, or zero coding for tech roles.
First round: Bajaj Finserv OA (aptitude + tech/finance by role)
Time split that matches how candidates report outcomes (not a marketing pie chart):
Aptitude/logical 35%
Coding/SQL 35%
CS + domain 20%
HR 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA
~90 min
Aptitude + technical or financial knowledge
Domain interview
~45 min
Tech or finance depth
HR
~30 min
Fit
Aptitude & Reasoning (40% time) - Practice quantitative aptitude, logical reasoning, and verbal ability from previous year papers
Technical Skills (30%) - Master programming (Java, Python, SQL), databases, and system design basics
Financial Knowledge (20%) - Understand basic financial concepts, lending systems, and insurance systems
Interview Preparation (10%) - Practice technical and HR interview questions
One timed block that matches Bajaj Finserv’s first round (aptitude/coding OA)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
Aptitude / logical
Timed sectional accuracy
3-4
Coding + SQL
Joins + medium coding comfort
5-6
CS + reliability themes
Explain transactions/controls simply
7-8
Mocks + behavioral
Full assessment mock weekly
Confirm whether your invite is aptitude-heavy or coding-heavy
SQL practice if the JD mentions data/tech analyst/SDE
Coding correctness and SQL joins/indexes for tech roles
Talk about reliability and controls without fake finance jargon
Why Bajaj Finserv, ethics/teamwork examples, relocation
Aptitude timed sets
Track-specific: Java/SQL or EMIs/credit basics
Aptitude or coding per invite pattern
SQL fundamentals
Clean project narration
Risk, controls, correctness language
Java comfort for many India tech centers
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Zero finance vocabulary for finance roles, or zero coding for tech roles - fix this first
Preparing only interviews while failing Bajaj Finserv’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Finance trivia instead of engineering depth for tech roles
HDFC Bank · ICICI Bank · Paytm · Goldman Sachs · JP Morgan · Deutsche Bank
Next step: Run one timed mock this week that matches Bajaj Finserv’s first round (aptitude/coding OA), then build the weeks around your weakest section - not around what is most fun to study.