Amazon's RTO Compliance Number Hides Your Best Senior Pool

Amazon's 5-day RTO has been running since January 2, 2025, and the public narrative is that compliance is high and the drama is over. It isn't. The small slice that hasn't quietly conformed is disproportionately L6 and L7 ICs with leverage, mortgages in the wrong city, and zero interest in flipping on the green "Open to Work" badge.

If you're sourcing senior engineers right now, that's your pool. And it has a shelf life.

The compliance number is a recruiting input, not a closed story

Andy Jassy's September 16, 2024 memo set the five-day mandate. Twelve months in, reporters like Eugene Kim at Business Insider and Matt Day at Bloomberg have steadily surfaced the internal Slack channels, badge-data dashboards, and manager-level compliance trackers that leadership uses to grade teams. The headline framing inside Amazon is that the policy "worked." Most people came back.

That framing is correct and useless. The interesting number for a recruiter is not the majority. It's the minority who stayed home, stayed senior, and stayed quiet.

A widely cited Blind survey from September 2024 reported that roughly 73% of Amazon employees said they were considering looking for a new job after the RTO announcement. A year later, almost none of those people show up on a "#opentowork" filter. Senior ICs with total comp north of $400K don't broadcast availability. They take warm intros during a two-month exploratory window once a year, and then they go dark again.

73%

Who the non-compliant minority actually is

The lazy assumption is that the holdouts are entitled juniors. The opposite is true. Junior engineers can't afford to defy a return mandate. L6 and L7 ICs with 8+ years of tenure can, because they have:

• Political capital with skip-level managers who don't want to lose them.
• RSU vest cliffs they're willing to walk away from but would rather not.
• Two-body problems. A working spouse, a school year mid-stream, a mortgage in Frisco or Herndon or Bellevue's eastern edge.
• Manager relationships that quietly accommodate three-day weeks or "I'll be at re:Invent" cover stories.

This is the cohort that drives regrettable attrition in internal dashboards. Leadership watches L6+ regrettable separately from everything else for a reason.

RTO non-compliance hiring starts with geography

The cleanest public signal is location. Refolk's index currently returns 2,727 senior+ profiles in the US matching AWS keywords with Amazon Web Services as the top current employer. Six of the top ten geos are Seattle and Greater Seattle. Three are Irving, Plano, and Frisco. One is Herndon, VA.

The Texas cluster is the tell. Those engineers relocated during COVID, kept their AWS jobs through the hybrid years, and are now structurally non-compliant with a Seattle or Arlington return requirement. They are not posting about it. They are not on the green badge. They are answering recruiter InMails at a rate of roughly zero, because the obvious sourcing motions ("AWS Principal Engineer Seattle") don't surface them.

The right query is the opposite shape. You want a senior IC at AWS whose listed location is not a hub, whose tenure crosses the RTO date, and whose recent activity suggests re-engagement with the outside world. That is not a Boolean string. That is a description of a person.

This is the specific shape of Refolk query that turns RTO compliance reporting into a sourcing artifact. You describe the person in plain English, and you get back people who match the description across GitHub, LinkedIn, and the open web, not just the ones who raised their hand.

The passive candidate signals that actually work

Forget the badge. Here is what senior ICs leak when they're checked out but not yet looking:

GitHub side-project revival

A Principal Engineer who hasn't touched their personal repos in three years suddenly has a half-finished Rust project from last month. Side projects come back when day jobs stop being interesting. This is one of the most reliable AWS engineer sourcing signals, and it's entirely public.

Conference silence

Look at re:Invent 2023 and 2024 speakers. Cross-reference against the 2025 program. The ones who used to speak and stopped are not retired. They're disengaged. Some of them are also writing on personal blogs again, which is the second tell.

Location edits

LinkedIn location changes inside the last 18 months from "Seattle" to "Greater Seattle Area" to "Bend, Oregon" to "Bozeman, Montana" tell you the story without anyone saying anything. Same with the quiet edit from "Arlington, VA" to "Northern Virginia."

Community re-engagement

Senior ICs who are figuring out their next move lurk in the Rands Leadership Slack, the Staff Engineer community around Will Larson and Tanya Reilly, and the Ex-Amazonians LinkedIn group. They post in Blind threads with amazon.com verification. They reappear on lobste.rs. None of this is on LinkedIn, and none of it is keyword-searchable in a traditional ATS.

The senior pool isn't hiding. It's leaking signals everywhere except the one surface recruiters are trained to read. </pull>

pull The senior pool isn't hiding. It's leaking signals everywhere except the one surface recruiters are trained to read.

## Why "Open to Work" is a negative signal at L6+

This is the part most sourcing teams get backwards. A senior IC with the green badge on has, in nine cases out of ten, already been passed over by the obvious buyers. Stripe saw them. Anthropic saw them. The top three AI labs saw them. The badge is a late-stage signal.

The real pool is invisible by design. They will take a warm intro from someone they trust. They will not take a cold InMail that opens with "saw you're open to new opportunities." They aren't, technically. They're open to one specific kind of opportunity that solves their actual problem, which is almost never compensation.

That problem is usually geography. Pitches that lead with "fully remote, we don't care where you live" beat pitches that lead with $50K more in base. Atlassian, Airbnb, GitLab, and Coinbase have been quietly absorbing this exact archetype for two years because their job descriptions say the magic words upfront.

## The Amazon return to office layoffs compounded the pool

Amazon's October 2025 corporate layoff wave, widely reported around 14,000 roles, sits on top of the January 2025 wave and a year of RTO attrition. Survivors are now both overloaded and disengaged. Internal "Focus" and "Pivot" programs (Amazon's PIP-adjacent tracks) have been used by managers to manage out the non-compliant who couldn't be quietly accommodated.

This is why the hiring window is narrowing, not opening. Once the October wave settles and surviving teams stabilize, the checked-out seniors either re-engage (because their team is now interesting again), get pushed out via Focus/Pivot (and become commoditized when they flip the badge on), or quit cleanly into a warm intro. You have roughly Q1 and Q2 of 2026 before this pool resolves.

2,727

One warning on AWS-specific skills

A Principal Engineer on an internal AWS control-plane team is not automatically valuable to a Series B startup. "AWS as an employer" experience is often deep but narrow. "AWS as a customer" experience (the engineer who built a company's platform on top of AWS) is portable.

When you're pitching the non-compliant L6/L7 cohort to your hiring manager, translate. A control-plane engineer at EC2 understands distributed systems at a scale almost no startup operates at, and they will be bored within six months at most Series B companies. Match them to the right altitude or don't match them at all.

This is also where a tool that ranks candidates against a plain-English description rather than a keyword list earns its keep. Asking Refolk for "engineers who built large-scale systems on AWS, not engineers who built AWS itself" is a query a Boolean string can't express, and it's the difference between a shortlist that closes and one that flames out in week three.

The playbook, compressed

1. Read Eugene Kim and Matt Day weekly. Their leaks are your sourcing inputs.
2. Filter your AWS pool by non-hub location and tenure crossing January 2, 2025.
3. Use GitHub revival, conference silence, and location edits as your shortlist signals.
4. Treat "Open to Work" as a negative filter at L6+, not a positive one.
5. Lead pitches with geography flexibility, not comp.
6. Move in Q1 to Q2 2026 before the pool resolves.

The compliance number was the headline. The 8% or so who didn't fall in line is the sourcing list.

FAQ

How do I find Amazon engineers who haven't relocated back to Seattle or Arlington?

Start with location data. Filter for current AWS employees whose listed location is outside the hub cities (Seattle, Arlington, NYC, Austin, Boston, Irvine) and whose tenure predates January 2, 2025. Cross-reference with public signals like GitHub activity and conference participation. The Texas cluster (Irving, Plano, Frisco) and Herndon are particularly dense with this profile because they represent COVID-era relocations that are now structurally non-compliant.

Why don't senior Amazon engineers use the "Open to Work" badge?

Because at L6+ with TC over $400K, the badge is a downgrade. It signals desperation in a market where the best moves come through warm intros from former colleagues, ex-managers, and trusted recruiters. Senior ICs typically have a 60-day exploratory window once a year where they answer warm outreach, then go dark again. The badge is for people who don't have that network, which is almost never a Principal at AWS.

What's the difference between "AWS as employer" and "AWS as customer" experience?

"AWS as employer" means you built AWS services from the inside (EC2, S3, control planes, internal tooling). The expertise is deep but often non-portable, because no other company operates at that scale or with that internal toolchain. "AWS as customer" means you built a product on top of AWS at a company that uses it. That experience translates directly to almost any cloud-native role. When sourcing, distinguish carefully and pitch to the right altitude.

When does this sourcing window close?

Roughly the end of Q2 2026. Amazon's October 2025 layoff wave will take a quarter or two to settle. After that, surviving non-compliant seniors either re-engage with stabilized teams, get managed out through Focus or Pivot programs (at which point they flip the "Open to Work" badge and become commoditized), or take a warm intro and leave cleanly. The unique value of the current moment is that the pool is large, senior, and almost entirely invisible to standard sourcing motions.