A tech job search is easier to carry when you treat it as a handful of separate problems, each with its own next step. These tech job search guides are split that way, so you can open the one that matches where you're stuck today. Each one is a plan for the parts you control.
If you've just been laid off, start with the first two weeks. The guide puts the things with deadlines ahead of any application: the severance agreement, health cover and unemployment benefits. Then it moves to how long you can afford to search, who to line up as references, and how to start applying with every application logged from the first one. You aren't behind, and a short ordered list beats a frantic one.
Once you're sending applications, the quiet is the next thing to deal with. The guide on getting no response explains what ordinary silence looks like on the hiring side, and why a long run without replies rarely proves your resume is the problem. It shows you how to sort your own applications into groups and see which ones get answers, so your next batch goes where it works.
A related question comes before you apply at all: is the posting even real? The ghost job guide gives you a quick check against the employer's own careers page, and a date to decide in advance when a quiet application moves to Closed.
If you're searching while you still have a job, two guides cover the awkward parts. One is about getting time off for a long interview loop without lying to your manager: how to ask each recruiter for the shape of the loop, which rounds to cover with leave, and what you can truthfully say at work. The other is about references. When your manager doesn't know you're looking, you need to know who else to name, and when it's reasonable to allow a call to your current employer.
The last guide is about safety. Engineers get targeted by fake recruiters, and some of those messages ask you to run code, not just hand over personal details. The guide walks through the checks on the sender, the role and the repository before you reply or open anything.
Read them in order if you're starting from a layoff, or jump straight to the problem in front of you. Whatever the guide, three habits carry across them:
- Write down where each application came from and when you sent it.
- Decide what "quiet for too long" means before you start waiting.
- Keep your search private until you've chosen to share it.
Every tech job search guide
- Laid off on H-1B: your job search inside the 60-day grace period: Laid off on an H-1B? What USCIS lets you do in the up-to-60-day grace period, what to track day by day, and where the DHS proposal stands as of Nov 13, 2026.
- Job search burnout as a software engineer: hours a day and when to pause: Months into a software engineering search and worn out? How many hours a day to keep, which days to drop, and a test for when a week off costs you nothing.
- Laid off during an interview process: do you tell the recruiter?: You were laid off in the middle of a hiring loop. When to tell the recruiter, what to put on forms, and what a background check can show.
- Fake recruiter email as a software engineer: the checks: A recruiter emailed you a repo to run or a Gmail address. Checks on the sender, the role and the code before you reply or open anything.
- Interviewing while employed: getting time off without lying: A four-round engineering loop takes about a day of your time. How to ask for the hours, split the rounds and say only what's true to your manager.
- No response from job applications as a software engineer: 150 applications, no replies? What's normal for a software engineer in 2026, and how your own counts show whether to change targeting, resume or channel.
- References while employed: who to name before an offer: The new company wants references and your manager doesn't know you're looking. Who to name, when to allow a current-employer check, and what to say.
- Is that software engineering job a ghost job? What to check before you apply: Is that engineering posting real? Check it against the company's own careers page first, then pick the date a quiet application goes to Closed.
- Laid off as a software engineer: your first two weeks, before you send an application: Laid off as a software engineer? Do these in order: severance and deadlines, health cover, money runway, references, then a search you can track.
Keeping a long search in one place
A search that runs for months, across a layoff or a current job, is hard to hold in your head. Job Search by HighCircl is free during the open beta, open to 300 people in the US. It lists roles only from employers' own boards, so a posting that's been taken down stops showing.
FAQ
Where should you start a tech job search after a layoff?
Start with whatever has a deadline: your severance agreement, health cover and unemployment benefits. Applications can wait a few days. Once those are on your calendar, work out how long you can afford to search and begin applying with each one logged.
Is it normal to hear nothing back from tech job applications?
Yes. Silence is common on the hiring side and rarely tells you much about your resume. Sort your applications by how well the role fit, how you applied and how old the posting was, then send your next batch to whichever group gets replies.
How can you interview while employed without telling your manager?
Ask each recruiter for the full loop up front, fit short calls around work and cover the long rounds with your own leave. You owe your manager a date, not a reason, and you never need to invent one. For references, name former managers and colleagues, and allow a current-employer check only after a written offer.