The Prior-Rejection Reapply Score, Six Dimensions to Reapply, Rework, or Wait

A company that already turned you down has posted a role you want, and you need to decide whether to apply now, change something first, or hold off until a specific week. This guide is for job seekers applying to many companies at once, who face this call often enough to need a standard way of making it. It gives you six dimensions you can score from evidence you can check yourself, a decision rule that turns those scores into Reapply, Rework or Wait, and a calendar date to put in your tracker.

Why a fixed waiting period is the wrong answer

No single waiting period is right. The published advice contradicts itself, and most employers publish no reapplication window at all. The useful question is not "how long", but "what has the employer said, and what has changed since?"

The pages that rank for this question each give one rule of thumb, and the rules disagree. Some say a resume-screen rejection needs no wait at all. Others say three months, and many say three to six. Tables of big-tech "cooldown" periods get copied from page to page, but the Amazon, Google and Meta claims on those pages have no primary source behind them.

When an employer does publish a window, it is narrow and specific. Two primary examples:

• Pinterest, on its application confirmation page: "We ask candidates to wait at least six months from their last application before reapplying to the same role at Pinterest." The window covers one role, and the same page invites applications to other roles.
• San Bernardino County, in its HR FAQ: "a six (6) month waiting period to re-apply for the same job (title and level)." The window covers one title at one level.

I have not built a sample of reapplication windows across dozens of employers, and I found no published audit that has. So I will not tell you what share of employers set a window. If you want that number for your own target list, build it by hand from each employer's own pages.

The bigger problem with a fixed wait is that, for most rejections, time is not what decides the outcome.

Most of those early rejections run on structured screening answers and stated requirements. Waiting three months does not change a "no" on a required license. Changing the answer, with evidence, does.

Time does not reset a knockout. Only a truthfully different answer, backed by evidence, does.

What does the employer still have on file when you reapply?

Assume your earlier application is still on file. US private employers must keep applicant records for at least a year, and the applicant tracking system (ATS, the software that receives and routes applications) will usually link a new application to your old profile by email. Plan the reapplication as a second look at the same file, not as a first impression.

How the common ATS platforms handle a returning candidate

Greenhouse's help docs list "Application questions" as application-specific information. The vendor docs I found do not say whether a recruiter can see the knockout answers from your earlier application. Treat that as unknown, not as "no".

Lever's block is real in practice. An open-source job-search project documented a Lever posting returning "already received" for an application made six months earlier.

Retention floors, the minimum time the record must exist

An OFCCP "large contractor" is one with 150 or more employees or a contract of $150,000 or more. California's four years comes from SB 807. The GDPR sets no number, and UK practice anchors to the six-month window for bringing a claim under the Equality Act 2010.

These are floors, not caps. Because the clock runs from the later of the record or the personnel action, a three-to-six-month wait lands well inside even the shortest US floor.

Which ATS you are likely to face

Which duplicate rule applies to you depends on which ATS the employer runs, and that varies by market and company type.

In Refolk's index, the Greenhouse sample leans towards tech companies such as Meta and Snowflake, and the Workday sample leans towards large enterprises such as Boeing and Siemens. For Greenhouse, the US count is 25.8x the UK count. People under-report skills on their profiles, so read these counts as direction only. Confirm the ATS for a specific employer from the domain of its application URL.

The six dimensions and how to score each

Stage reached is a class, not a colour: it sets the bar that the change in your record must clear. The other five dimensions each get Green, Amber or Red against fixed definitions, so two people scoring from the same evidence reach the same answer.

Dimension 1: Stage reached, which sets the change bar

What it proves: how much human judgement is on file, and so what kind of change will count. How it lies: an instant rejection looks like a resume rejection when it was really a knockout (an automatic rejection triggered by a screening answer).

One timing trap: LinkedIn auto-rejection messages arrive three calendar days after you apply, and they need at least one "Must-have" question on the posting. A three-day delay on a LinkedIn application with Must-have questions can still be a knockout.

The later the stage, the more specific the bar. Published passthrough rates show why:

The vendors use different denominators, so do not multiply these rows together. Each row only tells you how selective that one step is. Only about 24% pass the onsite, and the people who reached it were judged by interviewers who wrote notes. Your next attempt will be read against those notes.

Dimension 2: Stated window

What it proves: whether the employer has said in writing that you cannot apply yet. How it lies: a window copied from a third-party table looks official but has no primary source behind it.

• Green: the employer's own pages state no window, or the window has passed, or its stated scope excludes this posting.
• Amber: a window exists but its scope is unclear, for example "same position" with no title or level. Treat it as Red unless the recruiter signal (Dimension 6) confirms you are eligible.
• Red: the employer's own words state a window that covers this posting, and it has not passed.

Dimension 3: Requisition ID

What it proves: whether the system will accept your submission at all. How it lies: a new ID looks like a fresh start, but the employer can still link your profile by email. A new ID removes Lever's block. It does not remove the recruiter's memory.

• Green: a different role, with a different title or team, under a new posting ID.
• Amber: the same title reposted under a new ID. Lever documents that a repost gets "a different posting ID (even though the title is the same)", which lifts the block. You can submit, but the full change bar still applies.
• Red: the same posting ID, or the portal blocks you.

To compare IDs, read the number in a Greenhouse job-board URL (such as /jobs/7132897) or the Lever posting ID. How often reposts carry a new ID has not been published, so check every time.

Dimension 4: Stored knockout answers

What it proves: whether the automatic rule that rejected you will fire again. How it lies: changing an answer without evidence feels like a fix, but it creates a contradiction sitting next to the old answer on file.

• Green: no knockout caused the rejection and your answers are unchanged, or a knockout caused it and that answer is now truthfully different, with a dated proof.
• Amber: you cannot see what was stored, and the rejection was not a knockout.
• Red: a knockout caused the rejection and the answer is truthfully the same, or you suspect you answered wrongly by mistake and the application has not been reset.

Dimension 5: What has changed in your record

What it proves: that the next reviewer has a reason to decide differently. How it lies: a reworded resume reads as new but carries the same evidence, so you get the same outcome.

• Green: a dated, verifiable change that clears the change bar for your stage.
• Amber: a real, dated change that does not address the bar, for example a new certificate when the onsite feedback was about system design.
• Red: nothing has changed except the wording.

For a different role at the same company, the bar resets only where the earlier reason does not apply. A work-authorization knockout follows you to every role. A requirement specific to the old role does not.

Checking whether a change actually shows up against the new posting is tedious to do by hand. Refolk writes the resume from your own history and scores how well you fit the new posting, so you can see whether the requirement you missed last time now appears with evidence behind it, or whether you have only changed the wording.

Dimension 6: Recruiter signal

What it proves: what the employer has told you directly. How it lies: polite boilerplate reads like an invitation.

• Green: a written, specific message, such as an eligibility confirmation, a named role, or "reapply after" a stated date that has now passed.
• Amber: no request sent, no reply after 10 business days, or only boilerplate like "keep an eye on our careers page".
• Red: a written statement that you are not eligible until a date that has not yet arrived.

How the scores become Reapply, Rework, or Wait

Apply four rules in a fixed order and stop at the first one that fires. Timing gates come before content gates, because a strong change submitted into a blocked posting is wasted.

1. Wait, if Dimension 2, 3 or 6 is Red (an Amber window counts as Red until confirmed). Date: the latest of the window end (your last application date plus the stated window) and any date the recruiter named. If the only Red is a same-ID posting, use the date of your next scheduled careers-page sweep for a new ID.
2. Rework, if Dimension 4 or 5 is Red. Date: the day the change will exist with proof (exam result, project shipped, licence issued), or the day you send a reset request for a mistaken knockout answer.
3. Rework, if Dimension 5 is Amber and the stage reached was recruiter screen or onsite or final. Date: the day the change that meets the bar will be documented.
4. Reapply, if none of the above fire. Date: the day you submit, within the current week.

The same logic as a two-variable picture:

Two worked cases

Case A. You were rejected minutes after submitting. The new posting has the same title under a new ID, no window is published, and you still do not hold the licence the posting requires. Dimension 3 is Amber and Dimension 4 is Red, so Rule 2 fires: Rework, dated to the day your licence result arrives.

Case B. You were rejected after an onsite, and the feedback named one gap. The confirmation page states a six-month window for the same role, and the new posting is a different role. Dimension 2 is Green because the scope excludes this posting, and Dimension 3 is Green. If you have since shipped a dated project that addresses the gap, Dimension 5 is Green and Rule 4 fires: Reapply this week. If your only change is an unrelated certificate, Dimension 5 is Amber and Rule 3 fires: Rework.

Step-by-step: scoring one prior rejection

The procedure takes about an hour of desk time, plus however long the change in your record takes to make and up to 10 business days of waiting for a recruiter reply. Run it once for each earlier rejection, and finish with a dated tracker entry.

The 10-business-day cutoff in step 7 is my own working rule, not a published benchmark. Nobody has published response rates for eligibility or feedback requests.

Use one row per prior rejection. Filling in every field is what lets a second reader check your call.

Company: [name]   ATS: [Greenhouse / Lever / Workday / Workable / other]
Old posting ID: [id]   Applied: [date]   Rejected: [date]
New posting ID: [id]   URL: [url]
Stage reached: Knockout | Resume screen | Recruiter screen | Onsite or final
Change bar: [one sentence]
D2 Stated window: G | A | R   Quote: "[exact words]"   Source: [page]   Scope: [role / title and level / company / none]   Ends: [date]
D3 Requisition ID: G | A | R   Old vs new: [same / new, same title / new, different role]
D4 Knockout answers: G | A | R   Question: [text]   Old answer: [x]   Now: [y]   Proof: [document, date]
D5 Changed record: G | A | R   Change: [what]   Dated: [date]   Proof: [link or document]
D6 Recruiter signal: G | A | R   Message: "[exact words]"   Received: [date]
Rule fired: 1 Wait | 2 Rework | 3 Rework | 4 Reapply
Decision: [Reapply / Rework / Wait]   Date: [calendar date]

When the decision is Reapply, the next job is matching the application to the new requisition rather than resending the old one. Refolk tailors the resume and drafts the cover letter for that specific posting, so the change you documented in step 6 appears where the reviewer will look for it.

How the reapply call goes wrong

Most bad reapply calls come from evidence that looks solid and is not: borrowed windows, misread stages and a new ID mistaken for a clean slate. These eight failure modes cover what I see most often. Check your scored row against each one before you act on it.

1. A borrowed window. A cooldown period from a third-party table looks authoritative but has no primary source. Check: quote only the employer's own email or page, or score Dimension 2 as "none published".
2. A window applied too widely. "Six months" may cover only the same title and level (San Bernardino County) or the same role (Pinterest). Treating it as company-wide wrongly blocks you from other roles. Check: copy the scope words into the tracker next to the window.
3. A new ID read as a clean slate. The same title under a new ID reads as a fresh chance, but the employer may still link your profile by email. Check: a new ID only moves Dimension 3 to Amber or Green. Dimensions 4 and 5 still have to pass.
4. An instant rejection misread. An instant "Not Selected" gets read as a resume rejection when a knockout answer caused it. Check: a timestamp minutes after you submitted means a knockout. Ask for a reset instead of reapplying.
5. A second account to change an answer. A new account creates a duplicate profile. Greenhouse can auto-merge profiles that share an email and keeps the oldest, so your old answers sit next to the new ones.
6. A retention floor treated as a deletion date. The one-year, two-year and four-year figures are minimums. The absence of a published cap does not mean your record is gone.
7. Rewording treated as change. A reworded resume is not a change. If no knockout answer or credential differs, the same outcome repeats. Check: Dimension 5 needs a date and a proof, not new adjectives.
8. Boilerplate read as an invitation. A polite "keep an eye on our careers page" is boilerplate (it appears on Pinterest's confirmation page). It scores Amber, never Green.

Where practitioner advice disagrees on order

Two published approaches change the order of the procedure, and both lose information. CodeBegun says to wait until the gap is closed, not for a set time, which puts step 6 before step 2. That is right about content but skips the employer's stated window. Rednax says to reapply immediately if the job reopens, which skips steps 5 and 6. That is right about timing but resubmits the same evidence. The scored order keeps both: timing gates first, then content.

Asking recruiting for an eligibility check or a knockout reset

Send one short written request when a single answer would settle an Amber: a window with unclear scope, or a knockout answer you got wrong by mistake. Ask one question, cite the IDs, and state one dated change.

Nobody has published response rates for these requests, so do not plan around getting a reply. Send the request, set the 10-business-day cutoff, and score Dimension 6 as Amber if nothing comes back. A written yes moves Dimension 6 to Green and can clear an Amber window. A written "not until" is Red, and that date becomes your Wait date.

Subject: Eligibility question, [new role], requisition [new ID]

Hi [name],

I applied to [old role] (requisition [old ID]) on [date] and was not selected at the [stage] stage. You have now posted [new role] (requisition [new ID]). Before I apply, could you confirm whether I am eligible, and whether any waiting period applies to this posting? Since my last application, [one dated, verifiable change].

On my [date] application I answered "[screening question]" as [answer given], which was incorrect. The accurate answer is [correct answer], and [proof] confirms it. Could the application be reset rather than my creating a new account?

Thank you,
[name]
[email used on the original application]

Send it from the email address you used on the original application. A different address makes the request harder to match to your record, and it is the same mistake as creating a duplicate profile.

Keeping the call current

A Wait or Rework call is a dated prediction, not a permanent verdict. Score the row again when its date arrives, or sooner if something changes. Old scores go stale in specific, predictable ways.

Score again when any of these happen:

• The window end date arrives (Dimension 2 may turn Green).
• A new posting ID appears for the role you were waiting on (Dimension 3).
• Your proof arrives: a licence result, a shipped project, a completed credential (Dimensions 4 and 5).
• A recruiter replies, or the 10-business-day cutoff passes (Dimension 6).
• The employer changes its careers FAQ or confirmation page wording. Quote the new version, not your memory of the old one.

If you rely on the OFCCP contractor floor, confirm its current status in the Federal Register each time you cite it. The time-sensitive parts of this standard are mechanisms you check again, not values you memorise.