How Long a Job Search Actually Takes, and What to Do in the Meantime

The most damaging thing about a job search is not the rejections. It is the absence of a baseline — no way to tell whether four weeks of silence is normal or a sign that something is wrong. In that vacuum most people conclude the problem is them, stop applying at the rate they were, and make the search longer.

So: some arithmetic, and three checkpoints that tell you what to actually change.

Realistic timelines

Broad ranges, for the Indian market, from starting to apply seriously to holding an offer:

Two adjustments. Searching while employed is slower in elapsed time and easier in every other way. And the process itself — from first call to offer letter — runs two to six weeks at most Indian companies and considerably longer at large MNCs, banks and anywhere with a global approval chain. That is on top of the time spent finding the process to enter.

If you have been at it for three weeks and are anxious, you are inside the normal range and there is nothing to diagnose yet.

The funnel, with numbers

Rough orders of magnitude for a mid-level candidate with a reasonable resume applying to reasonably matched roles:

• 100 applications through portals →
• 5 to 15 recruiter responses →
• 3 to 8 first-round interviews →
• 1 to 3 processes reaching final rounds →
• 1 offer, sometimes.

That top-of-funnel conversion — around 5 to 15% — is the number that shocks people, and it is not a comment on your ability. It reflects roles already filled internally, postings left up after closing, consultancy listings that were never real, and hundreds of other applicants for the same URL.

Two things change these ratios more than anything else:

Referrals. A referred application converts at a dramatically higher rate — often one in three gets a conversation. This is why the same candidate can send 200 cold applications and 15 referral requests and get more interviews from the second. The mechanics are in how to get a referral when you do not know anyone.

Match quality. Applying to 30 roles you genuinely fit outperforms 200 sent indiscriminately, because the interview time you save is the scarce resource, not the application time.

What a week should look like

The failure mode of an unemployed search is doing it all day and burning out in three weeks; the failure mode of an employed search is doing it only when frustrated. Something structured beats both.

A workable week, roughly twelve to fifteen hours:

• 10–15 applications, matched, with the ten-minute tailoring pass from ATS keyword matching. Not 100 with no tailoring.
• 5 referral or recruiter messages, specific to a named role.
• One preparation block — the format-specific work in preparing for a technical interview, or your stories for the HR round.
• One skill block — the project or certification that will still be true in three months.
• A record of every application in a spreadsheet: company, role, date, source, status. Unglamorous and it is what makes the checkpoints below possible.

And a hard stop. A search conducted at every waking moment produces worse interviews, because you arrive at them exhausted and slightly desperate, and both are legible.

The three checkpoints

This is the useful part. Each stage of the funnel fails for different reasons, and the fix is different.

Checkpoint 1 — 30+ applications, no recruiter responses

The problem is upstream: the resume, the match, or the channel.

• Match. Be honest about how many of those 30 you genuinely fit. Applying to roles requiring five years with two years of experience produces exactly this pattern.
• Resume. Does it parse, and does it contain the words in the posting? Copy your PDF into a plain text editor and look at what comes out. The resume guide covers the content; ATS keyword matching covers the search.
• Channel. If everything went through one portal's Easy Apply, that is not a search, it is a lottery. Add referrals and direct company career pages.
• A second pair of eyes. One person who has screened resumes, fifteen minutes. This surfaces things you cannot see in your own document.

Checkpoint 2 — interviews happening, none progressing past the first round

The resume is working. Something in the room is not.

• Which round are you losing? First technical, HR, or final? The pattern is the diagnosis.
• Losing the first technical round usually means preparing for the wrong format, which is extremely common. Ask the recruiter what the rounds cover.
• Losing on "tell me about your work" means you have not written out your own projects. This is the cheapest fix available and almost nobody does it.
• Losing at HR after clearing technical rounds is usually the leaving-reason answer, the salary conversation, or notice-period friction. The HR round, question by question.
• Ask for feedback. Most companies give none, some give a sentence, and a sentence is enough to spot a pattern across four rejections.

Checkpoint 3 — reaching final rounds, no offers

The most frustrating position and usually the closest to done. Common causes, in order:

• Compensation mismatch discovered late, because nobody discussed the band early. Fix by asking for the range in the first call.
• You were the second candidate. Genuinely common at this stage and not a defect — it means your profile is right and you need more processes running in parallel, not a different profile.
• Notice period. A ninety-day notice against a role that needs someone in four weeks loses to a candidate on thirty days. Know your buyout position before it comes up: notice periods and relieving letters.
• Something in the final conversation. Often the questions you asked, or did not. What to ask the interviewer.

At this checkpoint the answer is usually volume rather than change. Three final-round processes running simultaneously produces an offer far more reliably than one at a time, and it also produces a better one.

Seasonality, which is real in India

Not decisive, but worth knowing. Hiring generally picks up from January through March as new budgets open, is reasonable through the middle of the year, dips around the appraisal cycle in April–June at companies that freeze external hiring during it, and slows in late December. Campus hiring runs to its own calendar entirely.

None of this should stop you applying in a slow month. It should stop you concluding from three quiet weeks in December that your resume is broken.

Keeping it survivable

The practical points that people who came through a long search mention afterwards:

Track everything. The spreadsheet is what turns "nothing is working" into "I have had 40 applications and 2 responses, so the problem is upstream". Anxiety cannot be argued with; a funnel can be diagnosed.

Keep one thing that is not the search. Something with visible progress — a project, a certification, teaching someone, a physical routine. A search gives you no feedback for weeks at a time and that is corrosive without a counterweight.

Do not tell everyone and then avoid everyone. The narrowest version of this — telling six people you trust, specifically, what you are looking for — is also the most useful, because that is where referrals come from.

Set a floor, not a target. "Ten applications a week" is achievable on a bad week. "An offer by October" is not something you control, and missing it feels like failure when it may simply be the market.

Take the interview even when you are not sure. Interviewing is a skill that decays, and a process you do not particularly want is the cheapest place to practise the salary conversation.

And if the search runs long enough that money becomes the constraint, a contract or short-term role is a legitimate move rather than a defeat — it restores a current employer on your resume, which measurably changes how the next set of applications are read.

Current openings are here, including fresher roles and remote positions.