Xoriant 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 support, resolving technical issues, monitoring systems, and escalating complex problems to senior teams. Day to day, you handle tickets, troubleshoot software or infrastructure problems, communicate with users, and document solutions. This role is common in fast-growing IT services companies that provide managed services or product support to global clients.

Role and Technical Knowledge

1. 1

   What is the difference between a hub, switch, and router?

   Explain that a hub broadcasts to all ports, a switch forwards based on MAC addresses, and a router connects different networks using IP addresses.

2. 2

   How would you troubleshoot a user who cannot access the internet?

   Start with basic checks: physical connections, IP configuration, ping gateway, DNS resolution, and then move to firewall or proxy issues.

3. 3

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

   Define Service Level Agreement as a contract that sets response and resolution times; explain how it prioritizes tickets and measures performance.

4. 4

   Explain the difference between a process and a thread.

   A process is an independent program with its own memory space; a thread is a smaller unit within a process that shares resources.

Practical Scenarios

1. 5

   A critical production server is down and users are panicking. What do you do first?

   Prioritize restoring service, communicate status to stakeholders, follow incident management steps, and document actions for post-mortem.

2. 6

   You receive a ticket that is outside your knowledge. How do you handle it?

   Acknowledge the ticket, research using available knowledge base, escalate to the right team if needed, and keep the user informed.

3. 7

   How would you handle a user who is angry and blaming your team for a recurring issue?

   Listen without interrupting, apologize for the inconvenience, take ownership, provide a clear action plan, and follow up until resolved.

4. 8

   You notice a pattern of similar tickets. What could you do to reduce them?

   Suggest creating a knowledge base article, automating a fix, or training users to prevent future occurrences.

Behavioural and HR

1. 9

   Tell me about a time you solved a problem under pressure.

   Use the STAR method: describe the situation, task, action, and result, highlighting calmness and a positive outcome.

2. 10

   Why do you want to work in support instead of development?

   Show interest in troubleshooting, client interaction, and learning broad technologies; mention career growth into specialized support or DevOps.

3. 11

   How do you handle working in rotational shifts, including night shifts?

   Express willingness and adaptability, mention any prior experience, and emphasize focus on health and time management.

4. 12

   Where do you see yourself in three years?

   Align with the company: gaining expertise, taking certifications, and moving into senior support or team lead roles.

Tools and Processes

1. 13

   What is a ticketing tool and which ones have you used?

   Mention any exposure to tools like ServiceNow, Jira, or Freshdesk; explain how tickets are logged, prioritized, and resolved.

2. 14

   What are the steps in an incident management process?

   Describe identification, logging, categorization, prioritization, diagnosis, escalation, resolution, and closure.

3. 15

   How do you ensure proper documentation of a solution?

   Write clear steps, include screenshots if needed, update the knowledge base, and share with the team for future reference.

4. 16

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

   A known error is a problem with a documented root cause and workaround; a problem is the underlying cause of one or more incidents.