Interview Experience: Dassault Systemes- 3YOE Java
Summary
I interviewed for a Java Backend Developer role at Dassault Systemes in Bangalore, completing two out of three rounds. The experience included deep technical discussions, live coding, and system design challenges. Unfortunately, I was not selected for the position.
Full Experience
I interviewed for a Java Backend Developer role at Dassault Systemes in Bangalore. The entire process involved three main rounds, though I only completed two.
Round 1: Telephonic HR / Profile Matching
This was a preliminary HR round where we discussed my past projects, reasons for switching jobs, total years of experience, and salary expectations.
Round 2: Face-to-Face Interview (Technology Lead Panel)
This technical round lasted about 1.2 hours and involved two panel members. We started with my introduction and a detailed discussion about my past projects. They asked in-depth questions based on my resume. I was then asked to draw an architecture diagram of my project on a whiteboard, explaining the microservice architecture, asynchronous communications, API Gateways, Spring Security, and Load Balancing, focusing on the 'WHYs' and 'WHATs' of each component. Following this, I had to write pseudo-code for a basic star ('*') pattern printing question on the whiteboard. The interview also delved into Spring Boot core questions, annotation usage, REST architecture, validation checks, and specific annotations used in my past projects. Further discussions covered database communication, MVC architecture, and handling edge cases. I also faced intermediate-level questions on Java 8, Exception handling, Concurrency, and in-depth OOPs concepts, particularly inheritance and abstraction. A live coding exercise required me to implement a simple User Defined Exception in Notepad. We also touched upon Unit Testing, how I handled bugs from UAT testing, and my approach to exceptions. Finally, we discussed my college project and my reasons for seeking a new role.
Round 3: Interview with Senior Technology Architect
Unfortunately, I was unable to make it to this round.
Overall, I was not selected for the position.
Interview Questions (6)
I was asked to draw an architecture diagram of my past project on a whiteboard. I had to explain the microservice architecture, asynchronous communications, API Gateways, Spring Security, and Load Balancing, detailing the 'WHYs' and 'WHATs' of each component.
I was asked to write pseudo-code for a basic star ('*') pattern printing question on the whiteboard.
I had a live coding session where I was asked to implement a simple User Defined Exception in Notepad.
I was questioned on Spring Boot core concepts, annotation usage, REST architecture principles, validation checks, and specific annotations used in my past projects. This also included discussions on DB communication, MVC architecture, and handling edge cases within a Spring Boot context.
I faced intermediate-level questions covering Java 8 features, Exception handling, Concurrency, and in-depth OOPs concepts, especially focusing on inheritance and abstraction.
Questions were asked about Unit Testing, specifically how I handled bugs encountered during UAT (User Acceptance Testing) and my strategies for handling exceptions in production.
Preparation Tips
I applied for this role through the Naukri Portal, and the HR team directly contacted me. My preparation primarily focused on Java Backend Development. However, it turned out that intermediate Front-end (Angular) competency was also expected, which was a surprise.