Will AI take the job I'm studying for?

No, but it will change it, and the bar to get in will be higher.

If you're taking IT, CS, or a related course and feeling unsure about the future because of AI, you're not alone. This page collects the questions students ask most, with honest and practical answers.

The short version

What's actually changing

The part of the field most exposed to AI is routine, entry-level work: writing boilerplate code, basic testing, simple bug fixes, Level 1 tech support, data entry, and templated documentation. Entry-level hiring for junior developers has tightened in many markets, and AI is part of the reason. In the Philippines, the IT-BPM sector is also feeling pressure on repetitive, script-driven roles. "Learn to code and you'll get hired" is weaker advice than it was five years ago.

What isn't going away

Someone still has to design systems, decide what to build, connect AI to real business processes, keep infrastructure running, secure it, and take responsibility when it breaks at 3 AM. AI makes a good engineer faster. It doesn't make a weak engineer good, and it doesn't take accountability. Companies still need people who can tell whether AI output is correct, and you can only do that if you understand the fundamentals.

Take infrastructure and operations work as an example. AI helps with scripts, log analysis, and documentation, but someone still has to understand Linux, networking, storage, and incident response well enough to know when the AI is wrong. That judgment comes from real knowledge and experience.

What to do in your next four years

  1. Take the fundamentals seriously. Data structures, networking, operating systems, databases, and security are what let you check and direct AI instead of being replaced by it.
  2. Use AI tools heavily, but don't let them do your thinking. Be able to explain every line you submit. Graduates who use AI well and can still reason on their own will stand out.
  3. Lean toward areas with more resilience. Cloud and infrastructure, cybersecurity, data engineering, DevOps and SRE, and building AI-powered systems rather than competing with them.
  4. Build real things and get real experience. Personal projects on GitHub, internships, open source, and freelance work. A degree with no proof of skills will be a weak position by the time you graduate.
  5. Develop the human skills. Clear writing, explaining technical things to non-technical people, and working well on a team. These are harder to automate.

The honest bottom line

The field won't disappear, but the bar for entry will be higher. The easy, repetitive starting jobs will be fewer, and graduates who only did the minimum will struggle. Those who built strong fundamentals, specialized in something, and can show real work will still find good opportunities, possibly better ones, because each engineer can do more with AI behind them.

Your questions, answered

No questions match that search. Try a shorter word, or pick "All topics".