Duplicate job applications are second submissions to a posting you already applied to, or a stack of applications to one employer that reads as a blast. They do not hide. The systems employers use flag them as duplicates or attach them to a single candidate record, so the same recruiter sees them together, and a growing number of employers switch on rules that block repeats outright. Auto-apply tools make the problem easier to cause, which is why recruiters complain about them. We make ApplyEze, one of those tools, and this page explains the three safeguards it uses against duplicates, in plain terms, along with the cases they do not cover.
Why duplicate applications hurt you
Start with what the recruiter sees. Greenhouse flags a possible duplicate when a new profile matches an existing one. Its merge documentation says that by default the Duplicate tag uses email address, phone number and LinkedIn profile URL, and a site admin can add name. A merge combines the separate applications into one profile, and Greenhouse says plainly: "You cannot un-merge candidates."
Lever is built the same way from the other end. Its help center says that "[e]very candidate in your Lever environment should only have one candidate profile," and each application becomes an opportunity attached to that profile (Lever, candidate profiles and opportunities). If a candidate has more than one active opportunity, a suitcase icon appears on their card in the pipeline.
So a second application to the same posting is not a second chance. It is the same person, appearing twice, in front of someone who already has a lot to read. Greenhouse's Hire Standard benchmarks put applications per job at 116 in 2022 and 244 in 2025, across more than 6,000 companies. Ashby's recruiter productivity report says the average recruiter "is processing 291 applications per hire".
Applying to several different roles at one company is a different question. That is normal, and Lever's whole data model assumes it. The risk is in the pattern. A former recruiter writing for The Muse put it this way: recruiters "tend to remember people who submit applications for multiple roles", and "not always in a good way". Ten applications to unrelated roles at one employer say you have not decided what you want.
Employers now block repeats themselves
All three of the systems below sell employers a way to stop repeat applications. Each one is switched on and tuned by the employer, not by the system's default, so two companies on the same platform can behave differently.
| Greenhouse | Lever | Ashby | |
|---|---|---|---|
| How it knows it is you | Email, phone and LinkedIn URL by default for its Duplicate tag | Email address and the "Job site" source tag, on the same posting ID | Rules the employer scopes to some or all of its jobs |
| What can be blocked | Duplicate applications and how often candidates apply | A repeat application to the same posting within a waiting period | Too many applications in a period; rejected candidates reapplying to the same job or any job |
| Who gets it | Expert-tier customers | Any Lever job site; off by default | Legacy Plus, Plus and Enterprise plans |
| What you see when blocked | Not described in the pages we read | A page saying your application was already received, when you applied and when you can reapply | A message the employer wrote |
Sources for the table: Greenhouse's June 2024 release notes ("Expert-tier customers can build rules to help block duplicate applications") and its application limit rules page, which describes a sales team dealing with "a glut of duplicate applications"; Lever's Blocking repeat applications article; and Ashby's Application Limits documentation.
Two details in the Lever article matter for anyone automating. The default waiting period, once an employer turns the setting on, is 6 months. And the block keys on the posting ID: if an employer closes a posting and opens a new one with the same title, the new one has a different ID and earlier applicants can apply to it.
Ashby went further. When it launched Application Limits in June 2023, it said employers were "seeing a big influx in inbound applications". Its throttling rule caps how many times a candidate can apply to any job in a scope over a number of days. That means a weak application can use up an allowance you would rather have spent on a role you fit. Our guide to Ashby covers those rules in more detail.
Checking history before applying
The first ApplyEze safeguard runs before anything is filled in. ApplyEze normalizes the posting's URL and checks it against your past applications. If the posting is already there, it is skipped.
Normalizing matters because the same job travels under many addresses. A Greenhouse posting reached from a social post might carry a tracking parameter, while the same posting opened from the employer's careers page does not:
https://boards.greenhouse.io/examplecorp/jobs/1234567?gh_src=abc123
https://boards.greenhouse.io/examplecorp/jobs/1234567/
To a plain text comparison those are two jobs. ApplyEze strips tracking parameters, normalizes case and drops the trailing slash before it compares, so both lines resolve to the same posting.
The posting lock
The second safeguard exists because ApplyEze can run up to 10 applications in parallel, each in its own browser window, with 3 as the default. Parallel lanes create a race a single person never has: two lanes could pick up the same posting from the queue at the same moment, before either has finished.
The posting lock closes that gap. A posting being applied to is reserved, so two lanes, or two machines signed in to the same account, do not apply to it at once. Once a posting has been applied to, it is fenced off from being picked up again. Together with the history check, the lock is built to stop double applications.
Employer application limits
The third safeguard handles the employers that set their own caps. For employers that cap applications, such as on Ashby, ApplyEze remembers when an employer has told you that you hit its limit and skips that employer on later runs, rather than sending more applications into a form that will block them.
This one is reactive by design. Ashby does not publish an employer's limits, and each employer picks its own numbers and scope, so there is no way to know the cap before the first block. The block itself is how ApplyEze learns it. Today this works for employers on Ashby.
What recruiters complain about
On 14 October 2026 a corporate recruiter posted in r/recruitinghell asking job seekers to stop using auto-apply tools. When we read it on 17 October it had 333 points and 76 comments. The complaints were specific, and duplicates were not the headline:
- tools that fail to finish the application, leaving sections such as education or work history empty, which makes the candidate look careless,
- applications sent from throwaway email domains that are invalid or never reach the candidate, and
- a generic stock resume attached to every application.
The top replies pushed back. One, with 88 points, said in effect that candidates will stop using bots when employers stop screening with software and AI. Both sides have a point. A separate thread on r/jobsearchhacks made the candidate's version of the same complaint: with most tools there is no way to see what was actually submitted, down to an old job title or a wrong number.
Duplicates belong on that list because they share a cause with everything else on it: software sending applications that nobody looked at. ApplyEze's answer to the visibility part is to run in a browser you can watch, on your own machine, with a dry-run mode that fills the form and never clicks Submit. Every posting gets its own resume, and a cover letter when the form asks for one, so there is no single stock resume.
One thing to check yourself. ApplyEze brings the posting's named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use a dry run to see what it writes, and be ready to discuss anything on the page. A certification the posting asks for is not added unless you hold it. Your employers, job titles, dates, schools, degrees and certifications come from your own record, and code rejects a rewrite that adds a figure, employer, school or credential your record does not hold. A recruiter who sees your profile twice will also notice if the two resumes disagree.
What we do not promise
The safeguards above are built to stop double applications. They are not a guarantee, and the gaps are worth knowing.
- A repost is a new posting. The history check works on the posting's address. If an employer closes a role and reposts it under a new posting ID, it looks new to ApplyEze, exactly as it looks new to Lever's own repeat block.
- The same role in two places may not match. If one job is listed under two unrelated addresses, for example on two different application systems, the two may not be recognized as one posting.
- Applications you sent by hand are not in the history. The check compares against applications made through ApplyEze. If you applied to a job yourself from the employer's site, ApplyEze has no record of it.
- A lock is a reservation, not a permanent record. If a run ends without a confirmed result, the reservation is eventually released so the posting is not stuck forever. In that narrow case a second attempt is possible.
- Different roles at one employer are not duplicates. If several of an employer's roles match your target roles, ApplyEze can apply to more than one. Matches rank by your own target roles first, then fit, so a tight, honest list of target roles is the best control you have.
- Employer limits are Ashby only, and learned after the first block. Limits set on Greenhouse or Lever are not tracked today.
How to avoid duplicates yourself
Whether you apply by hand or with software, a few habits keep your record clean:
- Use one email address everywhere. Lever matches repeat applicants by email, and Greenhouse's Duplicate tag uses email, phone and LinkedIn URL. Switching addresses does not make you a new candidate; it makes you a duplicate someone has to merge.
- Check before you reapply. If you are not sure you applied, look for a confirmation email or the employer's candidate portal first.
- Pick your strongest roles at each employer. Two or three well-matched applications beat ten scattered ones, and at an employer with a cap they may be all you get.
- Reapply to a repost only with a reason. A new posting ID lets you apply again. Do it when something has changed, such as a new skill or a better-fit resume, not by reflex.
For how the rest of an automated search fits together, see how job search automation works. For the wider argument about bots that mass-apply and what separates them, see the job bot guide.