J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Netsmartz (Chandigarh)
Entretien
The interview process is smooth and easy, consisting of three rounds: a technical round, a VP round, and an HR round. Each step is straightforward, ensuring a seamless experience for candidates.
Questions d'entretien [1]
Question 1
"Describe a challenging project you worked on, the obstacles you faced, and how you overcame them."
J'ai passé un entretien chez Netsmartz (Chandigarh)
Entretien
Netsmartz follows a two-step interview process. The first round is a technical interview, where you’ll interact with one of our senior developers or technical team members to assess your skills, project experience, and problem-solving approach. If you clear this round, you’ll proceed to a final interview with our VP, which focuses on cultural fit, career goals, and overall alignment with the company’s vision.
Questions d'entretien [1]
Question 1
In my technical interview, one of the most interesting questions they asked me was to explain how I would optimize a Node.js API that’s taking too long to respond under heavy load. They wanted to know my approach to identifying bottlenecks, techniques like query optimization, caching, and asynchronous processing, and how I’d ensure the API remains scalable and secure.
J'ai postulé via un recruteur. J'ai passé un entretien chez Netsmartz en mai 2025
Entretien
Unfortunately, my experience with this company has not been positive. The hiring process does not seem to prioritize actual skills or merit. Instead, internal politics appear to play a significant role, making it frustrating for genuinely qualified candidates.
Additionally, the interview process is unnecessarily difficult and inconsistent. Candidates are often asked tough technical questions, only to be rejected in the final round without any clear or valid reason. Overall, the process feels like a waste of time and effort.
Questions d'entretien [1]
Question 1
Expect tough questions on Node.js event loop, async patterns, memory leaks, rate limiting, middleware, streams, and security. For MongoDB, be ready for indexing, aggregation pipeline, data modeling, sharding, transactions, schema validation, and query optimization with explain() and a lot of coding questions