IT managers run an organisation's technology: the systems, support, security and budget. They balance everyday reliability with improvements, and they translate between technical staff and the business.
Where you start matters less than what you can show you have done. This is what the work is built from.
Core skills
Tools and settings
What the work tends to feel like from one day to the next.
The week begins with a review of open issues, upcoming changes and anything that went wrong over the weekend. You meet with your team, with department heads about their needs, and with vendors about renewals and problems. There is budget work, security reviews and the occasional crisis. You try to leave time for planning improvements, which is the first thing to be squeezed.
The day-to-day tasks behind the job title, in plain terms.
There is rarely one route to becoming an IT manager. These are the two most common.
Most IT managers have done the technical work and then led others doing it.
Leadership, budgeting and vendor management matter as much as technical depth.
How people usually show they can do the work, and how employers tend to weigh each route.
Common and helpful, but many engineers are self-taught or retrained. Employers care most about what you can build and explain.
Short, practical certifications for a cloud provider, a security standard or a tool show current skills, and can open doors for career changers.
Public repositories, a deployed project, or write-ups of problems you solved often count for more than any certificate.
As you gain experience the work tends to fork. These are two directions it commonly takes.
Keeping systems and support running smoothly.
Planning systems upgrades and digital projects.
A typical shape, not a rule: people move at different speeds, and some skip stages.
Most IT managers have done the technical work and then led others doing it.
Get dependable at systems and networks overview, service management and support processes and security and backup basics, and learn how your employer's tools and habits work. This is where trust is earned.
Keeping systems and support running smoothly. Strategy and change is the other common direction.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
What usually separates people who progress from people who stay level.
Take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Short design notes and post-incident write-ups show how you think, and they are what senior people are asked to produce.
Learn the layer just below and just above the one you work in; most promotions go to people who can see the whole path of a request.
Every role has them. Knowing what they are is part of choosing it well.
Set service levels, use a ticket system and protect time for planned work.
Rank requests by risk and value, be open about trade-offs and show the cost of delay.
Cover the basics well, automate where you can and use trusted partners for specialist needs.
No role suits everyone. These are the traits that help and the things people say they wish they had weighed first.
Local meetups, online forums and open-source project chats are where hiring managers and peers actually talk shop.
Answering questions and reviewing others' code builds a record people can check before they ever meet you.
A repository or two with a clear readme beats a long list of technologies on a resume.
Lead with the problems you have solved and the systems you have run, not only the languages you know.
The two most common routes are years in IT support, systems or networks and management experience and relevant training. Most IT managers have done the technical work and then led others doing it. Leadership, budgeting and vendor management matter as much as technical depth.
The essentials are systems and networks overview, service management and support processes and security and backup basics. Employers also value leading and developing a team, explaining technology in business terms and calm decision-making in outages.
Typical tools and settings include a service desk system, monitoring tools, asset and licence management and reporting tools. The names change with employer and fashion, so understanding what each kind of tool is for matters more than any one product.
Operations and service: keeping systems and support running smoothly. Strategy and change: planning systems upgrades and digital projects. To move up in this kind of work, own something end to end: take a feature, a service or an incident from first idea to production, and be the person who can explain every step of it.
Every organisation depends on technology, and IT managers who can combine reliability, security and sensible spending remain valuable. It is worth weighing the pace of change, screens and sitting and on-call and deadlines before you decide.
Read the interview questions for the role, then practise answering out loud. HireMonkey lets you upload your resume and a job description and answer an AI interviewer that follows up, then scores each answer and tells you what to fix.
Upload your resume and the job description, and the AI interviewer builds its questions from both. Every answer is scored against the bar for the role, with notes on what to fix.