Software Developer Engineer 1
Interview Date
December 19, 2023 (Published Date)
Result
Not Specified (Implies progression through rounds)
Difficulty
Medium
Rounds
4 rounds
Drive Type
Full-Time
Topics asked
Detailed experience
College: Not Specified
Interview Date: December 19, 2023 (Published Date)
Interview Type: Full-Time
Result: Not Specified (Implies progression through rounds)
Difficulty: Medium
Rounds: 4 rounds
Topics Asked: Aptitude, Logical Reasoning, Java output, Technical MCQs, DSA, Database, Project discussion, REST API design, System Design (handling high load), Spring/Core Java, Merge Sort, Binary Search, Team management, conflict resolution.
This GeeksforGeeks user provided a detailed account of their Chargebee Software Developer Engineer 1 interview experience.
Round 1: Online Assessment (1 hour 30 minutes)
This round consisted of 5 MCQ questions covering aptitude, logical reasoning, Java output, and technical topics. The aptitude and logical questions were described as intuitive and tricky rather than formula-based. It also included 2 easy DSA coding questions and 2 easy database questions.
Round 2: Technical Interview Round-1
Questions began with a discussion of the candidate's projects, specifically a project on REST, leading to typical questions about REST (Why, How) and designing a REST API for a part of the project. A system design scenario was posed: designing a restaurant service where 5 lakh restaurants send requests to the server and database concurrently. The interviewer asked how to manage these requests efficiently, to which the candidate responded with concepts like Load Balancer, Sharding, and Master-Slave architecture. Questions on Spring-related and Core Java topics were also asked. The candidate was asked to write algorithms for Merge Sort and Binary Search.
Round 3: Technical Interview Round 2
This round involved further discussion on all projects and a comparison between REST and SOAP.
Round 4: Managerial Round
This round included basic questions about team management and conflict. The interviewer presented scenarios that could arise in a team and asked for the candidate's approach. Discussions also revolved around known technologies and the candidate's favorite project and why.