AI is not removing the first IT job. It is removing the scripted version of it. If your plan is to start in a role where you read a runbook, ask three qualification questions and escalate, that role is shrinking faster than any training course admits. The first IT job that is growing is the one where you explain a strange result, connect two systems that do not normally talk, and make a reasonable call under uncertainty. Train for that one.
Who this is for
- Career changers choosing their first tech role and wondering whether AI has already closed the door.
- People in scripted first-line support who feel the seat getting tighter but are not sure what to move towards.
- Course sellers and bootcamps still marketing the old entry-level path.
What is actually changing
First-line support has been compressing for fifteen years. Self-service portals, better knowledge bases and chatbots were already eating the easy cases. Large language models are now eating the repeatable language work: drafting responses, summarising tickets, suggesting the next step from a runbook, rewriting a workaround in simpler terms.
This is not a prediction for 2030. It is visible now in outsourced contact centres, in the support tiers of SaaS companies, and anywhere the job is to read a script and either resolve or escalate. The role is not disappearing overnight, but the direction is clear enough to plan around. New entrants who target pure scripted L1 should assume the seat gets smaller every year.
The part that remains is the part the bot cannot do. The ticket that does not match any known pattern. The user who cannot explain the problem. The system where the logs say one thing and the user says another. The decision whether to reset a production account at 6pm on a Friday. These require judgement, context and ownership.
What people get wrong
The first mistake is confusing "AI can do part of my job" with "AI will take my job." AI can handle the repeatable part. It cannot handle the whole ticket. Across mainstream IT work, the boring slice compresses and the judgement slice expands. The total amount of useful work does not fall; it shifts up the value chain.
The second mistake is the "learn AI to survive" panic. Most "AI engineer" roles require the systems background that career changers do not yet have. Skipping to the fashionable title without the foundational work is a worse bet than deepening the operational base. The durable AI-related paths are mostly underneath the headline: model serving, data engineering, GPU networking, MLOps. Those are not first jobs.
The third mistake is thinking the cert still opens the same door. Certs still matter, but the door they open is changing. A cert that proves you can follow a process matters less when the process is automated. A cert plus evidence that you can handle ambiguity matters more.
What to do instead
Pick a first role that puts you next to uncertainty. A small internal IT team where you touch everything. A managed service provider with varied clients. A T2 support desk that sees the tickets the T1 bot could not close. A field or desktop role with physical access and real users. The common thread is that you see situations the knowledge base does not cover.
Build two skills in parallel alongside any cert. The first is diagnostic writing: can you describe a fault, what you have tried and what you still do not know in three sentences? The second is tool fluency without tool worship: use AI to draft responses and explain concepts, but never let it make the decision you will be asked to defend.
Treat the first role as a twelve-to-eighteen-month apprenticeship, not a destination. Plan the sideways move from day one: into infrastructure, security, cloud support, networking or identity. The role that is shrinking is the one you stay in.
When to walk away from the plan
If your only realistic local option is pure scripted L1 and you cannot relocate, take it. But treat it as a strict twelve-month foothold, not a career. If a course is selling you a "junior AI engineer" outcome without a coding or systems background, that is a different kind of shrinking seat.
Where this connects on POST
For the broader argument on why AI shrinks specific IT roles rather than all of them, read AI will not delete IT. For why IT support is still the right starting point for most people, read Why most people should start in IT support. The pathways page tags each route with an AI-resilience score based on the work itself.