The IT hiring freeze isn’t over — what still works if you’re job-hunting in 2026

I spent five years on the other side of the table, first as a technical recruiter and later running hiring for two mid-size product orgs. The sentence I heard from hiring managers in 2021 was “we’ll take anyone who can ship.” The sentence I hear in 2026 is “we’ll open the req when someone quits, and even then we might just split the work.” That is not a thaw. That is a freeze with better lighting.

LinkedIn will tell you the market is “selective.” Recruiters will tell you “we’re being thoughtful.” Headcount is not zero. It is rationed. If you are job-hunting as if 2021 never ended, you will burn six months proving that volume is not a strategy. This is not a “learn AI” pep talk. It is what still moves a req, what quietly died, and how I would run a search in the next ninety days.

What “freeze” actually means now

A freeze in 2026 is not a locked door. It is a door that opens for one person at a time, usually after someone leaves, usually with a tighter level, and usually with a hiring manager who has already been told they will not get a backfill if this one goes badly.

The public story is still “AI productivity.” Internally, finance wants a lower fully-loaded cost per engineer, legal wants fewer contractors converting, and the VP wants to look rightsized without admitting they over-hired. The pattern I keep seeing:

• Backfills only, and not every backfill. A senior leaves; the team absorbs it for a quarter “to see.”
• Level compression. The req says senior. The bar is staff. The pay band is mid.
• Lukewarm panels kill the req instead of going to a second onsite.
• Contractor-to-hire that never converts. The work is real. The headcount is not.

I still see companies post twenty roles on a Monday. I also still see fourteen of those sit in “interviewing” for eleven weeks while the team ships with the people they already have. The posting is not a promise. It is a permission slip that expires.

If you are mid-level or junior, this hits harder than the headlines admit. The work that used to justify a junior ticket queue — boilerplate CRUD, test scaffolding, “can you add this field” — is exactly the work coding agents made cheap. Companies did not stop needing that work. They stopped needing a full-time person whose whole job was that work.

Seniors are not safe either. They are just safer if they can point at a system they still own. “I was on the platform team” is not a system. “I kept checkout from falling over during the holiday peak after we killed the old queue” is a system. Hiring managers in a freeze hire for risk reduction, not potential.

What stopped working

Spray applications still feel like work. Easy Apply still feels like a plan. I used to watch candidates hit 80 applications in a weekend and then ask why nobody replied. In 2021, a decent resume in a warm market got you a screen. In 2026, a decent resume in a cold market gets you a confirmation email from Workday.

The generic AI cover letter died the same death. Recruiters can smell it in the first two sentences. So can the ATS classifiers vendors sold as “assistant screening.” You are not fooling a model with a model. You are adding another unread paragraph to a pile that is already unread.

Bootcamp volume is the third zombie. I advised programs that promised placement rates they could only hit in a hiring binge. A certificate is not a differentiator when the hiring manager has 400 applicants and a mandate to hire someone who has already done the job. “I completed the course” is not a skill the way “I shipped the migration and owned the rollback” is a skill. If your search depends on a credential you earned after the freeze started, you need a second plan.

What still works: fewer doors, better proof

The channels that still convert are the ones that reduce the hiring manager’s personal risk. They are not looking for the best engineer in the abstract. They are looking for the person they will not have to defend in a headcount meeting three months from now.

A real referral, not a LinkedIn “happy to connect”

Referral still beats every other channel. That has not changed since I was filling reqs in 2018. What changed is the quality bar. A former teammate who can say “I would take this person on my on-call rotation” is a referral. A college acquaintance who clicks a form is not.

Make a list of twenty humans, not two hundred companies. People you shipped with. People who saw you debug something ugly. People who left for a company that is still hiring in your stack. Write a short note that names the work, not your feelings about the market. Ask for fifteen minutes, not a referral. If the conversation is good, they will offer the intro. If you ask for the intro in the first sentence, you sound like everyone else in their inbox.

Warm intros into a frozen team still die. Warm intros into a team that just lost someone do not. Watch who posted a goodbye. Watch which engineering blogs mention a rewrite. Watch which companies just raised or just missed a quarter — both create different kinds of hiring, and both are more honest than the career page.

Proof that is boring and specific

Portfolios still matter, but not the ones with a gradient hero and three tutorial clones. I want two or three artifacts I can open in five minutes: a public repo with a real README and a real trade-off in the commit history, a write-up of an incident you owned, a before-and-after metric from a system you changed. If you cannot publish the work, describe the constraint. “Couldn’t show the code, here’s the latency graph and what we cut” is more useful than another weather app.

If you have been unemployed for a stretch, do not hide it and do not fill it with fictional consulting. Ship one ugly, finished thing that matches the jobs you want. Hiring managers in 2026 are allergic to “I was exploring.” They are hungry for “I shipped this, here is what broke, here is what I would do next.”

Resumes still go through ATS filters, and take-homes are still being used as unpaid screens. That pairing is its own mess — the keyword dance versus the weekend project that never gets read. If you want the mechanics of that loop, ATS keywords and take-home fatigue is the next layer. For this piece, the only rule I care about is: do not spend twelve hours on a take-home for a company that has not given you a real conversation with the hiring manager. In a freeze, take-homes are cheap for them and expensive for you.

Narrow the stack on purpose

Generalists still get hired. They get hired slower. The reqs that move in 2026 name a system: payments, identity, data platform, mobile release, SRE for a specific product, a compliance-heavy backend. If your resume says “full-stack” and your last three years were React plus a bit of Node, you are competing with everyone who also did that, including people who will work for less because they are scared.

Pick a lane for the search even if you do not want it to be your forever lane. I would rather see “TypeScript services, Postgres, the boring path” than “passionate about distributed systems and also design systems and also LLMs.” Passion is not a filter. A lane is a filter.

This is also where people waste the “learn AI” year. Adding Copilot to your workflow is table stakes. Calling yourself an AI engineer because you wrapped an API is how you get filtered out by the people who actually evaluate models. If AI is the lane, show evaluation, cost, or a production constraint. If it is not, use the tools and talk about the product you shipped. Do not make the tool the headline unless the job is the tool.

Contract work and the companies that never froze

A lot of the hiring that still happens is not on the career page. It is a three-month contract through a vendor you have never heard of, a staff-aug seat inside a bank, a consultancy backfilling a delivery team. Treat the contract as a paid interview with a known end date. Negotiate the rate as if conversion will not happen. Keep the search running in week eight. If they convert you, great. If they do not, you have recent production work and a reference that is not from 2023.

The companies that never really froze are boring on purpose. Regional banks. Logistics. Healthcare IT. Industrial software. Government-adjacent vendors. Mid-market SaaS that still sells with a purchase order. They pay less than the name-brand labs. They also hire because the work did not disappear. If your burn rate is real, prestige is a luxury good.

Remote-only is tighter than it was. Hybrid reqs in cities with an office are moving faster than fully remote reqs at the same level. That is not a moral statement. It is a count of who gets approved. If you can be in-office two days a week, say so early. If you cannot, do not spend three months pretending the remote role on page four of the listing is the real one.

How I would run a ninety-day search

If I were hunting right now, I would stop thinking in applications and start thinking in weeks.

Week 1 is inventory, not volume. Write down the last four things you actually owned. Not teams. Things. A service, a migration, an incident, a customer-facing bug that took a month. Put dates on them. Put a metric on them if you have one. Then write a one-page resume that only includes the work you can talk about for twenty minutes. Delete the rest. A freeze rewards depth you can defend, not a museum of tools.

Week 1 is also a list of twenty people. Names. Last time you spoke. What you shipped together. Then five companies where those people now work, plus five companies in your lane that are hiring a backfill you can actually see — a public goodbye, a new manager post, a job up for less than three weeks. Ignore the ones that have been “hiring” since last summer.

Weeks 2–4 are conversations. Two informational chats a week is a real pace. One tailored application a day is a real pace if you have a reason to believe a human will see it. Forty Easy Apply clicks is a coping mechanism. When you do apply, write the first paragraph as if the hiring manager will read only that paragraph. Name the system they run and the thing you have already done that looks like it. If you cannot name the system, you are not ready to apply to that one.

Weeks 5–8 are loops and cuts. If a company has not scheduled a hiring-manager conversation after two screens and a take-home, you are in a maybe-later pile. Stop giving them your weekends. If a loop keeps adding “one more stakeholder,” ask what decision is still open. Ambiguity is how frozen teams stall candidates they like but cannot afford. Do not resign until the written offer is signed. “Leading candidate” is a phrase recruiters use when they need you warm while they wait for budget.

Weeks 9–12 are a reset, not a panic. If nothing is moving, the problem is usually targeting, not your soul. You are too senior for the reqs you can get into and too vague for the reqs you want. Or you are only applying to companies that froze. Fix one of those. Do not add a sixth certification.

The conversations that still get you past the screen

Screening calls in 2026 are shorter and more suspicious. The recruiter wants to know if you will accept the band. The hiring manager wants to know if you will create work for them. Both are listening for one thing: have you done this job before, in conditions that look like theirs.

Prepare three stories you can tell in under three minutes each. A time you inherited a mess. A time you said no to a feature. A time production hurt and you were the person who stayed. Do not memorize a STAR worksheet. Memorize the constraint, the decision, and the leftover risk. Leftover risk is what seniors sound like. “It worked” is what juniors sound like when they are guessing.

Ask questions that reveal whether the req is real. “What happens to this role if you don’t hire by the end of the quarter?” is better than “what’s the culture like?” “What would make you close this req without a hire?” is the one I wish more candidates asked. Frozen teams close reqs without hires all the time. Salary still has to happen early. If you name a number first, name a range you would actually accept, then stop talking. Filling the silence with “I’m flexible” is how you get the bottom.

What I would stop doing this week

Stop refreshing the same six career pages. If they wanted you, the process would have dates on it. Stop rewriting your resume every Sunday to match a different fantasy job. Pick a lane for thirty days. One resume. Small edits.

Stop treating every rejection as information about your worth. In a freeze, rejection is often information about budget. And stop waiting for the market to “come back.” We are not going back to 2021 staffing. Software still gets written, by fewer people with more tools and less patience for ramp time. If you are employed and restless, a transfer into a drowning team is easier to approve than a new hire. If you leave, leave with proof. “I needed a change” is not a story that survives a frozen loop.

The unglamorous version of hope

People still get hired. I have seen it this year: a staff engineer who took a contract at a payments firm and converted in month four; a mid-level who moved cities for a hybrid role at a company nobody tweets about; a junior who got in because a former intern manager staked their name on them and the take-home was a real ticket, not a weekend puzzle. None of those stories started with 200 applications. They started with a short list and something specific to show.

The freeze is not a moral verdict on your career. It is a staffing policy wearing a productivity story. Treat it like weather. Walk toward the doors that still open. Leave the ones that are painted on the wall. Make the list of twenty people today. The resume can wait a day. The people who can still move a req cannot.