NEC India Support Engineer Interview: Rounds, Questions and Preparation

What the job involves

Support Engineers in Indian IT services provide first and second level technical support to enterprise clients, handling incidents, service requests, and escalations across networks, servers, applications, and end-user systems. The role involves troubleshooting, documentation, coordination with internal teams, and adherence to SLAs, often in a 24x7 shift environment. Freshers typically start on a helpdesk or remote support desk, gaining exposure to ITIL processes and multiple customer environments.

Role and Technical Knowledge

1. 1

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

   Explain that an incident is an unplanned interruption or degradation of service, while a service request is a routine user ask like password reset or software installation. Mention that both are tracked via tickets with different SLAs.

2. 2

   A user cannot access the internet but can access local file shares. How would you troubleshoot?

   Walk through checking IP configuration, DNS settings, default gateway, and proxy settings. Suggest ping tests to internal and external addresses, and mention checking the browser or firewall if needed.

3. 3

   What steps would you take to reset a user's password in Active Directory?

   Cover verifying the user's identity, locating the account in AD Users and Computers, resetting the password, forcing a change at next logon, and informing the user securely. Mention documenting the ticket.

4. 4

   Explain the OSI model layers and give one support example for each.

   List the seven layers briefly and relate them to support tasks: physical cable checks, switch port issues, IP conflicts, firewall rules, session timeouts, encryption errors, and application login failures.

Practical Scenarios

1. 5

   You receive multiple tickets at once: a VIP user cannot log in, a printer is down for a team, and a server disk is 90 percent full. How do you prioritize?

   Prioritize based on impact and urgency: VIP login first, then server disk to prevent outage, then printer. Mention communicating timelines to users and escalating the server issue if beyond your access.

2. 6

   A user reports that their system is very slow. What information do you gather and what checks do you run?

   Ask when it started, what changed, and whether it affects one app or the whole system. Check Task Manager for CPU, memory, and disk usage, run malware scans, review startup programs, and check for pending updates.

3. 7

   You have resolved a ticket but the user calls back saying the issue persists. What do you do?

   Reopen the ticket, apologize, and re-verify the fix from the user's perspective. Gather new symptoms, check if the root cause was misdiagnosed, and involve a senior or second-level team if needed.

4. 8

   How would you handle a suspected phishing email reported by a user?

   Advise the user not to click links or attachments, isolate the email if possible, collect headers, and report to the security team. Mention checking if others received the same email and following the company's incident response process.

Behavioural and Situational

1. 9

   Tell me about a time you helped someone solve a technical problem. What was your approach?

   Use the STAR method: describe the situation, the steps you took, the outcome, and what you learned. Focus on patience, clear communication, and following a logical troubleshooting process.

2. 10

   How would you handle an angry customer who blames you for a delay caused by another team?

   Show empathy, avoid blaming others, acknowledge the delay, and explain what you are doing to resolve it. Mention setting realistic expectations and following up until closure.

3. 11

   This role may require night shifts and rotational weekends. How do you feel about that?

   Be honest and positive if you can commit. Mention any prior experience with odd hours, your willingness to adapt, and how you plan to manage health and work-life balance.

4. 12

   Describe a time you had to learn a new tool or technology quickly. How did you go about it?

   Highlight self-learning through documentation, online resources, or peers. Show that you can apply new knowledge to real tasks and ask for help when needed.

HR and Company Fit

1. 13

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

   Connect your interest in troubleshooting and customer service with the learning opportunities in a services environment. Avoid saying it is just a temporary job.

2. 14

   What do you know about our company and the kind of support we provide?

   Research the company's domain, major clients, and support offerings. Mention any public information about their technology focus or service lines without claiming inside knowledge.

3. 15

   Where do you see yourself in three years?

   Show a realistic path: gaining certifications, moving to second-level support or a specialized technology track, and taking on more responsibility. Avoid saying you want to leave support immediately.

4. 16

   Are you comfortable working in a team where you may have to coordinate with people across different cities or countries?

   Emphasize clear written and verbal communication, respect for different time zones, and experience working in college projects or groups with remote members.