Never Apply to the Same Job Twice

Somewhere around week five, most people applying at any volume send the same application twice. Usually to the same role at the same company, arriving from two different routes, three weeks apart.

Nothing catastrophic happens. It’s just a small, visible signal that you’re not paying attention to what you’re doing — which is the one impression an operationally run search should never give — and occasionally it’s worse than that, when two agencies are involved and the employer now has a question about who introduced you.

It’s also completely preventable with about ten seconds of process per application.

The four ways it happens

Aggregation. The same posting is syndicated across several boards, sometimes with a different title, sometimes with a different reference number, sometimes with the employer name replaced by a recruiter’s. You genuinely don’t recognise it as the thing you applied to in June.

Reposting. The employer refreshes the advert. Same role, new date, new reference. Your feed presents it as new because, mechanically, it is.

Two routes. You applied through a board; a recruiter then puts you forward for the same role. Or you applied directly to the careers page and an agency pitches you a week later. This is the version with real consequences, and the prevention is in recruiters as part of your pipeline.

Bulk submission. Tools that submit on your behalf have no reliable way of knowing you already applied, and duplication scales with volume — which is one of the concrete costs in when to use auto-apply tools, and when not to.

Notice that none of these are memory failures on your part. They’re all cases where the same thing shows up wearing different clothes. Which means the fix has to be a lookup, not an effort to remember harder.

The dedupe key

You need a short string per application that identifies the role, independently of where you saw it. Company plus role plus location, normalised:

northwind | senior analyst | manchester

Normalising means: lowercase, drop the legal suffixes (Ltd, Inc, GmbH, plc), drop the seniority decorations that vary between adverts ((m/f/d), - Hybrid, II, #4471), and reduce the location to a city or “remote”. You’re not trying to be exact, you’re trying to make two adverts for one job produce the same string most of the time.

Put it in a column. In a spreadsheet you can build it from the columns you already have, or just type it — it takes five seconds and typing it is what makes you look at it.

Then the check is a search. Before you submit anything, search your tracker for the company name. Not the key, the company — a plain substring search on company name catches everything the normalised key would plus the cases where the role title was rewritten beyond recognition.

Wire the check into the applying block

Ten seconds, at the top of every application:

Search the tracker for the company name.
Look at what comes back: previous applications, rejections, and cooling-off state.
If there’s a hit on the same role, stop. If there’s a hit on a different role at the same company, read the note before proceeding — see reapplying to a company that said no.
Add the row before you start writing, not after you submit.

That last item matters more than it looks. People add the tracker row after submitting, which means an application abandoned halfway leaves no trace, and a fortnight later you start it again. Create the row when you begin, with status Applying, and the half-finished attempt is visible.

Reposts: the ambiguous case

You applied six weeks ago, heard nothing, and the identical role is advertised again. Is that a duplicate or a new opportunity?

You can’t tell from outside, and it depends on why it was reposted — a stale advert refreshed while the original process runs, a process that restarted, a second headcount, or an advert that was never really live. What you can do is take the cheaper action.

If you had human contact, message that person rather than reapplying. Two lines asking whether it’s worth putting yourself forward again resolves the ambiguity and reads better than a second identical submission.

If you had no contact and it’s past your ghost cutoff, applying again is defensible. Log it as a second row, linked to the first, with a note that it’s a repost. The link is what keeps your response-rate numbers honest — two rows for one opportunity inflates your denominator and makes your conversion look worse than it is.

If it’s within a couple of weeks of your first application, it’s the same advert. Leave it.

Sibling roles at the same employer

A related judgement call: three similar roles at one company, all open, all plausible.

Applying to all three is generally counterproductive. Where applications at a company are visible to the same recruiting team — which is common — three simultaneous applications read as indiscriminate rather than enthusiastic, and it undermines the specificity that made any one of them credible.

Pick the best-fitting one and apply to that. If you genuinely can’t choose between two, that’s a good use of a short question to the recruiter: “there are two roles advertised that both look close to my background — is one a better fit than the other?” This is a normal question and the answer is frequently useful, since they know things about the two teams that the adverts don’t say.

The exception is genuinely unrelated roles in different parts of a large organisation, months apart. That’s not a pattern anyone will notice or mind.

The company-level view

The underlying fix for all of this is being able to see a company rather than a list of applications.

Once your tracker has a few dozen rows, add a filtered view grouped by company — every row for one employer, in date order, with outcomes. It takes a minute to set up and it answers, at a glance, the four questions that prevent every error in this post: have I applied here, when, what happened, and who did I speak to.

That view plus the ten-second search before submitting is the whole system. It’s a trivial amount of process, and it removes an entire class of avoidable mistake — the kind that costs you nothing in effort to prevent and, in the recruiter-collision case, can cost you a role you were otherwise in the running for.