New to IT? The Skills That Matter in the AI Era, and the Order to Learn Them

Fifteen skills for anyone new to IT in the AI era, sorted into the floor, foundations, emerging skills and specialisations, with a first step for each.

Suthahar Jegatheesan By Suthahar Jegatheesan Published

Career 10 min read —views
Article banner. On the left, the eyebrow "New to AI" above the title "The skills that matter" and the line "Two job adverts, five years apart", with the MSDEVBUILD wordmark and the author name below. On the right, three stacked boxes joined by arrows: an amber box reading "A list of languages and frameworks", an arrow labelled "five years later" to a red box reading "AI tools, review, security, judgement", and an arrow labelled "how to get there" to a green box reading "Floor, foundations, then AI skills".

New AI skills sit on top of the old IT foundations, not instead of them. If you are new to IT, learn the floor first (programming, data structures, operating systems and networking), then the foundations (databases, APIs, security, cloud basics and communication), then add emerging AI skills such as context engineering, agents and AI evaluation. Specialise last.

Part 1 described what IT work looks like now and part 2 how to learn for it. This part is the list of what to learn, and in what order.

Two job adverts, five years apart

Imagine two adverts for the same graduate developer role at the same company, one from five years ago and one from this year. They are illustrative, but put together from the kind of wording you will see on any job board.

The older one is short. It asks for a degree, one or two named languages, a framework, “knowledge of SQL” and “good communication skills”. Mostly tools.

The newer one still asks for the degree, the language and SQL. Then it adds lines the old one never had. “Experience using AI coding assistants, and reviewing their output.” “Awareness of secure development practices.” “Able to explain technical decisions to non-technical colleagues.” “Comfortable writing tests and working with CI pipelines.”

Nothing was removed. What was added is judgement: checking, securing, testing, explaining. That is the pattern behind every skill in this article.

How do IT skills stack up in the AI era?

Think of IT skills as four layers. Each layer stands on the one below it.

Four stacked layers of IT skills. At the bottom, the floor: programming, data structures and algorithms, operating systems and networking. Above it, foundations: AI literacy, APIs, databases, secure development, cloud and CI/CD basics, communication and problem-solving. Above that, emerging skills: context engineering, AI-assisted development, AI agents and AI evaluation. At the top, specialisations: architecture, data engineering, cloud-native depth and UX.

Skip the floor and the AI skills on top have nothing to stand on.
  • The floor is not optional: programming, data structures and algorithms, operating systems and networking. It is how you tell when AI output is wrong.
  • Foundations are what every IT role now expects, and AI makes them matter more.
  • Emerging skills barely appeared in job descriptions three years ago. Few newcomers have them. That is why they stand out.
  • Specialisations are where you go deep later.

The WEF Future of Jobs Report 2025 lists AI and big data, networks and cybersecurity, and technological literacy among the fastest-growing skills, with analytical thinking still the most sought-after core skill. That list maps almost exactly onto the foundations and emerging layers.

The 15 skills, with a first step for each

#SkillLayerA good first step
1AI literacy and generative AIFoundationExplain tokens, context windows and hallucination to a friend in plain words
2API integration and backend developmentFoundationBuild a REST API with authentication and one external integration
3Database design and managementFoundationDesign a schema for a real app and explain every index you add
4Cybersecurity and secure developmentFoundationRead the OWASP Top 10, then find two of them in your own old code
5Cloud computing basicsFoundationDeploy one app on a free tier and write down every setting you changed
6DevOps, CI/CD and automation basicsFoundationAdd a GitHub Actions pipeline that runs your tests on every push
7Communication and technical documentationFoundationRewrite one README so a new student can run the project in ten minutes
8Critical thinking and problem-solvingFoundationSolve one problem a week by hand before asking AI, then compare
9Prompt and context engineeringEmergingWrite an instructions file for your repo and compare output with and without it
10AI-assisted software developmentEmergingBuild one feature with an assistant, then review its diff as if a classmate wrote it
11AI agents and agentic workflowsEmergingBuild an agent that calls one real API and asks before it changes anything
12AI evaluation and testingEmergingWrite 30 test questions with expected answers for an AI feature and score it
13Software architecture and system designSpecialisationDraw the architecture of an app you use daily
14Data engineering and analyticsSpecialisationBuild a small pipeline from a public dataset to a dashboard
15Human-centred design and UXSpecialisationWatch three people use your app without helping, and note every hesitation

Cloud and DevOps appear twice in spirit: everyone needs the basics, and going deep on cloud-native platforms or pipelines becomes a specialisation of its own.

Which IT skills are emerging because of AI?

Four, and they are the newest and least understood, so each gets a few lines.

Context engineering. What a model can see matters more than how cleverly you word the request. Giving it the right files, your project’s rules and examples of good output is the skill. In a repository that means instruction files such as AGENTS.md; the AGENTS.md playbook and the guide to GitHub Copilot custom instructions show what goes in them.

AI-assisted development. Using a coding assistant such as GitHub Copilot to plan, write, test and review, with you approving every change. The skill is the approving: reading the diff as carefully as you would read a classmate’s.

AI agents. An agent calls tools and takes steps on its own. It can also call the wrong tool, loop, or act on bad input. The skill employers want is not “has used an agent”. It is building one with limits, logging and a human approval step where the action matters.

AI evaluation. A normal function returns the same answer every time. An AI feature does not. Being able to say “this summariser is right on 27 of 30 test documents, and here are the three it gets wrong” is rare in a newcomer, and it stands out.

Where to start, by year

A four-stage timeline of what IT skills to focus on. First year: the floor, plus AI literacy, databases and problem-solving. Second year: APIs, security, cloud basics and documentation, plus building one feature with an AI assistant. Final year: CI/CD, two finished projects, and one emerging AI skill. Graduate or career changer: fill gaps in the floor, then show one emerging skill in one finished project.

A skill a term is enough, as long as each one is finished before the next.
  • First year: the floor, plus AI literacy, databases and problem-solving. Use AI only to review your own attempts.
  • Second year: APIs, security, cloud basics and documentation. Build one feature with an assistant and review every line of it.
  • Final year: CI/CD, and two finished, deployed projects. Add one of context engineering, agents or evaluation, whichever fits those projects.
  • Recent graduate or career changer: fill the gaps in the floor first, honestly, then show one emerging skill in one finished project.

Leave specialisations until you have finished and deployed at least one real project, because choosing between architecture, data engineering, cloud-native platforms and design is far easier once you have felt which part of a real project you enjoyed and which part you kept putting off. That project will tell you which one you enjoy far better than a course description will.

Questions students ask about what to learn

Which programming language should I learn first? The one your course uses. If you are choosing for yourself, pick Python. It is readable, and it is used for scripting, data and AI. Add JavaScript or TypeScript when you build for the web, and Java or C# if your target employers use them. Concepts carry over. The first language matters far less than learning one properly.

Do I need maths for AI? It depends on the job. Building and tuning models, as a machine learning engineer does, needs linear algebra, probability, statistics and some calculus. Building applications on top of existing models needs much less, although basic statistics helps when you measure how often an AI feature is right.

Should I learn AI first, or web development first? Web or app development, in most cases. AI features live inside applications, and you cannot add a useful AI feature to an app you cannot build. Once you can build and deploy a small app, adding an AI feature to it is the natural next step.

Is prompt engineering worth learning? As a skill, yes. Learn it in its fuller form, context engineering. As a job title on its own, it is rare and fading; employers expect it as part of a developer’s or analyst’s toolkit.

Are certifications worth it? Yes, with a condition. They help most in cloud and security, where employers recognise them. They help most when a project sits beside them that uses what the certificate covered. A certificate on its own shows you studied; the project shows you can do it.

Your skills checklist

Tick a line only when you could show someone the proof: a project, a test, a write-up.

  • I can write a program from a blank file without AI.
  • I can design a small database and explain every index.
  • I can build an API that checks who is calling it.
  • I can name the OWASP Top 10 risks and have found one in my own code.
  • I have deployed something to a cloud free tier.
  • I have a pipeline that runs my tests on every push.
  • I have written an instructions file for an AI assistant and seen the difference it makes.
  • I have measured an AI feature against test cases, not just tried it a few times.

Key takeaways

  • AI skills sit on top of the old foundations. The floor (programming, data structures, operating systems, networking) is not optional.
  • The newer job adverts add judgement to the fundamentals: reviewing AI output, security, testing and explaining.
  • The four emerging skills are context engineering, AI-assisted development, agents with limits, and AI evaluation.
  • Learn in order: floor, foundations, one emerging skill, then a specialisation chosen from experience.

Back to the two adverts

Read the newer advert again and notice what it does not ask for. It does not ask for ten frameworks or a list of AI tools. It asks whether you can build, check, secure and explain.

A newcomer who has the floor, most of the foundations and one emerging skill they can show in a finished project fits that advert. Not because they collected every skill on this list, but because they built them in an order that holds.

Sources

Was this useful?

Share

Found a mistake or an outdated step? Edit this page on GitHub

Frequently asked questions

What skills do I need to start a career in IT in the AI era?
Start with programming, data structures, operating systems and networking, then databases, APIs, secure development, cloud and CI/CD basics, communication and problem-solving. Add AI literacy alongside those, and then emerging skills such as AI-assisted development, context engineering, agents and AI evaluation.
Which IT skills are emerging because of AI?
Context engineering (giving a model the right files and rules), AI-assisted software development, building AI agents with limits and approval steps, and AI evaluation (measuring how often an AI feature is right). Few graduates have these yet, so they stand out, but only on top of solid foundations.
What is context engineering?
Context engineering is giving an AI model the right information to work with: the relevant files, your project rules and examples of good output. It matters more than a clever one-line prompt, and in a repository it usually means instruction files such as AGENTS.md or Copilot custom instructions.
Which programming language should I learn first?
Learn the language your course uses, or Python if you are choosing yourself, because it is readable and used across scripting, data and AI. Add JavaScript or TypeScript when you build for the web. The concepts transfer, so the first language matters less than learning one properly.
Do I need maths to work in AI?
It depends on the role. Machine learning engineers who build and tune models need linear algebra, probability and statistics. Developers who build applications on top of existing models need much less, though basic statistics helps when you measure how often an AI feature is right.
Should I specialise early in IT?
Not usually. Build the floor and foundations first, finish and deploy at least one real project, and let that experience show you which area you enjoy. Specialisations such as architecture, data engineering or cloud-native depth are easier to choose, and to learn, once the foundations hold.
Article banner. On the left, the eyebrow "New to AI" above the title "IT jobs of the future" and the line "The new titles, and the road into them", with the MSDEVBUILD wordmark and the author name below. On the right, three stacked boxes joined by arrows: an amber box reading "Aim straight at AI Engineer", an arrow labelled "no openings for juniors" to a red box reading "Months of rejected applications", and an arrow labelled "the change" to a green box reading "Established role first, AI skills on top".

Next in this series · Part 4 of 4

8 min

New to IT? The IT Jobs of the Future and How to Aim at One

Established and emerging IT roles in the AI era, what each one involves, which skills it needs, and how a newcomer can show they are ready for one.

Continue the series
Part 2 of 4The IT Student After AI: What You Need to Change About the Way You Learn

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

Comments

Your turn

How did Suthahar's articles help you?

If something here saved you time or unblocked a real project, I'd love to hear about it. Submissions are reviewed before they appear on the site.

0/1500 · minimum 10 characters

Never published — used only to verify your feedback.

Your name, company, and role appear publicly if published. Nothing else is collected.

↑↓ navigate ↵ open