
Synthesized from 8 candidate submissions for ALL.
Bajaj Finserv employs a structured, multi-stage hiring process that frequently begins with online assessments focusing on domain-specific coding and API development. Technical interviews are highly practical, emphasizing stack-specific proficiency (Node.js, Java, Spring Boot) and system design, while behavioral rounds prioritize long-term career alignment.
The interview was of average difficulty and focused on basic cloud infrastructure knowledge.
The interview focused on fundamental cloud computing concepts and infrastructure components.
What are the cloud deployment models
What are ec2
What is VPC in cloud
What is the security group
The candidate did not get selected for the Node.js-MongoDB role. The interview process consisted of four rounds: two online assessments (API request using Postman and a HackerRank test with Node.js, MongoDB, aptitude, and programming questions), followed by two technical interviews (one covering JavaScript and MongoDB basics, and another focused on system design with the CTO). 98 students from the candidate's college were selected across various job profiles.
Round 1: 1-hour online test on initiating API requests to send basic details (Name, College email ID, College Registration No., DOB) using Postman. Round 2: 1-hour online test on HackerRank with 15 Node.js and MongoDB questions, 3 aptitude-based questions, and 1 programming question (medium-hard difficulty, restricted to Node.js).
1-hour online test to initiate a successful API request to send basic details using Postman.
1-hour online test on HackerRank with 15 Node.js and MongoDB questions, 3 aptitude-based questions, and 1 programming question (medium-hard difficulty, restricted to Node.js).
Technical interview covering JavaScript basics (promises vs. async-await), favorite data structure (HashMap), MongoDB basics (indexes, unique indexing), differences between for loop and forEach(), and resume-based questions.
Technical interview with the CTO of Bajaj Finserv Health, focusing on system design and scenario-based questions related to microservices and new feature development.