We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

Application Support: market

Data as of November 19, 2026: 240 open Application Support jobs, 27% remote among jobs that state a work format; median advertised salary $6,250/mo (from 16 postings that state a salary). Source: Zorky, updated daily.

Application Support (production support, application support engineer) — a specialist who ensures business applications work in production: watches that corporate and industrial systems (banking systems, ERP, billing, trading and industry applications) work stably, takes apart incidents, diagnoses outages, works with logs and databases, interacts with development. This is the most technical of support roles: it's closest to production and to engineering. Unlike Technical Support, which helps users with problems (see /research/support/technical-support), Application Support is responsible for the applications themselves in operation — monitors them, fixes them when they behave wrong, and keeps them alive. The role is especially characteristic of banks, fintech and large enterprise, where there are many critical applications in production. Role family: Application Support Specialist / Engineer (application support), Production Support Engineer (production support — a close synonym), Senior Application Support, Application Support Lead, adjacent and career-linked — DevOps, SRE (see /research/devops), systems analyst (see /research/analyst/systems-analyst), QA. Responsibilities: monitoring of applications in production, intake and analysis of incidents, diagnosis of outages and abnormal behavior (logs, databases, metrics), resolution within one's competence or escalation to development, support of routine operations (running processes, updates, releases), work by SLA, incident management and documentation, interaction with development, infrastructure and business users. Stack / tools 2026: SQL (mandatory — diagnostics through the database), work with logs (reading, searching, analysis; ELK / Grafana Loki etc.), Linux (command line, production servers), monitoring (Zabbix, Prometheus + Grafana), scripting (Bash, Python — automation and routine tasks), ticket and incident systems, understanding of APIs and integrations, sometimes message queues (Kafka etc.), ITIL methodology and incident management. Top skills: sql, itil, linux, cloud, python. Among jobs with a stated work format, 27% are remote. Application Support — a technical and, for the support segment, well-paid role; it gives a deep understanding of production and opens a direct path into DevOps, SRE, systems analysis and engineering.

Data as of:

Key numbers for the Application Support market: open jobs, median salary, observed talent pool and remote share.

240
open jobs — by job title, reposts merged
$6,250
median $/mo
27%
remote

The Application Support market currently has 240 open roles, 203 of them freshly observed. Median salary $6,250/mo.

Among jobs with a stated work format, 27% are remote. Nuance — support of critical production systems often involves a shift schedule and duty (including 24/7); banks and fintech often prefer hybrid for security reasons.

⚠ salary known for 16 of 240 jobs; remote share from 162 with a stated format; 203 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many Application Support postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.

New postings per week

Chart data
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-014
2026-06-082
2026-06-1510
2026-06-2239
2026-06-2936
2026-07-0637
2026-07-1370
2026-07-2064
2026-07-2738
2026-08-0336
2026-08-1024
2026-08-1731
2026-08-2436
2026-08-3141
2026-09-0737
2026-09-1431
2026-09-2175
2026-09-2872
2026-10-0553
2026-10-12213
2026-10-19103
2026-10-26124
2026-11-02109
2026-11-0993

Active sources per week

Sources over the period: 105. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-014
2026-06-082
2026-06-157
2026-06-2218
2026-06-2918
2026-07-0612
2026-07-1324
2026-07-2022
2026-07-2720
2026-08-0315
2026-08-1014
2026-08-1717
2026-08-2419
2026-08-3112
2026-09-0720
2026-09-1418
2026-09-2124
2026-09-2826
2026-10-0522
2026-10-1231
2026-10-1936
2026-10-2629
2026-11-0230
2026-11-0928
New sources connected: Jun 22 +14 · Jun 29 +9 · Jul 6 +6 · Jul 13 +10 · Jul 20 +11 · Jul 27 +8 · Oct 12 +7 · all weeks (21) in the table
WeekNew sourcesNew postings
Jun 8+12
Jun 15+410
Jun 22+1439
Jun 29+936
Jul 6+637
Jul 13+1070
Jul 20+1164
Jul 27+838
Aug 3+336
Aug 10+224
Aug 17+231
Aug 24+336
Sep 7+237
Sep 14+131
Sep 21+575
Sep 28+172
Oct 12+7213
Oct 19+5103
Oct 26+2124
Nov 2+3109
Nov 9+293

The current week is not over yet and is not shown: an incomplete week would look like a drop.

Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.

Chart data
Timeline: postings and sources — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-0144
2026-06-0822
2026-06-15107
2026-06-223918
2026-06-293618
2026-07-063712
2026-07-137024
2026-07-206422
2026-07-273820
2026-08-033615
2026-08-102414
2026-08-173117
2026-08-243619
2026-08-314112
2026-09-073720
2026-09-143118
2026-09-217524
2026-09-287226
2026-10-055322
2026-10-1221331
2026-10-1910336
2026-10-2612429
2026-11-0210930
2026-11-099328

Salaries over time

Median Application Support salary per week, USD per month.

Median salary, USD per month

Chart data
Median salary, USD per month. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodMedianPostings with a salary per week (n)
2026-10-196,12810
2026-10-265,88417
2026-11-02—7
2026-11-095,75510

The series starts on Oct 19: there is no data before that.

Postings with a salary per week (n)

Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.

Chart data
Salaries over time — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekMedian
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-20—
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-31—
2026-09-07—
2026-09-14—
2026-09-21—
2026-09-28—
2026-10-05—
2026-10-12—
2026-10-196,128
2026-10-265,884
2026-11-02—
2026-11-095,755

Remote work over time

Share of Application Support postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-06-2218.8
2026-06-298
2026-07-0647.1
2026-07-1313.3
2026-07-2052.9
2026-07-2736.4
2026-08-039.7
2026-08-100
2026-08-1716
2026-08-246.7
2026-08-315.7
2026-09-076.2
2026-09-1413.6
2026-09-2121.2
2026-09-2829.6
2026-10-0511.8
2026-10-1230.2
2026-10-1932.5
2026-10-2623.2
2026-11-0221.5
2026-11-0910.8

The series starts on Jun 22: there is no data before that.

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Chart data
Remote work over time — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-2218.8
2026-06-298
2026-07-0647.1
2026-07-1313.3
2026-07-2052.9
2026-07-2736.4
2026-08-039.7
2026-08-100
2026-08-1716
2026-08-246.7
2026-08-315.7
2026-09-076.2
2026-09-1413.6
2026-09-2121.2
2026-09-2829.6
2026-10-0511.8
2026-10-1230.2
2026-10-1932.5
2026-10-2623.2
2026-11-0221.5
2026-11-0910.8

Technologies over time

How the share of Application Support postings mentioning each of the top technologies changed.

Postings mentioning the technology, %

Chart data
Postings mentioning the technology, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodSQLclouditil
2026-09-2124.424.47.3
2026-09-2851.131.925.5
2026-10-0548.313.834.5
2026-10-1235.236.119.4
2026-10-1930.733.324
2026-10-2642.135.531.6
2026-11-0253.825.626.9
2026-11-0946.827.421

The series starts on Sep 21: there is no data before that.

Up to 5 on the chart:

Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.

Chart data
Technologies over time — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekSQLclouditilPythonAWS
2026-08-10—————
2026-08-17—————
2026-08-24—————
2026-08-31—————
2026-09-07—————
2026-09-14—————
2026-09-2124.424.47.37.34.9
2026-09-2851.131.925.58.521.3
2026-10-0548.313.834.524.13.4
2026-10-1235.236.119.410.211.1
2026-10-1930.733.3242018.7
2026-10-2642.135.531.62513.2
2026-11-0253.825.626.916.714.1
2026-11-0946.827.42122.614.5

Countries over time

How the share of Application Support postings in each of the top countries changed, per week.

Postings in the country, %

Chart data
Postings in the country, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodPolandIndiaUK
2026-06-2245.75.72.9
2026-06-2918.218.29.1
2026-07-066.96.96.9
2026-07-1315.36.811.9
2026-07-2033.97.15.4
2026-07-272011.417.1
2026-08-0318.815.637.5
2026-08-10013.613.6
2026-08-173.711.17.4
2026-08-248.82.929.4
2026-08-318.116.235.1
2026-09-075.619.48.3
2026-09-143.614.317.9
2026-09-218.816.217.6
2026-09-2827.411.36.5
2026-10-0518.95.77.5
2026-10-126.410.87.6
2026-10-1926.810.37.2
2026-10-268.117.19
2026-11-024.714.18.2
2026-11-0910.814.510.8

The series starts on Jun 22: there is no data before that.

Up to 5 on the chart:

Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.

Chart data
Countries over time — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekPolandUSAIndiaUKAustralia
2026-06-01—————
2026-06-08—————
2026-06-15—————
2026-06-2245.711.45.72.90
2026-06-2918.26.118.29.10
2026-07-066.910.36.96.934.5
2026-07-1315.35.16.811.922
2026-07-2033.910.77.15.419.6
2026-07-27202.911.417.111.4
2026-08-0318.89.415.637.53.1
2026-08-1009.113.613.64.5
2026-08-173.718.511.17.411.1
2026-08-248.814.72.929.417.6
2026-08-318.113.516.235.113.5
2026-09-075.68.319.48.316.7
2026-09-143.63.614.317.925
2026-09-218.816.216.217.68.8
2026-09-2827.49.711.36.511.3
2026-10-0518.91.95.77.59.4
2026-10-126.415.910.87.63.2
2026-10-1926.813.410.37.23.1
2026-10-268.114.417.1913.5
2026-11-024.712.914.18.29.4
2026-11-0910.820.514.510.87.2

Clean market: hiring index

The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Application Support.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.

Chart data
Clean market: hiring index — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open Application Support jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand240
Open demand240
Observed supply— not published

Application Support — the most technical of support roles, steadily in demand where there are many critical applications in production (banks, fintech, large enterprise, telecom). Drivers 2026: growth in the number and complexity of production systems, requirements for their reliability. The role borders SRE / DevOps and often evolves toward them.

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

How salaries in Application Support jobs are distributed, in US dollars per month.

Salary distribution

P25 $3,250 · P50 $6,250 · P75 $7,500
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k0
$1–2k1
$2–3k2
$3–4k1
$4–5k2
$5–6k1
$6–7k3
$7–8k2
$8–9k2
$9–10k0
$10–12k1
$12–15k1
$15–20k0
$20k+0
Salary in postings: base 240
  • usable for the calculation: 16 (6.7%)
  • stated but not converted to USD/month: 29 (12.1%)
  • not stated: 195 (81.3%)

One in ten postings offers under $2,000, one in ten over $10,625. Half of the postings offer between $3,250 and $7,500. Sample: 16.

Pay is determined by technical depth (SQL, logs, architecture) and incident management experience.

⚠ percentiles from 16 salaries out of 240 jobs — a guide on a small sample

Chart data
Salary distribution — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0000
$1–2k1,0002,0001
$2–3k2,0003,0002
$3–4k3,0004,0001
$4–5k4,0005,0002
$5–6k5,0006,0001
$6–7k6,0007,0003
$7–8k7,0008,0002
$8–9k8,0009,0002
$9–10k9,00010,0000
$10–12k10,00012,0001
$12–15k12,00015,0001
$15–20k15,00020,0000
$20k+20,000—0

Which countries have the most open Application Support jobs.

Demand geography

countryjobsshare
India3819.6%
Poland3618.6%
United States2814.4%
United Kingdom147.2%
Thailand105.2%
Singapore94.6%
Canada84.1%
Germany63.1%
Portugal52.6%
Hong Kong52.6%
Other countries3518%

Leader by Application Support job count — India (38 positions). Demand concentrates in banks and fintech (the largest employer — critical 24/7 systems), telecom, large enterprise with ERP, at IT integrators, at large tech companies (there — often under the name SRE / DevOps).

⚠ job counts only: salary by country is not published

Chart data
Demand geography — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
IN38
PL36
US28
GB14
TH10
SG9
CA8
DE6
PT5
HK5

Which technologies are most often required in the same job as Application Support.

Used together with

sql
11146.3%
cloud
8033.3%
itil
6928.7%
python
4719.6%
aws
4117.1%
oracle
3916.3%
azure
3715.4%
servicenow
3313.8%
service desk
3112.9%
java
3012.5%

Share — how many of the 240 jobs in the Application Support market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).

Top Application Support skills and tools 2026: SQL (mandatory — diagnostics through the DB), work with logs (ELK, Grafana Loki), Linux, monitoring (Zabbix, Prometheus + Grafana), scripting (Bash, Python), understanding of application architecture, APIs and integrations, sometimes queues (Kafka), incident management and ITIL; reading code — a strong advantage.

Common pairs: SQL + logs (the diagnostic core), Linux + monitoring, scripting + automation, incident management + SLA, understanding applications + reading code. Learning roadmap: SQL confidently → logs and diagnostics → Linux → application architecture (client-server, APIs, integrations) → monitoring → scripting (Bash, Python) → incident management (ITIL) → with an eye on growth — automation, clouds, IaC (a bridge to DevOps / SRE).

Chart data
Used together with — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
sql111
cloud80
itil69
python47
aws41
oracle39
azure37
servicenow33
service desk31
java30
itsm23
javascript20

How many Application Support jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior36
middle30
lead13
junior8
principal3

Career flow: (from L2/L3 tech support, sysadmins, testing) → Application Support → Senior Production Support Engineer → Lead, or transition into DevOps / SRE (the most frequent and lucrative), into systems analysis, QA, development, DBA.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Chart data
Demand by grade — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior36
middle30
lead13
junior8
principal3

Who hires the most for Application Support and how concentrated demand is among the largest companies.

Employers

Demand is spread across 182 employers. The largest accounts for 3.9%, the top ten for 18.4%; the remaining 81.6% is long tail.

largest 3.9%2nd–3rd 4.3%4th–10th 10.3%the rest 81.6%
sharevalue
top-13.9%
top-38.1%
top-1018.4%
long tail81.6%

⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier

Which company sites and job boards Zorky collects Application Support jobs from.

Where Zorky sees this market

Observed across 39 sources; the largest accounts for 17.9% — this market does not rest on a single channel.

Application Support vacancies: hh.ru («application support specialist» / «application support» / «production support» / «application support engineer»), Habr Career, getmatch, LinkedIn, Telegram (support and DevOps communities, vacancy channels). The largest source of vacancies — banks and fintech. At large tech companies similar work is often framed as SRE / DevOps.

Chart data
Where Zorky sees this market — Application Support. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites1510.6292
boardджоб-борды и агрегаторыjob boards & aggregators850.3542
telegramTelegramTelegram30.0125
communityсообщества и публичные профилиcommunity & public profiles10.0042

The newest Application Support jobs from company career sites.

Recent openings

All jobs →

Latest open Application Support jobs — most recent 10 positions with adequate description quality. NB: the role is often called «application support specialist» or «production support» — full list in our CRM or via the «see all» link below.

How this is measured
Vacancy
an open job that cleared the quality gate and lists at least two technologies
Observed candidate
a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
Matchable candidate
not counted yet
Window
jobs open at the moment the snapshot was built

About the data

  • Some breakdowns are hidden: their data coverage is not yet sufficient.
  • Statistics are shown only where the sample clears a quality gate.
  • A missing block does not mean a value of zero.

Breakdowns currently hidden: 8.

Direction: Support / SysAdmin

Related specializations

Inside Application Support: Application Support Specialist / Engineer (application support), Production Support Engineer (production support — a close synonym), Senior Application Support, Application Support Lead. Adjacent and career-linked roles — DevOps, SRE, systems analyst, QA. Comparison with other support specializations — in the bar below.

IT HelpdeskNetwork EngineerProduct SupportSystem AdministratorTechnical Support

Frequently asked questions

The most common questions about Application Support: pay, grades, skills and tools, Application Support vs Technical Support, what production support does, is SQL and reading code needed, remote, where to grow (DevOps / SRE), companies, how to start, Senior skills. Answers recompute automatically.

What skills and tools are most often required from Application Support?

Top skills: sql, itil, linux, cloud, python. SQL — mandatory and at a good level: diagnosis of problems through the database, checking and sometimes correcting data — the core of the work. Logs — confident reading, searching and analysis of application logs (tools ELK / Grafana Loki etc.); causes of outages are sought in logs. Linux — command line, work with production servers. Monitoring — Zabbix, Prometheus + Grafana; understanding metrics of applications and infrastructure. Scripting — Bash and Python for automating routine tasks and diagnostics. Understanding of application architecture — how the supported application is structured, its components, integrations, APIs; sometimes — message queues (Kafka). Incident management — ITIL methodology, work by SLA, prioritization, escalation. Reading code — a big advantage (understand what's happening in the application). Domain knowledge — understanding the subject area of supported systems (banking, ERP etc.). Soft skills: cool-headedness in incidents (the work of critical systems depends on Application Support), systems and diagnostic thinking, accuracy, communication with development and business. The main thing: Application Support is a technical role; valued are those who can quickly dig down to the cause of an outage in production and have a command of SQL, logs and understanding of how applications are structured.

Application Support vs Technical Support — what's the difference?

Both roles are in support, but responsible for different things. Technical Support helps users and clients with their problems and questions — focus on people and their requests, organized by L1 / L2 / L3 levels (see /research/support/technical-support). Application Support is responsible for the applications themselves in production — focus on systems: monitors business applications, takes apart incidents, diagnoses outages, keeps critical systems running. Roughly: technical support — «helping people use the system», application support — «watching that the system itself works, and fixing it when it breaks». By technical depth: Application Support is noticeably more technical — this is work with production, SQL, logs, servers, application architecture; it's closer to engineering (DevOps / SRE) than to classic user support. By character: technical support has more communication with users; application support has more technical diagnostics and work with systems, often with production duty. On pay: Application Support is paid above basic tech support. Career flow: from technical support people more often grow gradually (through L3); Application Support itself is already a technical role with a direct exit to DevOps / SRE and systems analysis. In practice people often come into Application Support from L2/L3 tech support, having added technical depth.

What exactly does an Application Support — production support — specialist do?

Application Support (production support) ensures that business applications work in production stably and predictably. 1) Monitoring — watch the state of applications in production by metrics, dashboards, alerts; notice problems before the business notices. 2) Incident management — when an application behaves wrong (outage, errors, slowdown, unavailability), accept the incident, assess the impact and priority, start analysis. 3) Diagnosis — find the cause: log analysis, checking data in the database (SQL), metrics, state of servers and integrations; reproduce and localize the problem. 4) Resolution or escalation — eliminate the problem within one's competence (restart, data fix, workaround) or escalate to development with full context and priority. 5) Routine operations — perform planned procedures: running routine processes (for example, closing the operational day in a bank), participation in updates and releases, planned works. 6) Work by SLA — meet response and resolution times, especially for critical systems. 7) Interaction — with development (passing bugs, joint analysis), with infrastructure / DevOps, with business users. 8) Documentation of incidents and resolutions, populating the knowledge base, participation in postmortem. 9) Reliability improvement — at a mature level: suggest how to reduce the number of incidents. Key: Application Support is the «production front line»; how quickly business-critical systems are restored depends on the speed and quality of incident analysis. The role often works in shifts, providing coverage in the operating mode of the systems (often 24/7).

Does Application Support need SQL and the ability to read code?

SQL — yes, mandatory, and at a good working level: it's one of the core requirements of the role. Application Support constantly diagnoses problems through the database — look at the state of data, find an anomaly, check what and why went wrong, sometimes perform data correction by an agreed procedure. Without confident SQL you can't work in this role. Log reading — also a mandatory skill on par with SQL: causes of outages in production are sought in logs. Reading code — very desirable, but not always mandatory on entry: the ability to read the code of the supported application and understand what's happening in it greatly speeds up diagnostics and sharply raises the specialist's value; at Senior level this is essentially necessary. Application Support doesn't need to write production code — this isn't a developer role; but scripting (Bash, Python) for automating routine tasks and diagnostics is expected. Conclusion: Application Support is a technical role with a real entry threshold: SQL and logs — mandatory from day one, reading code and scripting — what distinguishes a strong specialist and needs to be built up. It is precisely this technical depth that makes Application Support both more paid than basic support and a good springboard into DevOps / SRE and engineering.

What share of jobs are remote?

Among jobs with a stated work format, 27% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.

Where to grow from Application Support?

Application Support is the most technical of support roles, and it gives a deep understanding of production, which opens strong career paths. 1) Inside support — Junior → Senior Production Support Engineer → Application Support Lead. 2) Into DevOps / SRE — the most natural and lucrative transition by income: Application Support already works with production, logs, monitoring, incidents, servers — this is a direct foundation for SRE (system reliability) and DevOps; having added automation, IaC, clouds, CI/CD, the specialist transitions into infrastructure engineering with a noticeable salary increase (see /research/devops). 3) Into systems analysis — deep understanding of how applications are structured and integrated makes Application Support a good candidate for systems analyst (see /research/analyst/systems-analyst). 4) Into QA — skills of reproducing problems, working with logs and SQL — a tester's base (see /research/qa). 5) Into development — for those who in support read a lot of code and in parallel learned to program. 6) Into DBA — for those captivated by database work (see /research/data/dba). Main advice: Application Support is a technical role with good prospects; the most frequent and lucrative growth vector is into DevOps / SRE, and from the very beginning it's worth purposefully pumping automation, clouds and infrastructure skills.

How to start an Application Support career in 2026?

Application Support is a technical role; people come into it from L2/L3 tech support, system administration, testing, sometimes after specialized training. Roadmap: 1) SQL — master confidently: queries, joins, aggregations, understanding of data structure; for Application Support this is mandatory skill #1. 2) Logs and diagnostics — learn to read and analyze application logs, approach the search for the cause of an outage systematically. 3) Linux — command line, work with servers. 4) Understanding of application architecture — how web and enterprise applications are structured, client-server, APIs, integrations, databases, queues. 5) Monitoring — Zabbix, Prometheus + Grafana; understanding of metrics. 6) Scripting — basics of Bash and Python for automation. 7) Incident management — ITIL, SLA, processes. 8) Domain knowledge — if you're aiming for a bank, it's useful to understand the banking subject area (this is a frequent hiring segment). 9) With an eye on growth — immediately master what leads into DevOps / SRE (automation, clouds, basics of IaC). Entry paths: transition from L2/L3 tech support or system administration with adding SQL and production skills; Junior Application Support at a bank or with an integrator. Resources: materials on SQL, Linux, monitoring, ITIL; courses on application support and DevOps. A good start — Junior position in the banking or enterprise segment with an eye on further growth into DevOps / SRE.

What skills does a Senior Application Support specialist need?

Senior Application / Production Support Engineer is responsible for the stability of critical applications in production and rapid analysis of complex incidents. Expert diagnostics: quickly find the cause of a complex, non-obvious outage in production — through logs, SQL, metrics, integration analysis; systems diagnostic thinking under pressure. SQL: expert level — complex queries for diagnostics, understanding of performance, careful work with production data. Logs and observability: fluent work with logging and monitoring systems, ability to set up useful alerts and dashboards. Deep understanding of applications: know the architecture of supported systems, their components, integrations, bottlenecks; read the application code. Incident management: lead critical incidents, coordinate analysis, make decisions under pressure, run postmortems and prevent repeats. Linux and infrastructure: confident work with production servers, understanding of infrastructure. Automation: scripting (Bash, Python), automation of routine operations and diagnostics — reduces routine and the risk of errors. Work with development: properly escalate with full context, participate in analysis, influence application reliability. Proactivity: not only fix incidents, but also suggest how to reduce their number — this brings the role closer to SRE. For Lead: managing the support team, processes, SLA, duties, training. Domain expertise: deep knowledge of the subject area (banking etc.). English — for documentation. The main value of a Senior — quickly bring back into operation a business-critical system and make it break less often; from this level a direct transition into SRE and DevOps is open.

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.