Should you apply to the same company twice? What the ATS does

Short answer: yes, apply to the same company as many times as there are jobs you can genuinely do. The two things that cost you are a repeat application to the same requisition, which some employers auto-reject, and a second application filed under a different email address, which no system treats as a fresh start.

The rest of this is the mechanism - what the applicant tracking system does with your name the second time it sees it, which of those behaviors are on by default, and which ones the employer had to switch on deliberately.

What happens when your name shows up twice

Both major systems assume duplicates and are built to collapse them. Greenhouse flags what it calls a Duplicate tag "when a new person matches an existing person on any of the selected criteria" - name, email, phone number, or LinkedIn profile URL, whichever combination that company enabled. Email, phone and LinkedIn are on by default in Greenhouse; name is the one an employer has to switch on. Workday is stricter about the match and looser about the consequence: it merges automatically when "their First Name and Last Name are exact matches and at least 1 of these fields is an exact match: Phone Number, Email Address, LinkedIn URL, X User Name, Facebook URL, Google+ URL."

Read those two rules and the practical conclusion is the same. You do not get a second identity. You get a second application attached to the record you already have.

How two ATS handle the same person applying twice

Greenhouse's Duplicate tag is a flag a recruiter clicks; Workday's automatic merge happens without anyone looking. The Workday page does not say whether a candidate merge can be reversed.

	Greenhouse	Workday
What counts as a duplicate	A match on any one selected field: name, email, phone, or LinkedIn URL	First and last name both exact, plus one exact match on phone, email, LinkedIn, X, Facebook or Google+
Merged automatically?	Only where auto-merge is switched on, matching email or phone	Yes, unless one of the records has a registered Candidate Home account
Records it will not merge	Anonymized profiles, agency submissions, referrals, confidential jobs and private prospects	Internal candidates and workers; only external candidates and pre-hires merge
Can the merge be undone?	No - "You cannot un-merge candidates"	Not addressed anywhere on the documentation page

That Workday exception is the one worth memorizing. If you created a Candidate Home account - the login where you can see your applications - Workday "doesn't automatically merge 2 candidates if at least 1 of them has a registered Candidate Home account." So the applicant who logs in and applies again through the portal is one clean record. The applicant who applies twice as a guest, with two spellings of their own name, may be two.

Does a second application to the same job get auto-rejected?

Sometimes, and only because the employer chose it. Greenhouse gives companies two levers: a frequency cap, where the employer enters "the number of applications a candidate can submit, and then enter the number of days they have to submit those applications," and a cooling-off period, where they "specify the number of days that must pass before a rejected candidate can submit another application." When an application breaks either rule, it is "automatically moved to the 'rejected' category and marked as 'blocked by auto reject rule'." Telling you is a checkbox - "Send a rejection email to affected candidates" - which means the auto-reject can also happen in silence.

The detail that catches people out is the scope. The employer picks which departments a rule covers, and Greenhouse then applies it to "all jobs within those departments." So the frequency cap is not only a same-requisition rule: a Data Engineer who fires off four applications to four postings inside one company's Data department in a week can trip a limit written for repeat applicants to a single job.

So a rejection that arrives before anyone could plausibly have opened your application is not a score on your resume. It is a counter.

Two openings, one company: the case that always works

This is the situation people worry about needlessly. A Data Engineer partway through the interview loop for a platform data role sees a second posting for an analytics data role at the same company, and hesitates in case the second application looks scattered.

Greenhouse documents exactly what happens: when a candidate is active on Job A and applies to Job B, the applications merge and the candidate information from Job A is retained, "ensuring the original hiring team maintains visibility." The first team does not lose you. The second team gets a profile with an interview history already on it, which is better than a cold submission, not worse.

Those five rows are Greenhouse's published behavior, not a general law of applicant tracking systems. Workday's documentation covers when records combine, not which application's data wins, so do not assume the same table describes a Workday employer.

What the merged profile looks like from the recruiter's side

One record, thicker than either of the two that went into it. Greenhouse lists what gets combined when profiles merge: "Data in the activity feed, Scorecards, Attachments, Phone number, Email, Social media links, Websites, Address, Education, Candidate tags." Fields that can only hold one value - source, recruiter, coordinator, referral, current company and title - do not merge at all. Greenhouse "will prioritize data from the primary candidate if it conflicts with the duplicate candidate profile," and the primary is whichever record the person doing the merge designates, not automatically the older one.

That matters more than it sounds. If your first application came in through a referral and your second came in cold from the careers page, only one of those two sources survives, and which one it is comes down to a choice made in a dialog box you will never see. What does survive from both is the history: the merged record carries the activity feed and the scorecards from interviews you already sat.

There is a cost on the employer's side that explains why some of them turn on application limits in the first place: Greenhouse warns that merging "may cause downstream integration errors," because the candidate ID of the profile marked secondary "will not be displayed in-app or within the API," and that scheduled interviews on the non-primary profile "will need to be manually updated for the merged candidate." Duplicates are not a moral failing on your part. They are administrative work on theirs, which is why the tooling is aimed at collapsing them rather than punishing them.

Is the second application better spent somewhere else?

Here is the position, and it is one you can argue with: for most people, the second application at the same company is worth less than the first application at a different one, and the reason is pay bands rather than etiquette.

Take the Data Engineer above. The Bureau of Labor Statistics reports a median annual wage of $139,500 for database architects - the occupation whose reported job titles include data engineer - as of May 2025, with the lowest 10 percent under $86,240 and the highest 10 percent above $204,000. That is a spread of more than $117,000 inside one job title. Where an employer sits in it is mostly a function of what that employer does for a living.

Median annual wage for database architects by industry, May 2025

The same occupation, five employer types. The gap between the top and bottom of this list is larger than most negotiated raises.

Computing infrastructure, data processing, web hosting		$152,560
Administrative and support services		$149,490
Computer systems design and related services		$148,680
Finance and insurance		$146,470
Management of companies and enterprises		$139,320

A second application at the same employer keeps you inside that employer's band. A first application at a different employer type moves you between bands. BLS counted 69,500 database architect jobs in 2025 and projects 9 percent growth over 2025–35, so the second door exists.

The hiring bar usually does not move between those doors either, which is the other half of the argument. O*NET reports that 76 percent of database architects hold a bachelor's degree and 14 percent a master's, and rates the occupation Job Zone Four - considerable preparation needed. A Data Engineer who clears that bar at one company clears it at the next, so the effort of a fresh application is mostly the form, not the qualification. Reapplying at the company that already said no is the expensive option disguised as the cheap one.

What this does not tell you is the thing you would most like to know: whether your target company pays above or below its industry median. BLS publishes occupation-by-industry medians, not company salary structures, and the five industries above are national figures with no adjustment for where you live. The chart bounds the question. It does not answer it.

If you were rejected from that job before

Then assume the recruiter can see it. Greenhouse merges the profiles when a rejected candidate applies again to the same job and preserves "every application" for the record, which means your new submission arrives stapled to the old outcome.

Reapplying to the identical requisition after a rejection is the weakest move available to you, because nothing in the record has changed except the date. Reapplying to a different requisition after a rejection is a different thing entirely, and Greenhouse's own handling reflects it: in that case the merge uses the newer job's candidate information "as the original team is no longer involved." A Data Engineer rejected for a staff-level platform role in March, applying to a mid-level analytics role in September, is not repeating themselves. They are answering a different question.

If you apply under a second email address

Don't. A second email is an answer to the question "how do I get around their record of me," and the record is keyed on your name, not your inbox.

Look at what a second email actually has to defeat. Workday needs the first and last name to match exactly and one of phone number, email, LinkedIn URL, X user name, Facebook URL or Google+ URL. Change the email and keep the phone number, and it still merges. Keep the LinkedIn URL, and it still merges. To break the match on purpose you would have to change your name and every contact field on the form, which is no longer a second email address - it is a different person on a legal document.

Greenhouse is looser and that is worse, not better, because it is unpredictable. Name is the one duplicate criterion Greenhouse ships switched off, so at some employers the second profile arrives unflagged and stays a separate record until somebody searches your name. Then it gets merged by hand, and Greenhouse is blunt about what that costs: "you cannot un-merge candidates." Whatever the merge decides to keep - one source, one recruiter, one referral - is what the record says about you from then on, permanently, and nobody asks you which version to keep.

How long should you wait before reapplying?

Nobody publishes a number. The six-month rule you keep reading is folklore - no ATS vendor's documentation contains it, and no employer is bound by it. What actually exists is a per-employer setting: Greenhouse asks the company to "specify the number of days that must pass before a rejected candidate can submit another application," and whatever they typed there is not visible to you, not disclosed in the posting, and not standard across companies.

The honest version is that the clock you should watch is the job's, not yours. Companies hire continuously - BLS recorded 5.1 million hires in July 2026 against 7.3 million job openings - so the practical trigger for a second application is a new requisition, a changed scope, or a year of work you did not have last time. Not a date on a calendar.

What to write when the form asks if you have applied before

Answer it, and answer it exactly. A blank on this field is an answer, and it is the wrong one, because the system already knows and the only variable is whether you did.

For a Data Engineer applying to a second team at a company that rejected them earlier in the year:

Have you previously applied to or worked for our company? Yes - I applied for the Senior Data Engineer role in March 2026 and was not selected. Since then I have shipped a streaming ingestion pipeline in production and I am applying here because this role is closer to analytics modeling than the earlier one.

Two facts and a reason. No apology, no explanation of the earlier rejection, and no claim about why it happened, since you were not in the room.

The one thing to get right

Use the same email address and the same spelling of your name on every application to that company, forever. That is the whole discipline. It is what makes the merge clean, keeps one profile with a real history instead of two thin ones, and stops a recruiter's first impression from being a duplicate flag.

If retyping the same identity into a fifth Workday form is what makes you sloppy about it, the platform fills those fields from your resume so the name and email you submit are identical every time.