November 15, 2026

How to find a software engineering job in 2026: a guide

How to find a software engineering job: where to look, spot ghost jobs, track applications, follow up and pace a long search, with guides for each step.

Career

Guide

Finding a software engineering job in 2026 means running the search as a funnel, not hoping the next application lands. Apply to real, open roles on the employer's own board, record every application, and follow up on a schedule. Then read your replies by group to see what to change. We'd cap daily hours and cut stale and ghost postings first, so silence stops hiding what's working.

If you're about to graduate, start with the job sites for new grad software engineers and come back for the later stages.

What's on this page

How hard is the search right now, and what is a normal result?

Harder than it was, and silence is the normal result. Ashby's May 2026 data release puts applications per hire at over 300, three times the 2021 level. It also says a candidate's chance of an interview is about 50% lower than five years ago. HR Dive's report on Employ's Hiring Benchmarks found 257.6 applications per job in 2025, up from 207.2, so the crowd keeps growing.

Those are employer-side numbers, and none of them tells you how many applications your own search needs. What they do tell you is that every posting you apply to has a crowd behind it.

Checkly published its own 2025 hiring funnel, and it's the clearest picture we've seen of what a crowd looks like. The company received 12,479 applications across 12 postings. Just 217 of them, about 1.7%, reached an interview with a hiring manager. A single Senior Backend Engineer posting drew 4,578 applications. If you were one of 4,578, a no was the most likely outcome however good your CV was.

So stop reading individual silences and start counting. A feeling of "nobody replies" can't be fixed, because it doesn't point at anything. A count can.

After about 50 applications, sort them into groups. Which resume version did you send? Did the role match your level? Did you apply on the employer's own board or through a repost? Did someone refer you? Then see which group produced any reply at all. If every reply came from one group, do more of that. If no group produced one, change one thing, the resume or the targeting, and count the next batch the same way.

The full version of this, with a 150-application worked example, is in our piece on what to do when software engineer applications get no response.

What do you do in the first two weeks after a layoff?

Start with the record, before the next application, whether you've sent none or forty. Then spend the first two weeks on the things that have dates attached. Those pay back more than extra applications.

Start with the paperwork. Find your last day, the date your benefits end, when any severance is paid and what you've been asked to sign. Put each date in one place and read what you've signed before you sign more. Deadlines are the one part of a layoff you can't recover from by working harder later, so they go first.

Next, count your money. Add up a month of real expenses and divide your savings and expected payments by it. The result is your runway in months, and it decides how picky you can be and how soon you need to widen the net. A number is easier to live with than a vague worry, even a short one. We'd also set a date, about a month out, to look at it again.

Then line up references while everyone still remembers your work. Ask two or three former managers or senior colleagues, one at a time, whether they'd speak for you, and write down how each prefers to be contacted. Ask before you need them. It's a harder conversation to start the week an offer is pending.

After that, build the record: a sheet or an app with every role you apply to, a date and a next step, described in the tracking section below. Our guide to your first two weeks as a laid-off software engineer walks through each step in order.

Two situations change the order. If you're on a work visa, the clock starts at your last day. Read the guide to your job search inside the H-1B 60-day grace period before anything else on this page.

If the layoff landed while you were mid-process with another company, you'll have to decide what to tell that recruiter and when. The post on being laid off during an interview process covers it.

Where do you find real software engineering roles?

Start from the employer's own careers page and treat job boards as a way to find leads. Many companies run their hiring through an applicant tracking system such as Greenhouse, Lever or Ashby. The posting on that page is the one the hiring team can actually see and act on. A board's listing is a copy, and copies go stale. A copy can sit online for weeks after the role is filled or the budget is pulled.

That principle shapes the whole of the rest of the search. You pick target companies, check their boards, apply there, and record the application with the link to that page. Boards still earn their place for discovery, because they show you companies you hadn't thought of. Use them to build a list, then go to the source.

Use as many sources as you can keep track of: company boards, a few job sites, referrals, recruiters. More sources isn't the problem. Losing track is, so make sure every application lands in one record, whichever source it came from.

Job Search is our product, so weigh this with that bias in mind. It shows jobs straight from the source: the careers pages companies run on applicant tracking systems such as Greenhouse, Lever and Ashby, synced daily, so new roles appear within a day. You won't see the same job five times, and a job disappears once the company takes it down. There's a tracker built in, and we keep adding sources and applicant tracking systems. In our opinion it's the best place to start, and that's exactly where we're biased.

Which other boards are worth the discovery time is a separate question, and we've answered it in a few ways. The best job sites for software engineers is the US overview. If you want to work remotely, the best remote job sites for software engineers cover that narrower field. For sites that only list direct employer jobs, there's a ranked list of job boards that skip reposts. If LinkedIn is where you've spent the most time and got the least back, the LinkedIn Jobs alternatives for tech job seekers are worth an hour.

You can also search many employers' applicant tracking pages at once instead of visiting each. The guide to searching Greenhouse, Lever and Ashby jobs in one place shows how.

Networking and referrals sit next to all of this. Pick one company from your list and one person who works there, ideally someone whose work you know or who shares a past employer or school with you. Ask a small, specific question, such as how the team works or whether the role is what the posting says. Don't open by asking for a job. One such conversation costs little and tends to be a better use of an hour than the fortieth cold application.

Make it a weekly habit, not a last resort, and put each conversation in your record next to the application it relates to.

If your next role isn't an engineering one, the same principle applies and the board lists differ. There are versions for product managers and data scientists and analysts.

How do you tell a real posting from a ghost job or a fake recruiter?

Check the company's own board first. If the role isn't there, treat the listing as dead until you learn otherwise. A role can be real and still be effectively closed, and it can be open and still not be hiring anyone. Greenhouse puts ghost jobs at 18-22% of postings on its platform in a given quarter. That's roughly one posting in five that isn't a real chance, and you can screen most of them out in a couple of minutes.

The checks are quick and, in our view, worth doing before you spend an hour tailoring a resume. Is the role on the employer's own board? Does the apply button go somewhere that works? Has the posting been reposted several times without changes? Does the job description list a team and a reason for the role, or does it read like a template? The post on whether that software engineering job is a ghost job lists the signals, and how to tell if a job posting is still open gives a six-step check you can run on any listing.

You'll also meet the other kind of fake, the recruiter email that isn't from a recruiter. For an engineer with a public profile, these often arrive weekly. The usual tells are a sender address that doesn't match the company's domain, a role you can't find on the company's own board, and a request for personal documents or payment before any interview.

Slow down at any of them. Look the recruiter up through the company's site and not through the email, and reply only after you've confirmed the person exists. The checks for a fake recruiter email go through the pattern in more detail.

Put the result in your record. A one-word note, "open", "unclear" or "gone", on each application saves you from following up on a role that vanished two weeks ago.

How do you track hundreds of applications without losing count?

Write down six things for every application on the day you send it: the company, the role, the link to the posting, the date you applied, the current stage, and the date you'll next do something about it. The last one is what turns a list into a system. That next-action date is the date you'll look at the application again, to follow up or close it. Without it, an application sits there and you only remember it when you feel guilty.

A set of stages keeps the record readable. These five cover nearly everything a search produces.

StageWhat you record
SavedThe role and link, before you've applied
AppliedApplied date, resume version, next-action date
InterviewingEach round, who you met, what comes next
OfferTerms, deadline, who else is pending
ClosedWhy: rejected, withdrawn, filled, or silence

Closed matters more than it sounds. Silence is an outcome, and it belongs in your count. Close each row with a reason, because the reasons feed the numbers. When you reach the 50-application checkpoint from the first section, the Closed rows tell you what happened to the ones that went quiet.

How you hold the record is a taste question. A spreadsheet is free, flexible and easy to break, and the guide to the job search spreadsheet has the columns to start with. A CRM built for sales can track people as well as roles, which sounds useful and often isn't. We'd skip it unless you already live in one.

A dedicated app does the bookkeeping for you at the price of learning one more tool, and the job search apps with a tracker, compared lines up seven of them. Pick the one you'll still open in week ten. We'd lean toward the simplest tool that has a next-action date.

Some employers also let you check where an application stands in their portal. It can be useful, but statuses are often vaguer than they look, and "under review" can sit on a role for months. Read what a given system shows before building plans on it, and copy any change into your own record so it lives in one place.

Search more than 300,000 open roles in one place
From more than 20,000 companies across the UK, the US and Spain. Free during the open beta, until the end of November.
Try Job Search

When and how do you follow up on an application?

Follow up once, about two weeks after you apply, and again at each stage where something is pending. A follow-up's job is to tell you whether the application is alive, so you can stop carrying it, and a polite note costs little.

What you're asking for differs by stage. After applying, you're checking that a human has seen your application, ideally by writing to someone on the hiring team and not a general inbox. The advice on a follow-up email after applying covers when to send it and who to address.

After a phone screen, you're thanking the person and confirming the next step, and the follow-up email after a phone interview gives short wording you can edit. After a second interview, when more rounds are coming, a follow-up should stay light and not ask for a decision. The guide to a follow-up email after a second interview handles that case.

Recruiters writing to you need a reply too, even when the answer is no. A short, friendly answer keeps the door open and keeps your inbox from becoming a second pile of things you owe someone. The post on how to reply to a recruiter email has versions for interested, not now and no.

Following up stays manageable because of the next-action date from your record. Each morning, filter for rows dated today or earlier. Send those messages, then set a new date or close the row. That's the whole routine, and it takes minutes. Without the date, following up means remembering 80 applications, and nobody can do that.

Keep every message short and polite, and treat any template as a starting point for your own words. One note is enough.

What do you do when a company goes quiet?

Quiet is common enough that you should plan for it. Greenhouse's survey puts ghosting after an interview at 61% across the US, UK and Germany. TopResume's October 2025 Jobseeker Trends Report found that 71.3% of its US respondents had been ghosted by an employer in the past year.

Read those as a description of how companies behave, not of what you did. Hiring teams freeze budgets, lose a champion or simply stop answering, and you rarely find out which. Silence isn't about you.

What you can control is how long you keep a role alive in your head. Our rule is the same at every stage: send one clear message, set a date for the last look, and when it arrives, close the row. A role kept open in your head costs attention you need for the ones still moving.

The wording and timing depend on where you stood when the messages stopped. After a final round, you're likely to have invested the most and heard the least. The guide on being ghosted after a final interview lays out when to follow up and when to move on.

After a take-home assignment, you gave unpaid hours, which changes how patient you need to be. The post on being ghosted after a take-home assignment covers the next message. After a verbal offer, the stakes are highest and a nudge is most justified. The guide to being ghosted after a verbal offer says how long to wait and what to send.

The other kind of ending is a rejection, which at least is an answer. A short, gracious reply costs a minute and sometimes leaves a recruiter remembering you for a different role. There's wording for replying to a rejection email in a short guide.

How do you run several interview loops at once?

Log every round as it happens, and line up offer timing early. When you're in four processes at once, memory fails first. Who you met, what they asked, what they said about the team, what the next step is and when it was promised are the details that blur by the third day.

For each loop, record the date, the interviewers and their roles, what you covered, anything you promised to send, what they promised, and the date you expect to hear back. Add the follow-up you owe and when. The interview tracker for several loops at once goes through what to log per round and how to line up offers.

Offer timing is the part most people leave to chance. Offers arrive on the employer's schedule, and a company that moves fast can pressure you to answer before a slower one has finished. If you're a few weeks from an offer elsewhere, tell the faster company you're in other processes and ask for a realistic deadline. Don't invent competing offers.

Write down the deadline of every process in your record so you can see collisions weeks ahead, not days.

Add a prep note per company to the same record. After each round, write down what you'd do better in the next one, split into coding rounds, system design and behavioral. Looking across companies, the gaps that repeat are the ones to practise, and the notes also tell you which company expects which format.

Our view on offers is that you shouldn't negotiate against a deadline you haven't seen yet. Once an offer lands, ask for the full terms in writing and a few days to respond, and use that time to tell the other processes where you stand.

Can you search while you are still employed?

Yes, and for most people it's the stronger position, because you have an income and no deadline. The cost is time and discretion: you have to find hours for interviews and keep the search from reaching your employer.

Time is the practical problem. Interviews happen in the working day, and you can't be on a call at 2pm every Tuesday without someone noticing. You can ask for time off the ordinary way, as personal time or leave, and you don't need to explain it. You never need to invent a dentist or a family emergency, and we'd advise against it. The guide to interviewing while employed and getting time off without lying covers the options.

Try to bundle interviews on the same day when a process allows it, and ask for early or late slots so fewer calls land in meeting hours.

Discretion is the other half. Keep the search off your work laptop, work calendar and work accounts. Use a personal email address and phone for recruiter contact, and keep your record somewhere your employer can't see it.

References need a plan too. Naming your current manager before you have an offer is risky, and most companies understand that. The guide to references while employed explains who to name as a reference before an offer. A former manager or a trusted peer from a previous company often works.

You can also afford to be choosy and turn down a mediocre offer. That's the real advantage of searching from a job, and you waste it if you apply to everything out of habit.

How do you keep going through a search that takes months?

Pace yourself, because a long search is a distance event. TopResume's report found that 68.4% of US respondents said their job search hurt their mental health. It also found that more than 26% of US respondents who landed a job in the past year said it took longer than 16 weeks. In Fortune's May 2026 coverage of a Glassdoor poll, 53% of the US professionals Glassdoor polled had paused a search entirely to protect their mental health.

So the plan has to survive week 16. A search built on sprinting won't. Three habits help, and they cost nothing.

First, cap your daily hours. Pick a number you can sustain, and stop when you reach it. More hours rarely produce better applications after the first few; they produce worse ones and a worse mood. We'd keep the cap lower than feels responsible, and protect the evenings. The guide to job search burnout for software engineers covers how many hours a day to put in and when to pause.

Second, pick a restart date before you need a break. A pause you planned feels like a decision, and a pause you fell into feels like failure. If you stop for a week, write down the day you'll start again and the first thing you'll do on it.

Third, keep a record that holds your place. When you come back after a break, the last thing you want is to rebuild the picture from memory. Your record tells you what's pending and what to do next, so a restart takes ten minutes instead of a day. It's also how you notice progress, a second-round interview or a recruiter who wrote back, on weeks when it doesn't feel like any.

Nothing here is a quota, and a slow week isn't a failed one. The point of pacing is to keep you searching long enough for the odds to work.

What to do with your search this week

Set a goal, choose your job boards and start tracking. Here's a week we'd stand behind.

  1. Set a goal for the week: how many applications you'll send, how many follow-ups, and a daily hours cap with a restart date.
  2. Choose your job boards and company boards, as many as you can keep track of, and check that each target role is open on the employer's own board before you apply.
  3. Start tracking today, before you send another application: which role, where you found it, what stage it's at, and a next-action date.
  4. Follow up once on each application that's about two weeks old.
  5. After 50 applications, count replies by group (resume version, targeting, source) and change one thing.

We'd check at 50 because it's enough to show a pattern without making you wait a quarter. The hours cap is yours to set; the number matters less than having one.

If you do only the tracking step this week, you've made the biggest difference, because every other step reads from that record. The tech job search guides go deeper on each stage, from the first weeks after a layoff to the offer.

All job search guides

Tracking your applications

Following up

If you can't say which applications went quiet

If you're searching right now and can't say which applications went quiet, a tracker can keep that count for you. Job Search is our newest product, so come try it out: jobs straight from the source, synced daily, plus a tracker that moves an application when a recruiter email is clear and leaves the unsure ones for you. It's in beta, and your spreadsheet works fine too.

FAQ

How hard is it to find a software engineering job right now?

Harder than five years ago. Ashby's data shows over 300 applications per hire and an interview chance about 50% lower than five years back. Checkly's 2025 funnel shows what that looks like in practice: 217 of 12,479 applications, about 1.7%, reached a hiring-manager interview. Silence is the base case, so judge your search by counting replies by group, not by how any single application feels.

How many applications does it take to get a software engineering job?

There's no universal number. The 300-plus figure is applications per hire from the employer's side, and it says nothing about how many you personally need. What works is counting: after about 50 applications, group them by resume, targeting and source, see which got replies, and change one thing.

What should you do first after a layoff?

Handle anything with a date on it: your last day, when benefits end, when severance is paid, and what you're asked to sign. Then work out your runway in months, line up two or three references while your work is fresh, and build your application record. Start applying once the record exists. If you're on a work visa, read about the grace period before anything else.

Should you follow up after applying for a job?

Yes, once, about two weeks after you apply, and again at each stage where something is pending. A follow-up tells you whether the application is alive. Keep it short and polite, address it to someone on the hiring team where you can, and set a next-action date in your record so you never have to remember it.

What do you do when a company ghosts you after an interview?

Send one clear follow-up, set a date for your last look, and close the row when the date arrives. Greenhouse's survey puts ghosting after an interview at 61% across the US, UK and Germany, and TopResume found 71.3% of US respondents had been ghosted by an employer in the past year, so it says little about you. Record the outcome as Closed with the reason "silence" and keep your attention on the roles that are moving.

Can you look for a job while you're still employed?

Yes, and most people find it the stronger position. Keep the search off work devices and accounts, ask for time off the ordinary way instead of inventing an excuse, and avoid naming your current manager as a reference before an offer. Your record and counting rules work the same, just at a lower weekly volume.

Sources

Share this article

Author Image

HighCircl Editorial Team

The HighCircl editorial team writes about hiring software engineers, nearshore development, and engineering team building. Our articles draw on direct experience sourcing and placing senior developers across Poland, Hungary, Slovakia, Serbia, Slovenia, Romania, and Spain — and on candid conversations with the CTOs and engineering leads who hire them.

HighCircl is a nearshore engineering network that delivers matched candidate shortlists in 72 hours. Every piece of content we publish is informed by real engagement data: actual developer rates, real hiring timelines, and what separates engineering teams that scale cleanly from those that stall.

Take Me to the Experts

Access our network of industry-leading software engineers.

Start Now