How many applications it takes to get an IT job

There is no exact number: it depends on your level, stack and market. But there is a way to work out yours, and to see what exactly to improve.

Think in a funnel

A job search is a funnel: applications → viewed → replies → interviews → offer. Some drop off at each step. If you know your conversion rates, you can see how many applications one offer takes and where the problem is.

What the weak spots mean

Few views: the wrong jobs, or you apply late. Check your filters and apply in the first hours.
Viewed but no replies: the CV or letter is the problem. Check your CV and rewrite the letter.
Replies but no next step: mismatched expectations about salary, English or level.
Interviews but no offer: time to prepare for interviews.

How many to send a day

Steady beats bursts: 5–15 applications a day to jobs that really fit do more than 100 in one evening once a week. Fresh jobs get more recruiter attention, and a daily rhythm keeps you from missing them.

Do not apply to everything: irrelevant applications waste recruiters' time and lower your reply rate.

How to keep count without spreadsheets

Keep at least a note: date, job, status. Or let AutoApply do it: the dashboard shows your 30-day funnel (found, sent, viewed, replied) and which letter templates work better.

For the bigger picture, see the IT job market stats.

FAQ

Is one reply per ten applications normal?

For many markets and levels, that is a common picture. Compare your rate with your own past weeks, not with other people's numbers.

Can sending many applications hurt?

Irrelevance hurts, not volume. Applying to jobs that do not fit you lowers your reply rate.