The 6-Month Cooldown: Why Amazon Auto-Rejects Before a Human Reads

You applied to Amazon at 11:58 PM. At 12:07 AM you got the rejection. It felt like an AI read your resume in nine minutes and hated it. It didn't. A rules engine matched your email, phone, or LinkedIn URL against a stored cooldown flag and fired an archive action before a recruiter ever opened the tab.

This piece is about how long you actually have to wait to reapply, what the ATS is matching on, and what has to be materially different on attempt two so the application reaches a human.

The instant midnight rejection is a rules engine, not the AI

Ashby's own documentation is explicit: the AI does not make advance or reject decisions. What fires at 12:07 AM is a recruiter-configured logic rule, usually a knockout answer on a form question or a duplicate-identity match on submit. Ashby's auto-reject emails go out within minutes of the archival action, which is why the rejection lands so fast it feels algorithmic.

That distinction matters because candidates on r/cscareerquestions and Blind are debugging the wrong layer. They rewrite bullets, swap fonts, and buy resume services. None of it touches the actual decision, which happened on identity fields the resume never sees.

Ashby's customer wall is a who's who of the exact companies job seekers target right now:

• OpenAI
• Ramp
• Notion
• Vercel
• Supabase
• Cursor
• Mercury
• Plaid
• Deel

If you were auto-rejected by any of them in under 15 minutes, you hit a rule. A slower rejection, days or weeks later, usually means a human did look.

How long the FAANG cooldown period actually is

Amazon is 6 months for a standard "reject, non-recycle" outcome. Google, Meta, Apple, and Microsoft are typically 12 months. Amazon's "no recycle" flag on L5 and above candidates now runs effectively 24 months per Blind reports, and only a bar raiser can shorten it back to 6 or 12.

Here is the current landscape drawn from Blind, Glassdoor, and Refolk's index of professional profiles:

There is a fourth Amazon state worth knowing: recycle. A recycled candidate was redirected to another team or role, and the cooldown is zero months. That is what "the loop went well but not for this team" looks like on the back end. If a recruiter uses the word "recycle" in a rejection call, do not wait six months. Reapply immediately, to a different org.

Why the ratios force cooldown flags to exist

Cooldowns exist because the pool-to-recruiter math is brutal. Roughly 4:1 at the population level, and far worse per open req once you filter for location and level. A "no recycle" flag is a rational cost-control mechanism, not personal animus. Reapplying identically to the same role wastes both sides' time. Reapplying with a materially different scope, meaning a new team, a new level, or a new demonstrable skill, is what recycle actually rewards.

What the ATS matches on when you reapply

Greenhouse's Duplicate tag matches on email address, phone number, and LinkedIn profile URL by default. Name matching is optional and off by default. Amazon's internal system, according to recruiters posting on Blind, goes further and flags on additional identity signals that swapping an email will not defeat.

The public defaults for the two ATS platforms most likely to auto-reject you:

• Greenhouse duplicate detection: email + phone + LinkedIn URL. Config changes are forward-only, so any profile already flagged in the system keeps its flag even after the recruiter changes the rule.
• Ashby application-limit and blocking rules: recruiter-configured, can be scoped globally across every job at an org on the Enterprise tier. Fires on submit.
• Amazon internal: identity matching well beyond the three fields above. An Amazon recruiter on Blind called it "a very basic ML problem for Amazon."

The practical implication: changing your email will not defeat Amazon. Changing your email, phone, and LinkedIn vanity URL together can present you as a new person in a plain Greenhouse instance, because that is literally what the default rule checks. This is a per-ATS problem, not a universal one.

The referral trap inside Greenhouse

Referrals can silently make your situation worse. Greenhouse's Auto-Merge tool folds a fresh referred application into the pre-existing rejected profile. The referrer sees credit go through. The recruiter sees "duplicate merged" on a flagged record and never opens the new resume. Referral source attribution can be lost inside the merge.

If a friend is about to refer you into a company where you were rejected in the last twelve months, tell them first. Ask them to check with the recruiter whether a prior record exists. A referral submitted on top of a "strong no" flag is worse than no referral, because it burns your friend's referral quota without ever reaching a decision-maker.

What to change on attempt two so it actually reaches a recruiter

Reapplying is an identity and evidence problem, not a formatting problem. The resume rewrite matters, but only after you have handled the flag. Here is the order of operations.

1. Diagnose the flag before you touch the resume

Ask these questions in order:

1. Was the rejection under 15 minutes? Assume a rules engine, not a human.
2. Did the recruiter or interviewer use the word "recycle" on the call? If yes, cooldown is 0 months, apply to a different team now.
3. Was it a phone screen fail or an onsite fail? Onsite fails at Amazon L5+ trigger the 24-month flag more often than phone-screen fails.
4. Is the target company on Ashby, Greenhouse, or an internal ATS? Each has different identity-match behavior.

2. Change what the target ATS actually checks

For Greenhouse-powered targets specifically, the default duplicate rule is public. Presenting as a new person means:

• A new email address, not a plus-alias of the old one.
• A different phone number (a Google Voice line is fine).
• A LinkedIn vanity URL change, not a new account. LinkedIn allows you to edit the URL slug and the old one stops resolving.

None of this works against Amazon, which is why "Amazon 6 month reapply rule" queries keep spiking on Blind. For Amazon, the only durable fix is time plus a materially different scope.

3. Rewrite the resume around what changed since attempt one

The "materially different" bar is real. A bar raiser looking at a recycled candidate wants to see specific new evidence, not a reformatted version of the same story:

• A new title or a step up in scope (IC to tech lead, analyst to senior analyst).
• A new system you owned end to end, named by tool (Kafka, Snowflake, dbt, Terraform).
• A shipped project with a metric attached, dated within the cooldown window.
• A new domain (payments, infra, ML platform) that maps to the target team's charter.

Tailoring the resume to the specific posting is the piece most candidates skip, because doing it by hand for every application is exhausting. That is the exact work Refolk takes off you: paste the posting, get your own resume back rewritten against it, with a fit score that flags the gaps before you submit.

4. Apply to a different team, not the same req

The single highest-leverage move for FAANG reapplicants is changing the org, not just the role. An Amazon Retail rejection does not carry the same weight against an AWS req staffed by a different bar raiser. A Google Ads rejection reads differently to a Google Cloud recruiter. The flag exists, but its interpretive weight drops when the hiring team is genuinely different.

What actually changes between month zero and month six

Between the rejection and the reapply window opening, the honest answer is: your file at Amazon does not change. What changes is you. The candidates who clear on attempt two have measurable new evidence, not a better-worded version of the same evidence.

Concrete moves that read as "materially different" to a bar raiser:

• Shipped a system, not a feature: owned scoping through on-call, not just wrote the code.
• Named a scale number: QPS, dataset size in TB, number of downstream consumers.
• Cross-functional artifact: a design doc, an RFC, a postmortem you authored and can attach.
• Level-appropriate scope: for L5+, evidence of ambiguity resolution, not just execution.

Refolk's fit scoring will tell you plainly whether your rewritten resume clears the bar for the specific posting you are targeting, or whether the gap is still too wide to be worth burning the reapply attempt. Better to know before you submit than to burn another 6 to 24 months on the flag.

The Ashby customer problem for job seekers

Ashby's customer list is disproportionately the companies job seekers want most: OpenAI, Ramp, Notion, Vercel, Supabase, Cursor, Mercury, Plaid, Deel. Which means the global auto-reject rule pattern is going to define reapply behavior at exactly the companies with the tightest headcount.

Benji Encz, Ashby's co-CEO and formerly an engineering leader at Quora, built a rules engine that lets recruiters scope auto-reject globally across every job at the org. On the Enterprise tier, one bad answer to a global knockout question can archive you from every current and future req at the company. That is a much wider blast radius than a per-req rejection.

Two practical implications for anyone applying to that customer list:

• Global knockout questions (visa status, location, years of experience) are worth reading twice. A wrong answer flags you across the entire org.
• If you were auto-rejected by an Ashby customer in under 15 minutes, the flag is likely tied to a form answer, not the resume. Reapplying with the same answers reproduces the same result.

FAQ

How long do I have to wait to reapply after being rejected by Amazon?

Six months for a standard "reject, non-recycle" outcome, zero months if you were "recycled" to another team, and up to 24 months at L5 and above if the bar raiser flagged you "no recycle." The recruiter's language on the rejection call is the tell. If they said "recycle," apply to a different team immediately. If they said nothing specific, assume six months and use the time to ship materially different evidence.

Can I just change my email to defeat the ATS duplicate application auto reject?

For a Greenhouse-powered company, sometimes yes, because the default rule is email plus phone plus LinkedIn URL. Change all three (new email, Google Voice number, new LinkedIn vanity URL slug) and you can present as a new person in a plain Greenhouse instance. For Amazon, no. Amazon recruiters on Blind have said outright that the internal system matches on additional identity signals that a swapped email does not defeat.

Why did I get rejected in nine minutes if a human is supposed to review?

Because a human almost certainly did not review. Ashby's rules engine fires auto-reject emails within minutes of an archival action, and archival can be triggered by an application-limit rule, a global knockout answer, or a duplicate-identity match on submit. Under-fifteen-minute rejections are the rules engine. Rejections that arrive days or weeks later usually mean a recruiter opened the tab.

Does a referral reset the FAANG cooldown clock?

No, and inside Greenhouse it can quietly make things worse. Greenhouse's Auto-Merge tool folds a referred application into the older, flagged profile. Your friend gets referral credit through, but the recruiter sees "duplicate merged" on a rejected record and never opens the resume. Before accepting a referral into a company that rejected you, ask the referrer to check with the recruiter whether a prior record exists on file.