Postings for IT jobs in the US rose 3.2% in the first quarter of 2026, but that headline is a lie in the way only aggregated data can be. Infrastructure and security roles bumped 9% higher. Generic frontend and entry-level analyst postings slipped 6% over the same stretch, according to Lightcast's quarterly labor-market pulse (Q1 2026). The market is not a monolith even a little, and if you treat it like one, you will end up sending another 200 applications into the same black hole that swallowed the last 200.
The short version: the jobs that keep hiring are the ones that keep a company's lights on or its data safe.Cloud infrastructure, applied AI engineering, security operations, and data engineering are all still net-positive.The oversaturated bucket, the one where a posting gets 600 applicants in a weekend, skews hard toward “learn to code” bootcamp outcomes: junior frontend, manual QA, and early-career data analyst roles where the work can be done by a smart intern with ChatGPT and a YouTube playlist.
If your plan hinges on one of those, the math is rough right now.
Which IT sub-paths are actually hiring right now?
I track this stuff because I have to. The BLS projects 25% growth for information security analysts through 2034, considerably faster than average (BLS Occupational Outlook Handbook, 2024). Network and systems administrator roles are only growing about 3%, but the churn is brutal because older engineers keep retiring, so the actual number of open positions stays high. On the other hand, BLS puts web developer growth at around 8%, which is still net new jobs but nowhere near the flood of candidates that bootcamps and comp-sci departments are producing.
From what I have seen, the real hiring oxygen goes to people who can show they have touched a production environment.Infrastructure-as-code, monitoring pipelines, access control that did not break on a Friday.The opposite end of the spectrum, the kind of frontend role where you mostly tweak CSS and call APIs, is getting crushed by global competition and AI-assisted coding tools.I am not saying frontend is dead.
I am saying the generic version of it, the one with a portfolio of calculator apps and weather widgets, is practically a credential for rejection right now.
Why two real projects beat 20 tutorial repos
Here is a thing I keep telling people and they keep not believing me: no hiring manager is clicking through your tutorial repo. They are not. I have sat in rooms where a candidate's GitHub link stayed blue through the entire screening. What recruiters and engineering leads actually do is scan a bullet on your resume that describes something you built that solved a real problem for a real user.
A developer I know in Cleveland spent six months firing off 200 applications with a bootcamp portfolio.He had a to-do app, a weather dashboard, and a movie-search page that hit an API.Crickets.So he stopped applying and rebuilt his portfolio around two things: a real-time incident response dashboard for a mid-size manufacturing company (he cold-emailed the plant manager and offered to build it for free) and a CI/CD pipeline he set up for an understaffed open-source project.
That second project got him a conversation because the pipeline had failed builds, rollbacks, and a post-mortem note.It was ugly.It worked.He got hired within five weeks.
The lesson is not that you should work for free. The lesson is that a single project with real-world scars, even minor ones, is worth more than a dozen polished tutorial clones. I would rather see one sloppy but functional deployment with a README that says “I broke the database and here is how I fixed it” than twenty pristine things that got copied from a YouTube playlist.
Referral economics: the hit rate gap nobody talks about
The numbers are not subtle.LinkedIn's 2024 Hiring Report found that referred applicants are four times more likely to get an interview than cold applicants, and they fill around 30% of all hires despite being only 7% of applicants.That is not new information, but what I find under-discussed is how much the cold-application channel has degraded since AI cover letters and one-click apply tools flooded the market.
When a single posting for a junior data engineer in Denver gets 800 applications in 48 hours, the recruiter is not reading cover letters.They are scanning for a referral flag, a previous company name, or a project link that is not a tutorial.
The most uncomfortable career advice I give to people trying to break in: spend less time tailoring resumes and more time getting someone inside the building to vouch for you.A short Slack message from a current engineer that says “This person built a thing that actually runs” can do more than 50 pages of ATS-optimized text.
I have seen it happen at a logistics firm in Spokane, where a referral triggered a same-day phone screen for a candidate who had been ghosted for three months on the open application track.
How non-CS grads are breaking in (no, not another bootcamp)
The pipeline that actually works for career-changers is not the one bootcamp marketing needs you to believe. It is not “learn React in 14 weeks, build a portfolio, start at $100k.” The people I have watched make the jump, quietly, often come through IT support, QA, or internal-transfer paths that never make it into the success-story blog posts.
A woman I spoke to in Atlanta had a degree in anthropology and was working a help-desk job at a healthcare IT vendor. She started automating her own ticket triage with Python scripts, which got noticed by the infrastructure team. They moved her to a junior cloud operations role because she understood the pain of the on-call rotation better than anyone on that team. No bootcamp. No capstone project. Just proximity to a real system and the willingness to fix things that annoyed her.
Other doors I see work: quality-assurance engineering (automated testing is scripting-heavy, and it is a common bridge into development), Salesforce and ServiceNow administration (low-code but real platform depth), and open-source contribution as a networking tool, not a resume line. If you are not coming from a computer-science pipeline, you need a path that shows you can operate in a messy, production-shaped environment, not one that asks a hiring manager to squint at a tutorial project and imagine you can.
Salary reality check: what the numbers actually look like
Here is where the bootcamp ads and the BLS wage data part ways. The median pay for software developers was $132,270 in 2024 (BLS). But that median pulls in senior engineers making twice that and early-career people making much less. Information security analysts, who are in the highest-demand bucket, had a median of $120,360. Computer support specialists, a common starting point for non-CS grads: $57,910. That gap is real, and it matters if you are budgeting for a career pivot.
The sub-path you pick largely determines the first three years of your compensation arc. Infrastructure and cloud roles trend toward six figures quickly if you have a cert like AWS Solutions Architect Associate and some hands-on project work to back it up. Frontend roles that lean on HTML, CSS, and basic JavaScript often start closer to $65,000 to $75,000, even in mid-cost cities like Boise or Columbus. It is not that those roles are bad. It is that the return-on-hustle is worse because the applicant pools are enormous.
The messiness of all this is the point. There are still great IT jobs out there. They just do not look like the tidy career ladder that gets sold. A lot of the people who end up in them got there sideways, with one real project that solved a real problem and one person inside a company who said, “You should talk to this one.” The rest is noise.