Will AI Replace Desktop Support Technician Jobs?

Also known as: 2nd Line Support·Computer Technician·Desktop Engineer·Desktop Support·IT·Second Line Analyst·Second Line Support

Mid-Level IT Support Live Tracked This assessment is actively monitored and updated as AI capabilities change.
YELLOW (Urgent)
0.0
/100
Score at a Glance
Overall
0.0 /100
TRANSFORMING
Task ResistanceHow resistant daily tasks are to AI automation. 5.0 = fully human, 1.0 = fully automatable.
0/5
EvidenceReal-world market signals: job postings, wages, company actions, expert consensus. Range -10 to +10.
0/10
Barriers to AIStructural barriers preventing AI replacement: licensing, physical presence, unions, liability, culture.
0/10
Protective PrinciplesHuman-only factors: physical presence, deep interpersonal connection, moral judgment.
0/9
AI GrowthDoes AI adoption create more demand for this role? 2 = strong boost, 0 = neutral, negative = shrinking.
0/2
Score Composition 26.3/100
Task Resistance (50%) Evidence (20%) Barriers (15%) Protective (10%) AI Growth (5%)
Where This Role Sits
0 — At Risk 100 — Protected
Desktop Support Technician (Mid-Level): 26.3

This role is being transformed by AI. The assessment below shows what's at risk — and what to do about it.

Role transforming. Physical, on-site hardware work provides meaningful protection that pure help desk lacks, but the remote-solvable portion of the role (25-45% of tasks) is automating now. Adapt within 3-5 years to stay relevant.

If you learn to build AI for this role: ▼ stays Yellow See full AI-Driven analysis ↓

Done by building your own AI agents and tools instead of running them by hand, this role changes shape. One person who builds delivers what a team used to — hired for the judgement and the solutions, not the tooling.

Role Definition

FieldValue
Job TitleDesktop Support Technician
Seniority LevelMid-Level
Primary FunctionOn-site, hands-on IT support. Deploys, configures, and repairs workstations, laptops, peripherals, and local network equipment at users' desks. Images and provisions new machines, replaces failing hardware (RAM, drives, screens), troubleshoots connectivity issues requiring physical access, and provides face-to-face walk-up support. Handles Tier 1.5-2 complexity: issues that require being physically present with the device.
What This Role Is NOTNOT a Help Desk Technician (remote Tier 1 phone/chat/email — AIJRI 7.8, Red). NOT a Systems Administrator (server/infrastructure management — AIJRI 13.7, Red). NOT an IT Operations Manager (team leadership, ITSM ownership). The defining feature is physical presence with end-user hardware.
Typical Experience2-5 years. CompTIA A+, sometimes Network+. ITIL Foundation common. Hands-on hardware experience is the primary qualification, not certifications.

Seniority note: Entry-level desktop support (0-1 years, supervised, script-following) would score closer to Red (~20). Senior desktop support / field engineer (5+ years, independent diagnosis, some infrastructure work) would score higher Yellow (~35-40) as their work overlaps with L2/L3 troubleshooting and infrastructure tasks.


Protective Principles + AI Growth Correlation

Human-Only Factors
Embodied Physicality
Significant physical presence
Deep Interpersonal Connection
Some human interaction
Moral Judgment
No moral judgment needed
AI Effect on Demand
AI slightly reduces jobs
Protective Total: 3/9
PrincipleScore (0-3)Rationale
Embodied Physicality2Core to role. Physically at users' desks: swapping hardware, re-cabling, imaging machines, configuring docking stations. Semi-structured office environments — more predictable than field work (electrician) but still requires hands-on dexterity and physical presence. 10-15 year protection.
Deep Interpersonal Connection1Regular face-to-face interaction with end users. Walk-up support requires patience and communication, but interactions are transactional, not trust-based. Users prefer in-person help over chatbots, but this is preference, not deep relational value.
Goal-Setting & Moral Judgment0Follows established procedures, escalation paths, and deployment standards. Does not set IT strategy or make ethical decisions. Independent troubleshooting judgment exists but within defined technical boundaries.
Protective Total3/9
AI Growth Correlation-1AI reduces demand for the remote-solvable portion of the work (software installs, ticket admin) but does not directly displace hands-on hardware tasks. Relationship is weakly negative — more AI means fewer tickets reaching a human, but physical device lifecycle management persists.

Quick screen result: Protective 3/9 AND Correlation -1 = Likely Yellow Zone (proceed to quantify).


Task Decomposition (Agentic AI Scoring)

Work Impact Breakdown
25%
75%
Displaced Augmented Not Involved
Hardware troubleshooting and repair on-site
25%
2/5 Augmented
Workstation setup, imaging, and deployment
20%
3/5 Augmented
Software installation and configuration
15%
4/5 Displaced
Peripheral setup (printers, monitors, docking stations)
10%
2/5 Augmented
Ticket logging, documentation, and admin
10%
5/5 Displaced
Network connectivity troubleshooting on-site
10%
3/5 Augmented
End-user communication, training, walk-up support
10%
2/5 Augmented
TaskTime %Score (1-5)WeightedAug/DispRationale
Hardware troubleshooting and repair on-site25%20.50AUGMENTATIONDiagnosing and replacing failing components (RAM, SSDs, screens, batteries), testing hardware, working in cramped desk environments. AI diagnostics can identify likely faults, but the physical repair requires human hands. Moravec's Paradox applies.
Workstation setup, imaging, and deployment20%30.60AUGMENTATIONPhysically unboxing, cabling, imaging, configuring, and deploying new machines at user desks. MDM/SCCM/Intune automates the software provisioning, but physical setup, cable management, and desk configuration require on-site presence. AI handles the imaging pipeline; human handles the physical deployment.
Software installation and configuration15%40.60DISPLACEMENTRemote software deployment via MDM, Intune, and SCCM already handles most installs without physical presence. AI agents can push configurations, resolve install failures, and manage licensing. Desktop support only intervenes for edge cases requiring physical access.
Peripheral setup (printers, monitors, docking stations)10%20.20AUGMENTATIONPhysically connecting, mounting, and configuring peripherals. Printer jams, monitor arm installation, docking station troubleshooting. AI cannot reach behind desks or mount hardware.
Ticket logging, documentation, and admin10%50.50DISPLACEMENTAI generates tickets and documentation as byproduct of automated workflows. Asset management databases auto-populate from MDM. The administrative overhead of desktop support is automating rapidly.
Network connectivity troubleshooting on-site10%30.30AUGMENTATIONDiagnosing network issues that require physical access — checking patch cables, testing wall jacks, verifying switch port assignments, Wi-Fi site survey. AIOps tools diagnose remotely but cannot replace physical cable testing or hardware swaps.
End-user communication, training, walk-up support10%20.20AUGMENTATIONFace-to-face guidance for users struggling with new equipment or workflows. Walk-up bar / tech bar model. Users strongly prefer in-person help for hardware-related issues. Klarna effect: AI-only support degrades satisfaction.
Total100%2.90

Task Resistance Score: 6.00 - 2.90 = 3.10/5.0

Displacement/Augmentation split: 25% displacement, 75% augmentation, 0% not involved.

Reinstatement check (Acemoglu): Moderate new task creation. "AI tool administrator" tasks are emerging — configuring MDM policies, tuning self-healing endpoints, managing automated deployment pipelines. Desktop support techs who learn these tools gain new responsibilities. The role is shifting from "fix what's broken" to "manage the automated systems that fix what's broken, and handle what they can't." Physical device lifecycle management (procurement, deployment, decommission, e-waste) remains human-led and is growing as device fleets expand.


Evidence Score

Market Signal Balance
-4/10
Negative
Positive
Job Posting Trends
-1
Company Actions
-1
Wage Trends
-1
AI Tool Maturity
0
Expert Consensus
-1
DimensionScore (-2 to 2)Evidence
Job Posting Trends-1BLS projects Computer User Support Specialists (15-1232) at +6% growth (2023-2033) aggregate, but this masks seniority divergence. Pure "Desktop Support Technician" postings declining 5-15% as companies consolidate into broader "IT Support Engineer" or "Endpoint Engineer" titles. The title is shrinking; the physical work is not.
Company Actions-1Companies restructuring IT support tiers. Palo Alto Networks cut remote IT support 50% but retained on-site hardware staff. ServiceNow, Moveworks deployments reduce ticket volume reaching desktop techs but do not eliminate hardware lifecycle work. Some consolidation of desktop support into broader L2 roles.
Wage Trends-1Glassdoor median desktop support: $55K-$68K. Stagnant in real terms — tracking inflation but not outpacing it. Compare to cloud engineers ($118K-$148K) growing 5-10% YoY. Desktop support wages are not declining, but they are not keeping pace with specialist IT roles.
AI Tool Maturity0Remote management tools (Intune, SCCM, Jamf) and self-healing endpoints (Tanium, Nexthink) are production-ready for the software layer. But no viable AI tool exists for the physical tasks — hardware swaps, cable management, peripheral setup, on-site diagnostics. The 75% of the role that requires physical presence has no AI replacement. Tools augment but do not replace the core physical work.
Expert Consensus-1Industry consensus: desktop support is transforming, not disappearing. Ecasys (2026): "AI handles repetitive, low-complexity tasks. It shifts human focus toward complex troubleshooting, strategy, and AI system management. The role evolves — it doesn't disappear." Gartner predicts 60% of large enterprises adopt AIOps self-healing by 2026, reducing ticket volume but not eliminating physical support needs.
Total-4

Barrier Assessment

Structural Barriers to AI
Moderate 3/10
Regulatory
0/2
Physical
1/2
Union Power
0/2
Liability
1/2
Cultural
1/2

Reframed question: What prevents AI execution even when programmatically possible?

BarrierScore (0-2)Rationale
Regulatory/Licensing0No licensing required. CompTIA A+ is voluntary. No regulation mandates human involvement in desktop hardware support.
Physical Presence1Physical presence required but in semi-structured, predictable office environments. More protected than remote help desk (0) but less protected than electricians working in unstructured environments (2). Robotics not viable for office desk-side support — the economics and dexterity requirements don't justify it. 10-15 year physical barrier.
Union/Collective Bargaining0Overwhelmingly non-unionised in private sector. Some public sector / government desktop support roles have union protection, but this is the exception.
Liability/Accountability1Moderate. Misconfigured hardware can cause data loss or security incidents. Physical damage to equipment during repair creates some liability. Not criminal liability, but organisational accountability for hardware assets and data security is non-trivial.
Cultural/Ethical1Users strongly prefer in-person support for hardware issues. Walk-up tech bars (Apple Genius Bar model) demonstrate cultural preference for face-to-face hardware support. Less than 10% of workers prefer chatbot IT support (CNBC). But this is preference, not prohibition.
Total3/10

AI Growth Correlation Check

Confirmed at -1 (Weak Negative). AI adoption reduces the volume of tickets that require desktop support intervention — self-service portals resolve password resets and software issues before they reach a technician. But the physical device lifecycle (procurement, deployment, repair, decommission) is independent of AI adoption. More AI tools in the enterprise means more endpoints to manage, partially offsetting the ticket reduction. The relationship is weakly negative, not strongly negative like pure L1 help desk (-2). Desktop support does not exist BECAUSE of AI, but it is not directly displaced by AI either.


JobZone Composite Score (AIJRI)

Score Waterfall
26.3/100
Task Resistance
+31.0pts
Evidence
-8.0pts
Barriers
+4.5pts
Protective
+3.3pts
AI Growth
-2.5pts
Total
26.3
InputValue
Task Resistance Score3.10/5.0
Evidence Modifier1.0 + (-4 x 0.04) = 0.84
Barrier Modifier1.0 + (3 x 0.02) = 1.06
Growth Modifier1.0 + (-1 x 0.05) = 0.95

Raw: 3.10 x 0.84 x 1.06 x 0.95 = 2.6222

JobZone Score: (2.6222 - 0.54) / 7.93 x 100 = 26.3/100

Zone: YELLOW (Green >=48, Yellow 25-47, Red <25)

Sub-Label Determination

MetricValue
% of task time scoring 3+55%
AI Growth Correlation-1
Sub-labelYellow (Urgent) — AIJRI 25-47 AND >=40% of task time scores 3+

Assessor override: None — formula score accepted. The 26.3 score sits 1.3 points above the Red/Yellow boundary, which is borderline. However, the physical presence protection (75% augmentation, only 25% displacement) is genuine and durable. The formula correctly captures that this role is transforming, not being displaced. No adjustment warranted.


Assessor Commentary

Score vs Reality Check

The 26.3 score is borderline — 1.3 points above the Red zone boundary. This reflects the genuine tension in the role: the physical tasks are well-protected (task resistance 3.10 is solid), but the market is consolidating desktop support into broader IT roles, and the remote-solvable tasks (25% of time) are automating. The score would drop to Red if evidence worsened by one point (e.g., if major employers began cutting on-site hardware staff). The physical presence barrier is doing meaningful work here — without it, this role would score closer to Help Desk Technician (7.8). The barrier is real and durable for 10-15 years, but it is protecting a role whose scope is shrinking.

What the Numbers Don't Capture

  • Title rotation is the dominant dynamic. "Desktop Support Technician" as a standalone title is declining. The work is migrating to "Endpoint Engineer," "IT Support Engineer," or "Field Services Technician" — titles that bundle physical desktop work with L2 troubleshooting, MDM management, and automation skills. The physical work survives; the pure desktop support title does not.
  • Device fleet growth partially offsets automation. Enterprise device counts are growing (laptops, tablets, phones, IoT). More devices = more physical lifecycle management work, even as per-device ticket volume drops. This creates a floor under the role that pure software support roles lack.
  • The Apple Genius Bar model is expanding. Walk-up tech bars in corporate IT are growing. This model values the in-person, face-to-face support experience that AI cannot provide for hardware issues. Companies adopting this model are investing in desktop support, not cutting it.
  • Rate of improvement in remote management tools. Self-healing endpoints (Nexthink, Tanium, 1E) are improving rapidly, automating more of the software troubleshooting that desktop techs currently handle. Each improvement reduces the scope of work that requires physical presence.

Who Should Worry (and Who Shouldn't)

If you're a desktop support tech who only handles software issues — installing applications, configuring email, resetting passwords — and rarely touches physical hardware, you're doing help desk work with a desktop support title. Your role is automating at the same pace as Tier 1 help desk. The title won't protect you.

If you're the person who physically deploys machines, swaps hardware, manages the server room, and runs cabling — you have the physical presence protection that makes this role Yellow instead of Red. No AI agent can reach behind a desk to re-seat a cable or replace a laptop screen.

The single biggest factor: whether your daily work requires physical presence with hardware, or whether it could be done remotely. The remote-solvable desktop support tech is heading toward Red. The hands-on hardware tech with MDM and endpoint management skills is heading toward stable Yellow or even lower Green.


What This Means

The role in 2028: The standalone "Desktop Support Technician" title will be less common. Surviving roles will be "Endpoint Engineers" or "Field Services Technicians" who combine physical hardware support with MDM management, automated deployment pipelines, and self-healing endpoint administration. The physical deployment, repair, and decommission work persists — but the person doing it will need broader technical skills than today.

Survival strategy:

  1. Master endpoint management platforms. Intune, SCCM, Jamf, and Workspace ONE are the tools that are automating the software side of your job. Become the person who manages these platforms, not the person they replace. Microsoft 365 Certified: Endpoint Administrator is the key certification.
  2. Build toward L2/L3 skills. Independent diagnosis, root cause analysis, and infrastructure troubleshooting are what separate the surviving role from the automated one. Network+, Azure fundamentals, and hands-on server experience bridge the gap.
  3. Lean into the physical. Hardware lifecycle management, asset procurement, e-waste compliance, and physical site infrastructure are growing as device fleets expand. These skills have zero AI displacement risk and increasing organisational value.

Where to look next. If you're considering a career shift, these Green Zone roles share transferable skills with this role:

  • Data Center Technician (AIJRI 48.1) — Physical hardware skills, cabling, and infrastructure management transfer directly to data center operations
  • Telecom Equipment Installer (AIJRI 55.0) — Hands-on hardware installation, troubleshooting, and physical site work are core to both roles
  • Computer and Information Systems Manager (AIJRI 62.7) — IT operations knowledge and end-user support experience provide a foundation for IT management with additional leadership development

Browse all scored roles at jobzonerisk.com to find the right fit for your skills and interests.

Timeline: 3-5 years for title consolidation. The physical work persists for 10-15+ years, but the standalone "Desktop Support Technician" title will be absorbed into broader endpoint engineering and field services roles by 2029-2031.


AI-Driven Variant secondary lens

Meet the AI-Driven Desktop Support Technician

What "AI-driven" means
✍️
By hand (today)
You do the work yourself, line by line
🛠️
AI-driven
You build AI to do it, then review & direct it

You become the person who creates and checks the solution — not the one typing it out.

Today vs the AI-Driven outlook
26.3
Yellow
Today
▼ Safer if you build
stays Yellow
If you build AI for it
▲ Transforms
The new role

Narrow but real: you build the imaging-and-deployment pipeline that provisions new machines, the self-healing endpoint rules (Intune, Tanium, Nexthink) that fix common faults before anyone raises a ticket, and the automation that logs and closes routine tickets. That frees your hands for the work AI can't touch: the physical hardware repair, on-site deploy, cabling and walk-up support behind the desk. It's a smaller build surface than most tech jobs — the physical core stays yours — so it lifts you part-way, not all the way.

Will AI replace this job — and does going AI-driven save it?

Only a little. Most of this job is physical — swapping hardware, deploying machines, sorting cables, walk-up help — and AI can't reach behind a desk. Building automation for the software slice lifts you, but it leaves you better, not safe.

The catch: the standalone desktop-support title is folding into broader Endpoint Engineer and Field Services roles. On what's happening today, highly likely that narrows — so ride the automation skills up into one of those rather than stay in the shrinking title. This lifts the person who adapts; it doesn't add seats.

This is what the AI Master's trains you to become.
The AI-Driven Desktop Support Technician above isn't a different career — it's this one, done by the person who builds the AI solutions. The StationX AI Master's is where you learn to build real, secure cyber security solutions with AI, and walk out the engineer teams fight to hire.
Train for the AI-Driven Role → Apply to the AI Master's

Transition Path: Desktop Support Technician (Mid-Level)

The easiest move is becoming the AI-Driven version of your own role — or transition sideways into a green-zone role. Click any card to see the breakdown.

↑ Level up in place

AI-Driven Desktop Support Technician

YELLOW 31.4
+5.1 pts · same role
Your Role

Desktop Support Technician (Mid-Level)

YELLOW (Urgent)
26.3/100
+41.0
points gained
Target Role

Data Center Technician (Mid-Level)

GREEN (Transforming)
67.3/100

Desktop Support Technician (Mid-Level)

25%
75%
Displacement Augmentation

Data Center Technician (Mid-Level)

5%
35%
60%
Displacement Augmentation Not Involved

Tasks You Lose

2 tasks facing AI displacement

15%Software installation and configuration
10%Ticket logging, documentation, and admin

Tasks You Gain

3 tasks AI-augmented

20%Hardware troubleshooting and diagnostics
10%Environmental monitoring and facilities coordination
5%Firmware updates and configuration tasks

AI-Proof Tasks

4 tasks not impacted by AI

25%Hardware racking/stacking and physical installation
15%Hot swaps and break/fix repairs
10%Cable management and infrastructure cabling
10%GPU cluster deployment and liquid cooling

Transition Summary

Moving from Desktop Support Technician (Mid-Level) to Data Center Technician (Mid-Level) shifts your task profile from 25% displaced down to 5% displaced. You gain 35% augmented tasks where AI helps rather than replaces, plus 60% of work that AI cannot touch at all. JobZone score goes from 26.3 to 67.3.

Want to compare with a role not listed here?

Full Comparison Tool

Green Zone Roles You Could Move Into

Data Center Technician (Mid-Level)

GREEN (Transforming) 67.3/100

Physical hands-on server racking, cable management, hardware diagnostics, and GPU cluster deployment in data center facilities cannot be performed by AI or robots -- and AI infrastructure buildout is actively driving unprecedented demand for this role. Safe for 5+ years.

Also known as data centre engineer data centre technician

Computer and Information Systems Manager (Mid-to-Senior)

GREEN (Transforming) 62.7/100

Strategic IT leadership survives the automation wave because accountability, business judgment, and C-suite relationships can't be delegated to AI. The operational work beneath this role is automating rapidly, but the strategic layer — setting direction, owning budgets, aligning technology with business goals — persists. Safe for 5+ years if you own the strategy, not just the operations.

Also known as ict manager it manager

Self-Service Kiosk Technician (Mid-Level)

GREEN (Transforming) 49.7/100

The hands-on repair work is physically protected by Moravec's Paradox, and the kiosk equipment base is expanding across retail, hospitality, healthcare, and transport. AI augments diagnostics but cannot replace field repair. Safe for 5+ years with growing demand.

Also known as kiosk engineer kiosk repair technician

AI Solutions Architect (Mid-Senior)

GREEN (Accelerated) 71.3/100

The AI Solutions Architect role exists because of AI growth and is recursively protected — more AI adoption creates more demand for enterprise AI architecture, technology selection, and governance. Demand is acute and accelerating. 10+ year horizon.

Sources


▸ AI-Driven Variant — Derivation (auditable, internal methodology)

AI-Driven Variant — Derivation (auditable)

Verdict: FORK → transforms, down-but-still-exposed (stays Yellow). Internal score: 31.4 / 100 (YELLOW) vs base 26.3 — direction ▼ down-if-you-adapt, zone stays Yellow, magnitude material. Not boundary-fragile (primary outside 45–51 and no single-axis re-read crosses 48). Amalgamation note: the AI-driven uplift path leads UP into a broader Endpoint Engineer / Field Services role — but the role is NOT displaced, because the irreducible physical work keeps a coherent job at this seniority.

Why not displaced, and why not compresses: Unlike SOC Tier 1 (the rote middle), ~75% of this role is physical work AI cannot do or be directed to do (hardware repair, on-site deploy, peripherals, on-site network, walk-up support). That physical core is a genuine, durable floor — the base scores the role Yellow on physical-presence protection, not on AI usage — so a coherent role survives at this level. It is not compresses (Pattern 5) because the surviving physical work is not commoditising: wages are stagnant rather than falling, device-fleet growth adds hands-on demand ("a floor under the role"), and "one does what three did" is not evidenced for per-device hardware work. The named title-rotation pressure is amalgamation (the title folds upward into Endpoint Engineer), not wage-collapse of the surviving core.

Step A — Re-decomposed task table (the two DISPLACED tasks shrink within the ±10pp cap, justified by named deployed tools — Intune/SCCM/Jamf for software/imaging, ServiceNow/Moveworks for ticketing; freed time flows to the irreducible physical + the new build task; ±10pp respected on every row):

TaskAI-driven time %ScoreBucket
Hardware troubleshooting & repair on-site25%2ENHANCED
Workstation setup, imaging & deployment20%3ENHANCED
Software installation & configuration (Intune/SCCM)7%4DISPLACED
Peripheral setup (printers, monitors, docks)10%2UNCHANGED
Ticket logging, documentation & admin (ServiceNow/Moveworks)3%5DISPLACED
Network connectivity troubleshooting on-site15%3ENHANCED
End-user communication, training, walk-up support15%2UNCHANGED
Build & manage MDM / self-healing endpoint automation5%2ENHANCED

Enhanced share: 90% (ENHANCED + UNCHANGED-irreducible time; the two DISPLACED rows = 10%). Task Resistance = 6.00 − 2.58 = 3.42.

Step B — Coherent-Role Test: PASS to a coherent role at this level — the physical hardware/deploy/walk-up core is irreducible and even growing with device fleets, so what survives is a real, hireable mid-level job, not thin glue absorbed up. The AI-driven uplift is genuine but partial (it only touches the ~25% software/admin slice), which is exactly why it lands stays-Yellow, not down-to-Green.

Step C — Inputs as DELTAS FROM BASE (base E=-4, B=3, G=-1):

  • Evidence: base -4 → -3 (+1). Named: the reinstatement of "AI tool administrator / Endpoint Engineer" tasks (base Step-2 reinstatement note) plus Ecasys (2026) — "the role evolves, it doesn't disappear" — gives a one-point lift for the adapter who automates the fleet. AI-driven-specific durability data is thin, so the move is capped at +1.
  • Barriers: base 3 → 3 (delta 0). Physical-presence and liability barriers do not rise from directing AI, and verifying jagged AI output here is low-stakes (a bad MDM push is reversible, not a breach or court-inadmissible error). No upward move.
  • Growth: base -1 → -1 (delta 0). Directing AI does not make this role grow because of AI; the weakly-negative correlation (AI removes tickets) persists. +1 would be unjustified and would contradict the base.

<!-- audit: E=-3 B=3 G=-1 deltaEvidence=E:Ecasys -->

Step D — Primary composite (Python, no ±5 override): TR 3.42 × E-mod(-3 → 0.88) × B-mod(3 → 1.06) × G-mod(-1 → 0.95) → (raw − 0.54) / 7.93 × 100 = 31.4 / 100 → YELLOW.

Step E — Per-axis conservative re-read: TR → 30.1 · E → 29.7 · B → 30.7 · G → 29.4 — all four stay Yellow, none crosses 48, and the primary 31.4 is well outside the 45–51 auto-band → NOT boundary-fragile. Published as a direction + zone-movement scenario: ▼ down-if-you-adapt · stays Yellow · material. Survives and improves (+5.1 over base 26.3) but does not reach safety — the honest "better, not safe; the population narrows as the title folds upward."

Concept gate (4 tests) — all pass. (1) Subject-vs-method: the verdict rests on directing AI changing the daily software/admin slice (a hand-operator who learns to automate the fleet IS partly transformed) — not on "it's a tech role." (2) Seniority-shortcut: not invoked; rests on the physical floor + partial build uplift. (3) Base-contradiction: base YELLOW / Growth -1 / "transforming" is fully consistent with transforms-stays-Yellow holding Growth at -1. (4) Spine: strip "uses AI / faster" and a survival reason remains — the irreducible physical work — and the compression check was run first and came back negative on the surviving core (amalgamation, not commoditisation).

Impact dimensions: Leverage MED (only the software/admin slice is buildable; the physical core caps it). Headcount indeterminate (fleet growth adds hands-on demand; automation removes software tickets — they roughly offset). Compounding MED (deployment/self-healing automation reuses, but much hardware work is one-off per device). Verify-burden LOW (errors are cheap and reversible, so the human is not strongly protected by verification here). Skill-ceiling rising — the tech who automates the fleet climbs toward endpoint engineering; the software-only tech is left behind.

Useful Resources

Get updates on Desktop Support Technician (Mid-Level)

This assessment is live-tracked. We'll notify you when the score changes or new AI developments affect this role.

No spam. Unsubscribe anytime.

Personal AI Risk Assessment Report

What's your AI risk score?

This is the general score for Desktop Support Technician (Mid-Level). Get a personal score based on your specific experience, skills, and career path.

No spam. We'll only email you if we build it.