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.
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
| Period | New postings per week |
|---|---|
| 2026-06-01 | 4 |
| 2026-06-08 | 2 |
| 2026-06-15 | 10 |
| 2026-06-22 | 39 |
| 2026-06-29 | 36 |
| 2026-07-06 | 37 |
| 2026-07-13 | 70 |
| 2026-07-20 | 64 |
| 2026-07-27 | 38 |
| 2026-08-03 | 36 |
| 2026-08-10 | 24 |
| 2026-08-17 | 31 |
| 2026-08-24 | 36 |
| 2026-08-31 | 41 |
| 2026-09-07 | 37 |
| 2026-09-14 | 31 |
| 2026-09-21 | 75 |
| 2026-09-28 | 72 |
| 2026-10-05 | 53 |
| 2026-10-12 | 213 |
| 2026-10-19 | 103 |
| 2026-10-26 | 124 |
| 2026-11-02 | 109 |
| 2026-11-09 | 93 |
Active sources per week
Sources over the period: 105. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 4 |
| 2026-06-08 | 2 |
| 2026-06-15 | 7 |
| 2026-06-22 | 18 |
| 2026-06-29 | 18 |
| 2026-07-06 | 12 |
| 2026-07-13 | 24 |
| 2026-07-20 | 22 |
| 2026-07-27 | 20 |
| 2026-08-03 | 15 |
| 2026-08-10 | 14 |
| 2026-08-17 | 17 |
| 2026-08-24 | 19 |
| 2026-08-31 | 12 |
| 2026-09-07 | 20 |
| 2026-09-14 | 18 |
| 2026-09-21 | 24 |
| 2026-09-28 | 26 |
| 2026-10-05 | 22 |
| 2026-10-12 | 31 |
| 2026-10-19 | 36 |
| 2026-10-26 | 29 |
| 2026-11-02 | 30 |
| 2026-11-09 | 28 |
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
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 2 |
| Jun 15 | +4 | 10 |
| Jun 22 | +14 | 39 |
| Jun 29 | +9 | 36 |
| Jul 6 | +6 | 37 |
| Jul 13 | +10 | 70 |
| Jul 20 | +11 | 64 |
| Jul 27 | +8 | 38 |
| Aug 3 | +3 | 36 |
| Aug 10 | +2 | 24 |
| Aug 17 | +2 | 31 |
| Aug 24 | +3 | 36 |
| Sep 7 | +2 | 37 |
| Sep 14 | +1 | 31 |
| Sep 21 | +5 | 75 |
| Sep 28 | +1 | 72 |
| Oct 12 | +7 | 213 |
| Oct 19 | +5 | 103 |
| Oct 26 | +2 | 124 |
| Nov 2 | +3 | 109 |
| Nov 9 | +2 | 93 |
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
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 4 | 4 |
| 2026-06-08 | 2 | 2 |
| 2026-06-15 | 10 | 7 |
| 2026-06-22 | 39 | 18 |
| 2026-06-29 | 36 | 18 |
| 2026-07-06 | 37 | 12 |
| 2026-07-13 | 70 | 24 |
| 2026-07-20 | 64 | 22 |
| 2026-07-27 | 38 | 20 |
| 2026-08-03 | 36 | 15 |
| 2026-08-10 | 24 | 14 |
| 2026-08-17 | 31 | 17 |
| 2026-08-24 | 36 | 19 |
| 2026-08-31 | 41 | 12 |
| 2026-09-07 | 37 | 20 |
| 2026-09-14 | 31 | 18 |
| 2026-09-21 | 75 | 24 |
| 2026-09-28 | 72 | 26 |
| 2026-10-05 | 53 | 22 |
| 2026-10-12 | 213 | 31 |
| 2026-10-19 | 103 | 36 |
| 2026-10-26 | 124 | 29 |
| 2026-11-02 | 109 | 30 |
| 2026-11-09 | 93 | 28 |
Salaries over time
Median Application Support salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-10-19 | 6,128 | 10 |
| 2026-10-26 | 5,884 | 17 |
| 2026-11-02 | — | 7 |
| 2026-11-09 | 5,755 | 10 |
The series starts on Oct 19: there is no data before that.
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
| Week | Median |
|---|---|
| 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-19 | 6,128 |
| 2026-10-26 | 5,884 |
| 2026-11-02 | — |
| 2026-11-09 | 5,755 |
Remote work over time
Share of Application Support postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-22 | 18.8 |
| 2026-06-29 | 8 |
| 2026-07-06 | 47.1 |
| 2026-07-13 | 13.3 |
| 2026-07-20 | 52.9 |
| 2026-07-27 | 36.4 |
| 2026-08-03 | 9.7 |
| 2026-08-10 | 0 |
| 2026-08-17 | 16 |
| 2026-08-24 | 6.7 |
| 2026-08-31 | 5.7 |
| 2026-09-07 | 6.2 |
| 2026-09-14 | 13.6 |
| 2026-09-21 | 21.2 |
| 2026-09-28 | 29.6 |
| 2026-10-05 | 11.8 |
| 2026-10-12 | 30.2 |
| 2026-10-19 | 32.5 |
| 2026-10-26 | 23.2 |
| 2026-11-02 | 21.5 |
| 2026-11-09 | 10.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
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | 18.8 |
| 2026-06-29 | 8 |
| 2026-07-06 | 47.1 |
| 2026-07-13 | 13.3 |
| 2026-07-20 | 52.9 |
| 2026-07-27 | 36.4 |
| 2026-08-03 | 9.7 |
| 2026-08-10 | 0 |
| 2026-08-17 | 16 |
| 2026-08-24 | 6.7 |
| 2026-08-31 | 5.7 |
| 2026-09-07 | 6.2 |
| 2026-09-14 | 13.6 |
| 2026-09-21 | 21.2 |
| 2026-09-28 | 29.6 |
| 2026-10-05 | 11.8 |
| 2026-10-12 | 30.2 |
| 2026-10-19 | 32.5 |
| 2026-10-26 | 23.2 |
| 2026-11-02 | 21.5 |
| 2026-11-09 | 10.8 |
Technologies over time
How the share of Application Support postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | SQL | cloud | itil |
|---|---|---|---|
| 2026-09-21 | 24.4 | 24.4 | 7.3 |
| 2026-09-28 | 51.1 | 31.9 | 25.5 |
| 2026-10-05 | 48.3 | 13.8 | 34.5 |
| 2026-10-12 | 35.2 | 36.1 | 19.4 |
| 2026-10-19 | 30.7 | 33.3 | 24 |
| 2026-10-26 | 42.1 | 35.5 | 31.6 |
| 2026-11-02 | 53.8 | 25.6 | 26.9 |
| 2026-11-09 | 46.8 | 27.4 | 21 |
The series starts on Sep 21: there is no data before that.
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
| Week | SQL | cloud | itil | Python | AWS |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 24.4 | 24.4 | 7.3 | 7.3 | 4.9 |
| 2026-09-28 | 51.1 | 31.9 | 25.5 | 8.5 | 21.3 |
| 2026-10-05 | 48.3 | 13.8 | 34.5 | 24.1 | 3.4 |
| 2026-10-12 | 35.2 | 36.1 | 19.4 | 10.2 | 11.1 |
| 2026-10-19 | 30.7 | 33.3 | 24 | 20 | 18.7 |
| 2026-10-26 | 42.1 | 35.5 | 31.6 | 25 | 13.2 |
| 2026-11-02 | 53.8 | 25.6 | 26.9 | 16.7 | 14.1 |
| 2026-11-09 | 46.8 | 27.4 | 21 | 22.6 | 14.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
| Period | Poland | India | UK |
|---|---|---|---|
| 2026-06-22 | 45.7 | 5.7 | 2.9 |
| 2026-06-29 | 18.2 | 18.2 | 9.1 |
| 2026-07-06 | 6.9 | 6.9 | 6.9 |
| 2026-07-13 | 15.3 | 6.8 | 11.9 |
| 2026-07-20 | 33.9 | 7.1 | 5.4 |
| 2026-07-27 | 20 | 11.4 | 17.1 |
| 2026-08-03 | 18.8 | 15.6 | 37.5 |
| 2026-08-10 | 0 | 13.6 | 13.6 |
| 2026-08-17 | 3.7 | 11.1 | 7.4 |
| 2026-08-24 | 8.8 | 2.9 | 29.4 |
| 2026-08-31 | 8.1 | 16.2 | 35.1 |
| 2026-09-07 | 5.6 | 19.4 | 8.3 |
| 2026-09-14 | 3.6 | 14.3 | 17.9 |
| 2026-09-21 | 8.8 | 16.2 | 17.6 |
| 2026-09-28 | 27.4 | 11.3 | 6.5 |
| 2026-10-05 | 18.9 | 5.7 | 7.5 |
| 2026-10-12 | 6.4 | 10.8 | 7.6 |
| 2026-10-19 | 26.8 | 10.3 | 7.2 |
| 2026-10-26 | 8.1 | 17.1 | 9 |
| 2026-11-02 | 4.7 | 14.1 | 8.2 |
| 2026-11-09 | 10.8 | 14.5 | 10.8 |
The series starts on Jun 22: there is no data before that.
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
| Week | Poland | USA | India | UK | Australia |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | 45.7 | 11.4 | 5.7 | 2.9 | 0 |
| 2026-06-29 | 18.2 | 6.1 | 18.2 | 9.1 | 0 |
| 2026-07-06 | 6.9 | 10.3 | 6.9 | 6.9 | 34.5 |
| 2026-07-13 | 15.3 | 5.1 | 6.8 | 11.9 | 22 |
| 2026-07-20 | 33.9 | 10.7 | 7.1 | 5.4 | 19.6 |
| 2026-07-27 | 20 | 2.9 | 11.4 | 17.1 | 11.4 |
| 2026-08-03 | 18.8 | 9.4 | 15.6 | 37.5 | 3.1 |
| 2026-08-10 | 0 | 9.1 | 13.6 | 13.6 | 4.5 |
| 2026-08-17 | 3.7 | 18.5 | 11.1 | 7.4 | 11.1 |
| 2026-08-24 | 8.8 | 14.7 | 2.9 | 29.4 | 17.6 |
| 2026-08-31 | 8.1 | 13.5 | 16.2 | 35.1 | 13.5 |
| 2026-09-07 | 5.6 | 8.3 | 19.4 | 8.3 | 16.7 |
| 2026-09-14 | 3.6 | 3.6 | 14.3 | 17.9 | 25 |
| 2026-09-21 | 8.8 | 16.2 | 16.2 | 17.6 | 8.8 |
| 2026-09-28 | 27.4 | 9.7 | 11.3 | 6.5 | 11.3 |
| 2026-10-05 | 18.9 | 1.9 | 5.7 | 7.5 | 9.4 |
| 2026-10-12 | 6.4 | 15.9 | 10.8 | 7.6 | 3.2 |
| 2026-10-19 | 26.8 | 13.4 | 10.3 | 7.2 | 3.1 |
| 2026-10-26 | 8.1 | 14.4 | 17.1 | 9 | 13.5 |
| 2026-11-02 | 4.7 | 12.9 | 14.1 | 8.2 | 9.4 |
| 2026-11-09 | 10.8 | 20.5 | 14.5 | 10.8 | 7.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
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.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
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Application Support jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 240 |
| Open demand | 240 |
| 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
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 1 |
| $2–3k | 2 |
| $3–4k | 1 |
| $4–5k | 2 |
| $5–6k | 1 |
| $6–7k | 3 |
| $7–8k | 2 |
| $8–9k | 2 |
| $9–10k | 0 |
| $10–12k | 1 |
| $12–15k | 1 |
| $15–20k | 0 |
| $20k+ | 0 |
- 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
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 1 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 1 |
| $4–5k | 4,000 | 5,000 | 2 |
| $5–6k | 5,000 | 6,000 | 1 |
| $6–7k | 6,000 | 7,000 | 3 |
| $7–8k | 7,000 | 8,000 | 2 |
| $8–9k | 8,000 | 9,000 | 2 |
| $9–10k | 9,000 | 10,000 | 0 |
| $10–12k | 10,000 | 12,000 | 1 |
| $12–15k | 12,000 | 15,000 | 1 |
| $15–20k | 15,000 | 20,000 | 0 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open Application Support jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| India | 38 | 19.6% |
| Poland | 36 | 18.6% |
| United States | 28 | 14.4% |
| United Kingdom | 14 | 7.2% |
| Thailand | 10 | 5.2% |
| Singapore | 9 | 4.6% |
| Canada | 8 | 4.1% |
| Germany | 6 | 3.1% |
| Portugal | 5 | 2.6% |
| Hong Kong | 5 | 2.6% |
| Other countries | 35 | 18% |
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
| Country | Jobs |
|---|---|
| IN | 38 |
| PL | 36 |
| US | 28 |
| GB | 14 |
| TH | 10 |
| SG | 9 |
| CA | 8 |
| DE | 6 |
| PT | 5 |
| HK | 5 |
Which technologies are most often required in the same job as Application Support.
Used together with
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
| Name | Count |
|---|---|
| sql | 111 |
| cloud | 80 |
| itil | 69 |
| python | 47 |
| aws | 41 |
| oracle | 39 |
| azure | 37 |
| servicenow | 33 |
| service desk | 31 |
| java | 30 |
| itsm | 23 |
| javascript | 20 |
How many Application Support jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 36 |
| middle | 30 |
| lead | 13 |
| junior | 8 |
| principal | 3 |
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
| Level | Count |
|---|---|
| senior | 36 |
| middle | 30 |
| lead | 13 |
| junior | 8 |
| principal | 3 |
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.
| share | value |
|---|---|
| top-1 | 3.9% |
| top-3 | 8.1% |
| top-10 | 18.4% |
| long tail | 81.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
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 151 | 0.6292 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 85 | 0.3542 |
| telegram | Telegram | Telegram | 3 | 0.0125 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0042 |
The newest Application Support jobs from company career sites.
Recent openings
- Advisor, Software Development Engineering(Java Application Support)) · IN
- Level 1 Application Support Analyst · LK
- [BD] SAP FI Application Support Consultant · VN
- Lead Application Support Analyst (.NET / .NET Core / AMS / DevOps) · IN
- Application Support Analyst (Java / Spring Boot / AMS / DevOps) · IN
- Application Support Analyst (VN3323) · US
- Application Support Developer - Mid-Level (Ruby on Rails) | Middle | IC
- How can I switch from Application Support to DevOps with 8 months of experience?
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.
Adjacent markets
Application Support — the most technical role of the Support / SysAdmin direction, the «production front line». The main career exit — DevOps and SRE (/research/devops): production support — a direct bridge into reliability engineering. Borders systems analyst (/research/analyst/systems-analyst), QA (/research/qa), DBA (/research/data/dba). Career source — L2/L3 tech support. Comparison of support specializations — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
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.
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.