Application Support Engineer (L2)

Credible resume terms

Terms that should plausibly appear on a real Application Support Engineer (L2) resume. “Must-have” marks the ones whose total absence is a genuine red flag.

• L1/L2/L3 SupportMust-have

  How IT support is split by depth. L1 (the help desk or service desk) takes the first call and fixes common issues from a script; L2 handles problems that need hands-on technical work; L3 is the specialists or developers who fix the root cause in the system or code.

• ITIL

  The most widely used set of good practices for running IT services: how incidents are logged and resolved, how recurring problems are traced to a root cause, and how changes are approved before they reach live systems.

• Incident Response

  The structured process a team follows when something breaks in production — detecting, communicating, mitigating, and resolving the issue.

• Job Scheduling (Control-M, Autosys)

  Tools that run a company's batch jobs on a timetable and in the right order: end-of-day banking runs, data loads, report generation.

• SQLMust-have

  The standard language for querying and managing data in relational databases.

• LinuxMust-have

  An open-source operating system that runs the vast majority of servers, cloud infrastructure, and containers — comfort with its command line is assumed baseline for most backend and DevOps work, even when the day-to-day IDE is on Windows or Mac.

• Bash / Shell Scripting

  Writing scripts in a Unix shell (most commonly Bash) to automate command-line tasks — file processing, deployment steps, cron jobs — often the glue between other tools rather than an application language itself.

• ServiceNow

  A cloud platform companies use to run IT support and internal workflows such as tickets, change requests, asset tracking and HR requests.

• SLA / Uptime

  An SLA is a commitment about a system's reliability (e.g. 99.9% uptime); uptime measures how much of the time a system is actually available and working.

• Runbook

  A documented, step-by-step procedure for handling a specific, known operational task or failure scenario, so it doesn't rely on one person's memory.

• ELK Stack

  A common set of tools (Elasticsearch, Logstash, Kibana) for collecting logs from many systems into one searchable place, so engineers aren't SSHing into individual servers to read log files during an incident.

• Postmortem

  A written review conducted after an incident to understand what went wrong and prevent it from recurring, ideally 'blameless' — focused on the system and process, not blaming an individual.

Application Support Engineer (L2): screening questions

One question per core skill, must-haves first. Each term’s page shows what a junior and a senior answer sound like.

1. L1/L2/L3 Support

   “Which support level were you at? Tell me about a problem you fixed at the root so the tickets stopped coming back.”

2. SQL

   “Walk me through the last complex SQL query you wrote — what problem was it solving?”

3. Linux

   “Walk me through how you'd track down what's eating memory or CPU on a Linux server, without a GUI.”

4. Incident Response

   “Tell me about the worst incident you were part of. What was your specific role in resolving it?”

5. Postmortem

   “Tell me about a postmortem you wrote or contributed to. What changed on your team as a direct result?”

Adjacent, but not real signal

These read as related, but they don’t tell you this candidate can do this job — they usually belong to one of the roles below.

• Helpdesk Tools (Zendesk, Freshdesk)

  Software that support teams use to receive, track and answer customer or employee requests as tickets: Zendesk and Freshdesk for customer support, Freshservice and Jira Service Management for internal IT.

• Microsoft 365 / Exchange Online

  Running a company's Microsoft email and collaboration services: Exchange for mailboxes, plus Teams, SharePoint and OneDrive, along with licences and security settings.

• SLO and SLI

  The internal reliability target a team holds itself to, and the specific measurement it is judged by.

Most often confused with

• Technical Support Engineer

  Solves technical problems customers hit with a company's product, usually at a SaaS or software company: reproducing bugs, reading logs, testing APIs, querying data and handing real defects to engineering with clear evidence. Faces customers, which is where it differs from application support, which keeps internal business systems running.

• SRE

  Applies software-engineering discipline to keeping systems reliable at scale — on-call, incident response, and error budgets are the job, not a side effect of it.

Application Support Engineer (L2): search strings