Emtec India Support Engineer Interview: Rounds, Questions and Preparation

What the job involves

A Support Engineer in Indian IT services works on the front line of client-facing technical support, resolving incidents and service requests within agreed SLAs. The day typically involves monitoring ticketing tools, troubleshooting application or infrastructure issues, escalating complex problems, and documenting fixes for knowledge bases. Freshers often rotate through shifts and gradually take ownership of specific accounts or modules.

Role and Technical Knowledge

1. 1

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

   An incident is an unplanned interruption or degradation of service, while a service request is a routine user ask like password reset or access. Mention that incidents aim for quick restoration, requests follow a defined fulfilment process.

2. 2

   Explain the OSI model layers and where common support issues occur.

   Name all seven layers briefly, then link common issues: physical layer for cable or port problems, network layer for IP or routing, transport layer for port or firewall blocks, and application layer for service errors. Show you can map a symptom to a layer.

3. 3

   What steps do you follow when a user reports they cannot access an internal web application?

   Start with scope: is it one user or many? Check network connectivity, DNS resolution, browser or cache, VPN status, and application logs. Mention documenting findings and escalating with evidence if it is a server-side issue.

4. 4

   What are the common causes of a 'server not reachable' error and how would you check them?

   Cover ping to test reachability, traceroute to find where packets drop, checking the service port with telnet or netstat, firewall rules, and whether the server process is running. Emphasise a layered, evidence-based approach.

Practical Scenarios

1. 5

   You have three tickets: a P1 server down, a P2 application slow for many users, and a P3 password reset. How do you prioritise?

   Follow severity and impact: P1 first because it affects business continuity, then P2 because multiple users are impacted, then P3. Mention informing your lead about the P1 and setting expectations on the others.

2. 6

   A client is angry that their issue is not resolved within SLA. How do you handle the call?

   Listen without interrupting, acknowledge the delay, apologise for the impact, give a clear status and next update time, and avoid blaming other teams. Show empathy and ownership rather than defensiveness.

3. 7

   You suspect the issue is beyond your access or knowledge. What do you do?

   Gather logs, error messages, steps to reproduce, and impact, then escalate to the right team with a clear summary. Mention updating the ticket and keeping the user informed instead of going silent.

4. 8

   How would you troubleshoot a slow database query reported by an application team?

   Check for missing indexes, run an execution plan, look at locks or blocking sessions, review server CPU and memory, and check recent changes. Suggest testing in a lower environment before any fix in production.

Tools and Process Awareness

1. 9

   Which ticketing tools have you used or studied, and what fields matter most in a ticket?

   Name tools like ServiceNow or Jira if familiar, and highlight fields like category, priority, impact, urgency, description, and resolution notes. Show that clear tickets reduce back-and-forth.

2. 10

   What is an SLA and why is it important in support?

   SLA is a contractual commitment on response and resolution times. Explain that it drives prioritisation, client trust, and reporting, and that breaching it can affect the account.

3. 11

   How do you use logs to debug an application error?

   Describe locating the timestamp of the error, reading the stack trace or error code, correlating with other logs, and checking recent deployments or config changes. Mention not pasting sensitive data into public tools.

4. 12

   What is the difference between a known error and a problem record?

   A problem is the underlying cause of one or more incidents, while a known error is a problem with a documented root cause and workaround. This shows ITIL awareness beyond ticket closing.

Behavioural and HR Questions

1. 13

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

   Be honest and specific. If yes, say you understand support is 24x7 for many clients and you are willing to adapt. If you have constraints, state them clearly and professionally.

2. 14

   Tell me about a time you helped someone solve a technical problem.

   Use a simple STAR structure: situation, task, action, result. Pick a college project, lab, or personal example and highlight patience, clear explanation, and a successful outcome.

3. 15

   How do you handle a situation where you do not know the answer?

   Say you would acknowledge it honestly, research using internal knowledge bases or documentation, ask a senior, and revert with a solution. Show willingness to learn rather than pretending.

4. 16

   Why do you want to start your career in support engineering?

   Link it to learning how systems work end to end, building client communication skills, and growing into roles like system administration or DevOps. Avoid saying it is just a backup option.