What is the Bajaj Finserv interview process for freshers?

Bajaj Finserv's campus process is unusual: multiple independent write-ups describe Round 1 as a build task, not a DSA test - candidates get an API spec and actually build/hit an endpoint over 2-3 hours, in a language of their choice, and are sometimes streamed into a technology track based on that language. Round 2 is a more conventional coding/MCQ test, followed by an HR/Culture round on motivation, integrity, and relocation. Timeline is usually 2-4 weeks from application to offer for campus drives.

What questions are asked in Bajaj Finserv interviews?

Bajaj Finserv interviews commonly cover DSA or aptitude screening, core CS (OOPs, SQL), project discussion, and domain topics such as lending journeys, SQL, Java. Behavioural rounds check ownership, teamwork, and why Bajaj Finserv.

How many rounds are there in the Bajaj Finserv interview?

Bajaj Finserv typically has 4 stages: Online Assessment (90 min), Technical Round 1 (45-60 min), Technical Round 2 (45-60 min), HR / Culture (20-30 min). Some drives skip a round or merge HR with managerial. Check that cycle's college placement email.

How should I prepare for Bajaj Finserv interviews?

For Bajaj Finserv, practise timed DSA or aptitude mocks, revise OOPs and SQL, prepare one crisp project narrative, and read up on lending journeys and SQL. Use STAR for behavioural answers.

Bajaj Finserv Interview Experiences

How Bajaj Finserv fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

For fresher tech roles, Bajaj Finserv’s Round 1 is commonly reported as an API build task (2-3 hours, language of your choice) rather than a DSA test, followed by a more conventional coding/MCQ round and an HR/Culture round. Campus and off-campus patterns differ slightly, trust the drive college placement email over older PDFs.

Fresher package ballpark (from student reports): ₹8-12 LPA. Confirm on your offer letter.

Round-wise process

Round	Duration	What they test
Round 1: API build task	2-3 hours	Build/hit an API endpoint in a language of your choice; can determine your tech track
Round 2: Coding/MCQ test	45-90 min	Conventional DSA/technical MCQs
HR / Culture	20-30 min	Motivation, integrity, relocation

Real interview experiences

Bajaj Finserv’s campus process is unusual and worth knowing before you prep: multiple independent student write-ups describe the first round as a build task, not a DSA test - you are given an API specification and asked to actually hit or build an endpoint, in a language of your choice, over two to three hours. Only after that do you get a conventional coding/MCQ test, and in some cycles you are streamed into a technology track based on the language you used in round one.

Documented on-campus drive: Backend (Node.js) track

A student who went through the on-campus drive for a Backend - Node.js role reported:

Round 1 (online, ~3 hours) - build an API using a backend framework, with JavaScript, Python, or Java as the preferred stack. Other accounts of the same round describe being given an API to which you submit your own details (name, email, college) via a PUT request.

Round 2 (online, ~1 hour, HackerRank) - 17 Node.js questions plus one medium-hard programming question, and this round was restricted to Node.js only.

Round 3 (technical interview, ~1 hour, face to face)

Self-introduction and a walkthrough of projects.
AJAX methods, and writing Node.js code for MongoDB queries.
Why Node.js is single-threaded and how it handles concurrency.
What I/O means, and the drawback of Node.js (the expected answer being that it is unsuited to heavy computational work).

HR round (~15 minutes) - hobbies, family, willingness to relocate to Pune, and confirmation of a Monday-Saturday working week with a Pune office start date.

Outcome: offered an internship plus PPO, with results announced the same day.

Documented on-campus drive: Microservices-Java track

A second student (VIT Vellore, electronics background who moved into IT) reported a similar shape with different streaming:

Round 1 (~2 hours): an API-based coding challenge, any language allowed.
Round 2 (~1.5 hours): candidates were classified by the language they used in round one - this candidate landed in the Microservices-Java track. The round itself was an aptitude test plus two easy coding questions. Roughly 600 students cleared it.
Round 3 (technical interview): background and resume projects, then PUT vs POST, Java fundamentals, threading, SQL basics, a database project, method overriding vs overloading, collections, and OOP concepts. Around 250 advanced, including this candidate.
Round 4 (HR, telephonic): essentially a confirmation call about the Pune location and compensation. Everyone who cleared the technical round received an offer.

What this means for prep: the reported fresher process has no system design round and very little algorithmic depth - the filtering happens on whether you can actually build and explain a working API, and then on language/framework fundamentals (Node.js event loop and concurrency, or Java threading and collections) plus SQL. Know your chosen stack properly rather than grinding hard DSA, be ready for Pune relocation to come up in HR, and expect fast turnarounds - both accounts report same-day or near-same-day results.

Sources:

Bajaj Finserv Interview Experience for Backend Developer (On-Campus) - GeeksforGeeks (student write-up, offer)
Bajaj Finserv Interview Experience for Software Developer, On-Campus - GeeksforGeeks (student write-up, offer)
Bajaj Finserv Interview Experience (On-Campus) 2023 - GeeksforGeeks (student write-up)
Bajaj Finserv Interview Experience for Internship - GeeksforGeeks (student write-up)

Round structure varies by role and hiring cycle - Data Engineering and Full Stack tracks report different section mixes. Trust your drive’s placement email over any older summary.

Questions that come up often

Coding / technical

Design an LRU cache. Usually expects HashMap + doubly linked list
Implement a rate limiter. Usually expects sliding window / token bucket
Merge overlapping time intervals. Usually expects sort + sweep
Discussion on lending journeys and SQL, bottlenecks, failure modes, simple APIs
Detailed project discussion, architecture, hardest bug, what you would change

HR / behavioural

Why fintech / payments?
A production bug or outage you helped with
An integrity / pressure scenario
Joining timeline

Practical tips for Bajaj Finserv

Clear the screening round first. Timed practice beats last-minute topic hopping.
For domain questions, explain lending journeys in plain language, inputs, outputs, what breaks at scale.
OOPs and SQL still open a lot of Bajaj Finserv panels. Do not skip fundamentals.
HR answers should be concrete. One story with a result beats five slogans.
If you do not know something, say so and outline how you would find out.

HR interview

After technical rounds, Bajaj Finserv usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions

Common Bajaj Finserv HR questions, sample answer frames, and STAR tips.

Similar companies

HDFC Bank · ICICI Bank · Paytm · Goldman Sachs · JP Morgan · Deutsche Bank