I applied through university. The process took 1 day. I interviewed at Dextra Labs (Mumbai) in Dec 2025
Interview
Basic fundamentals should be clear and focused on projects . Should know each and everything about projects and also know fundamentals of each thing you mention for eg oops , data structures and many other things you mention
Interview questions [1]
Question 1
Oops,Dsa,Projects and Dbms and also error solving problems
I applied online. The process took 1 week. I interviewed at Dextra Labs (Mumbai) in July 2025
Interview
The interview process at Dextra Labs consisted of three virtual rounds:
Aptitude Round:
This round included basic logical reasoning and quantitative questions. It was fairly straightforward.
Coding Round:
I was given three coding problems based on arrays and backtracking, with a medium level of complexity. I was able to solve them within the time limit.
Technical Interview:
This round focused on the backend technologies mentioned in my resume, particularly Node.js. I was asked questions on:
JWT authentication
Middleware in Express.js
Bot rate limiting
The interviewer also tested my understanding of Java OOPs concepts, CORS, and SOLID principles. The interview was technical and went well.
Despite successfully completing all rounds and following up via email twice, I have yet to receive any response. It’s unfortunate that after such a detailed process, the company chooses not to communicate with candidates — something that reflects poorly on its professionalism.
Interview questions [1]
Question 1
The interviewer primarily focused on the backend technologies listed in my resume. Since his background was in Java backend development, most of the questions were aligned accordingly. I was asked about:
Node.js concepts, especially how I implemented JWT authentication, middleware, and rate limiting in my projects.
My understanding of Java OOP concepts, SOLID principles, and CORS.
Real-world backend scenarios I handled in my personal and academic projects.
The discussion was technical and in-depth, and I was able to explain my implementation choices and architecture decisions confidently.
