is this you?
IT Manager
Every company runs on systems someone has to own — the network, the laptops, the identity stack, the vendor contracts, the security posture, and the human beings who keep it all breathing. The IT manager is that someone. It's the classic destination of the help-desk ladder and one of the most underrated six-figure careers that doesn't require a degree. Here's the honest picture.
Median pay (US)
~$105k / yr
Degree required?
Often no — experience + certs carry it
What the job actually is
IT managers own an organization's technology operations: the infrastructure (network, endpoints, servers or — increasingly — the SaaS and cloud stack that replaced them), identity and access, the help desk team and its queue, vendor selection and contracts, budgets and hardware lifecycles, security hygiene (patching, backups, MFA, the unglamorous work that prevents disasters), and the projects — migrations, office moves, new systems — that keep the place current. The people side is half the job: hiring and growing technicians, managing the queue's morale, and translating between executives who want costs down and users who want everything to just work. In smaller companies you're hands-on-keyboard daily; at larger ones you're a manager of managers with a budget line.
Is it actually you?
You'll probably love it if
- You like being the person who makes the whole place run — quietly load-bearing
- Mentoring junior techs into professionals genuinely appeals to you
- You can hold both vocabularies: subnet masks with the team, cost-per-seat with the CFO
- Structured problem-solving under interruption is your natural mode
- You want a technology career with roots — IT managers build tenure, not gig-hop
Maybe not, if
- You'd miss deep technical work — this job trades depth for breadth and people
- Being blamed for everything that breaks (and thanked for nothing that doesn't) would corrode you
- Budget season, vendor negotiations, and compliance checklists sound like purgatory
- On-call escalations and the occasional ruined weekend are dealbreakers
- You avoid conflict — performance issues and pushy vendors both require it
The real day-to-day (no hype)
- This is the help desk's ceiling-breaker — and the ladder is genuinely open. Help desk → senior tech/sysadmin → IT manager remains one of the most reliable no-degree six-figure ladders in the economy. What separates the ones who climb: they document, they own projects end-to-end (not just tickets), they learn the business vocabulary, and they say yes to the migration nobody wants to lead. Certifications (CompTIA stack early, then Microsoft/cloud/networking depending on environment) function as the degree substitute — imperfect but genuinely effective here.
- The job moved to the cloud and became vendor management. The server room is mostly gone; the modern IT manager runs a portfolio of SaaS and cloud services — which means the core skills shifted toward identity management, integration sanity, license and cost optimization, and negotiating with vendors from a position of knowledge. The techs who resent this drift struggle; the ones who embrace 'my infrastructure is contracts and configurations now' thrive.
- Security became half the job whether you asked for it or not. Most mid-size companies have no CISO — the IT manager IS the security function: backups that actually restore, MFA enforcement, phishing response, cyber-insurance questionnaires, and being the person explaining to leadership why the company needs to spend money on invisible protections. This is also the career accelerant: IT managers who develop real security chops are the natural candidates for the better-paid security leadership roles.
- AI is thinning the tier-one layer below you — restructure toward it, not against it. Chatbots and automated remediation are eating password resets and routine tickets — the traditional training ground for junior techs. Forward-looking IT managers are redesigning their teams around it: fewer people on rote tickets, more on projects, automation, and user enablement. The uncomfortable part: the entry rung you climbed is narrowing for the next generation, which makes deliberate skill development for your juniors a management obligation, not a nicety.
How people break in — or switch in
The standard route runs through the trenches: help desk or desktop support → sysadmin/senior tech (own systems, not just tickets) → team lead → manager, typically 6–10 years compressed or stretched by company size and your project appetite. Accelerators: volunteer to LEAD something visible (an office move, an identity migration, an MDM rollout) — management sees project leadership, not ticket volume; get the people-reps early (train new hires, run the queue when the boss is out); and learn budget language (cost-per-seat, opex/capex, license true-ups) before you need it. Switching in from adjacent tracks (network engineering, sysadmin at an MSP) works well; MSP experience especially — it's IT management boot camp, high reps across many environments. Degrees help at conservative enterprises; a track record of systems that stopped breaking helps everywhere.
Help desk / IT support → IT manager (the ladder)MSP technician → in-house IT managerSysadmin → IT management (the people turn)IT manager → IT director / security leadership
Sysadmins hesitating at the people-management turn: try it reversibly first — lead a project with two techs assigned to you, or run the team for a coverage month. Some discover they love multiplied impact; others learn cheaply that they'd rather stay deep. Both answers are wins.
Your application, already half-written
Here's a question every IT Manager application asks, answered the way pirch would — in a real voice, grounded in real experience:
“Tell us about a time you improved IT operations at an organizational level.”
I inherited a 200-person company's IT with a bad smell: the ticket queue averaged four days to resolution, nobody trusted the backups, and shadow IT was everywhere because official requests died in the queue. Rather than grind the queue harder, I treated it as a systems problem. First, data: two weeks of categorizing showed 60% of tickets were the same eight issues — so we automated password resets with self-service MFA, wrote plain-English guides for the next five, and cut the queue nearly in half without hiring. Second, trust: I ran an actual restore test (the backups failed it, as I feared), fixed the pipeline, and started monthly restore drills with results reported to leadership — which turned IT from 'the department that says no' into the department that shows receipts. Third, the shadow IT: instead of policing it, I built a fast-track approval path — most people just wanted a decision in days, not weeks. A year in, resolution time was under one day, and my favorite metric: unsolicited exec requests for IT to be in planning meetings, because we'd become the department that makes things work rather than the one that explains why they can't.
pirch's co-pilot writes answers like this for
your background and the exact job —
try it free →
pirch finds the IT leadership roles that are actually you
IT manager postings range from 'hands-on tech with a title' to 'director in disguise' — scope and pay vary wildly for the same words. Tell pirch who you are and it hunts down real, still-open roles that match your actual level, with a tailored cover letter already written. No spray-and-pray. No dead links.
start your free hunt
first hunt free · we never auto-apply · you stay in control
Common questions
What does an IT manager actually do?
They own technology operations: infrastructure and the SaaS/cloud stack, the help desk team, identity and security hygiene, vendor contracts and budgets, and the projects that modernize it all — plus translating between executive cost pressure and user needs. In smaller companies it's hands-on; at scale it's management proper.
How much do IT managers make?
Roughly $75k–$150k+ with a median around $105k, scaling with company size and scope. IT directors and security-leadership roles above it run $130k–$200k+. It remains one of the most reliable six-figure destinations reachable without a degree.
How do I go from help desk to IT manager?
Own projects, not just tickets: lead a migration, a rollout, an office move. Add people-reps (training hires, running the queue), certifications matched to your environment, and budget vocabulary. The typical climb is 6–10 years; project leadership and business fluency are what compress it.
Do you need a degree to become an IT manager?
Frequently no — this is one of tech's most experience-driven ladders, with certifications standing in for credentials. Large conservative enterprises may filter on degrees, but mid-market companies hire proven operators, and MSP experience is widely treated as the equivalent of an intensive apprenticeship.