Nagarro India Support Engineer Interview: Rounds, Questions and Preparation

What the job involves

Support Engineers in Indian IT services handle client-reported technical issues, troubleshoot software and infrastructure problems, and ensure service level agreements are met. They work in shifts, document resolutions, and escalate complex issues to engineering or product teams. The role is a common entry point for freshers into managed services and application support projects.

Role and Technical Knowledge

1. 1

   What is the difference between an incident and a problem in ITIL?

   Explain that an incident is an unplanned interruption, while a problem is the root cause of one or more incidents. Mention that problem management aims to prevent recurrence.

2. 2

   How would you troubleshoot a user's inability to access a web application?

   Cover checking network connectivity, browser and cache, application logs, server status, and DNS resolution. Show a structured, step-by-step approach.

3. 3

   What are the key differences between TCP and UDP?

   Highlight connection-oriented vs connectionless, reliability, ordering, and use cases like HTTP vs DNS. Relate to support scenarios such as packet loss.

4. 4

   Explain what an SLA is and why it matters in support.

   Define service level agreement, mention response and resolution targets, and explain how it drives prioritisation and client trust.

Practical Scenarios

1. 5

   A critical production server is down and multiple clients are affected. What do you do first?

   Show prioritisation: acknowledge the incident, check monitoring alerts, inform stakeholders, and start basic diagnostics. Emphasise communication and following escalation matrix.

2. 6

   A client is angry because their ticket has not been resolved for two days. How do you handle it?

   Demonstrate empathy, take ownership, provide a clear status update, and set realistic expectations. Mention documenting the interaction and escalating if needed.

3. 7

   You suspect a recent change caused a new issue. How do you verify and what do you do next?

   Talk about checking change logs, comparing before/after states, and involving the change owner. Suggest rollback if safe and following change management process.

4. 8

   How would you handle a ticket that requires access you do not have?

   Explain the process: raise an access request, follow security policies, and inform the user of the timeline. Never bypass security controls.

Behavioural and HR

1. 9

   Why do you want to work as a Support Engineer in an IT services company?

   Connect interest in troubleshooting, client interaction, and learning new technologies. Mention exposure to diverse environments and career growth.

2. 10

   Are you comfortable working in rotational shifts, including night shifts?

   Answer honestly and positively if you are. Mention adaptability and willingness to support global clients across time zones.

3. 11

   Tell me about a time you had to explain a technical issue to a non-technical person.

   Use a STAR example from college projects or internships. Focus on simplifying jargon and confirming understanding.

4. 12

   How do you handle stress when multiple tickets are pending?

   Describe prioritisation based on impact and urgency, using checklists, and taking short breaks. Show that you stay calm and communicate.

Tools and Processes

1. 13

   What is the purpose of a ticketing tool like ServiceNow or Jira?

   Explain tracking, categorisation, assignment, and reporting of incidents and requests. Mention how it helps meet SLAs and maintain audit trails.

2. 14

   How would you use logs to diagnose an application error?

   Talk about identifying log location, filtering by timestamp and severity, and correlating with user reports. Mention tools like grep, Event Viewer, or Splunk.

3. 15

   What basic SQL query would you write to check if a user record exists?

   Show a simple SELECT statement with a WHERE clause. Mention avoiding updates/deletes in production without approval.

4. 16

   What steps would you take to remotely troubleshoot a user's machine?

   Cover remote desktop tools, checking event logs, running diagnostics, and guiding the user. Emphasise security and privacy.