HN Sept 2026 "Who Is Hiring": 106 Cleared SWEs vs 2,090 Anduril Reqs

The September 2026 "Ask HN: Who is hiring?" thread went live on Sept 1, and if you scroll it with a sourcer's eye, something has shifted. "NO VISA SPONSORSHIP," "US CITIZEN / GREEN CARD ONLY," and ITAR carve-outs are no longer the exception in US postings. They are the default, and the pool you thought you were sourcing into just split in two.

What actually changed in the September 2026 thread

The Sept 2026 thread is the first monthly "Who is hiring" to fully post-date the one-year anniversary of the $100K H-1B proclamation, and the density of no-sponsorship language in US postings is visibly higher than in any comparable thread over the past two years. Companies are pricing sponsorship out of their pipelines while defense-tech pulls every cleared engineer it can find.

A few concrete signals from the thread and its policy backdrop:

• The thread landed Sept 1 2026 under the standard rules: hiring-company posts only, one per company, actively filling.
• Aeqium (SF, YC comp-planning startup) writes it plainly: "US CITIZEN / GREEN CARD ONLY (NO VISA SPONSORSHIP)... CANNOT provide visa sponsorship, transfers, or OPT/STEM extensions of any kind."
• Others hard-code ITAR: "The role touches ITAR-controlled data, so US persons only, no visa sponsorship."
• Some post middle-path stacks. Softmax's application form says it sponsors "J-1, TN, E-3, sometimes O-1" but not H-1B.
• Canadian and European posters (Landjourney in Montreal, Attendi in Amsterdam) are actively offering sponsorship and relocation, absorbing the candidates US posts just excluded.

The macro cause is the Sept 19, 2025 proclamation, which restricts H-1B entry unless the petition includes a $100,000 one-time payment per beneficiary or qualifies for a national-interest exemption. Existing H-1B filing fees are generally under $4,000. That is roughly a 25x jump in the sticker price of a single sponsorship decision.

25x

The $100K fee is legally shaky and behaviorally sticky

A federal court has found the proclamation unlawful and collection is currently blocked by litigation, yet US postings on Sept 1 still read "no sponsorship" across the board. The chilling effect is outrunning the policy.

Two reasons this matters for sourcing right now:

1. The proclamation is scheduled to expire Sept 21 unless extended. The Sept 2026 HN thread landed 20 days before that cliff, and posters wrote as if the fee were permanent.
2. A separately proposed DHS rule would add a $103,265 H-1B fee under different legal authority. Even if the proclamation lapses, sponsorship-blocking pricing may persist through another vehicle.

Recruiters who assume the courts will fix this and keep their old candidate lists warm are going to miss two quarters of hiring. The safer bet is to rebuild the pipeline around what US employers are actually writing on Sept 1 2026, which is: I will not sponsor, and I may need a US person under ITAR.

"No sponsorship" is not "US citizen only," and HN is conflating them

A lot of the Sept 2026 postings say "US citizen" when they legally mean "work-authorized without sponsorship" or "US person under ITAR." Sourcers who filter on the literal word "citizen" over-exclude legally hireable candidates and shrink their own pool for no reason.

The distinctions worth memorizing:

• Work-authorized without sponsorship: US citizens, lawful permanent residents (green card), asylees, refugees, TPS holders, and some others. This is the broad "no sponsorship needed" bucket.
• US person under ITAR: US citizens and lawful permanent residents. Broader than citizenship, narrower than work-authorized.
• US citizen only: A real, narrow category usually tied to security clearance eligibility or federal contract requirements.

If a posting says "no sponsorship" but you filter LinkedIn for "US citizen," you are ignoring green-card holders, asylees, and TPS holders who would clear the actual bar. That is the exact gap Refolk closes for US persons only sourcing: describe the constraint in plain English (for example, "work-authorized in the US without sponsorship, ideally with ITAR eligibility") and get a ranked shortlist that respects the real legal category rather than a keyword proxy.

The cleared-engineer supply is structurally tiny

In Refolk's index of professional profiles, only 106 US-based Software, Senior Software, or Staff Software Engineers currently surface with "security clearance" in their public headline. Against Anduril's 2,090 open reqs alone, that is not a talent market. That is a hostage negotiation.

106

Here is the comparable dataset the Sept 2026 thread implies once you line it up:

Two mechanisms explain why this pool cannot expand fast:

• Clearances take 6 to 18 months to originate. You cannot crash-manufacture supply against a Q3 req plan.
• Embedded firmware roles, which are the shape of most defense-tech hiring, take 102 days to fill with 80% of postings staying open for months, per Paraform data on defense/space manufacturing.

Anduril alone added 736 open roles in a 29-day window in 2026 and grew headcount ~83% year over year (4,490 at end-2024 to ~8,200 at end-2025). Shield AI, Saronic, Hermeus, Skydio, Saildrone, and Palantir (whose Maven Smart System became a Pentagon program of record via a March 2026 Feinberg memo, and which is guiding to ~$7.2B in 2026 revenue) are all pulling from the same 106.

You cannot crash-manufacture 106 cleared engineers into 2,090 reqs. Someone loses this quarter.

The TN, E-3, O-1 stack is the new sponsorship middle

US employers who still want international talent are quietly re-architecting around visas the $100K fee does not touch: TN (Canadian and Mexican citizens), E-3 (Australians), and O-1 (extraordinary ability). Sourcers should re-index candidate pools by nationality rather than treating "needs sponsorship" as one undifferentiated bucket.

Why this is a real workaround, not a hack:

• TN is uncapped and does not use the H-1B lottery. A Canadian software engineer can be at a US desk in weeks, not fiscal years.
• E-3 is Australia-only, uncapped in practice, and renewable indefinitely.
• O-1 is expensive to lawyer but does not carry the $100K fee, and it maps well to senior ML researchers with publications or patents.

Softmax's Sept 2026 posting spelling out "J-1, TN, E-3, sometimes O-1" but not H-1B is the pattern to watch. Expect more YC-stage companies to publish this shape of language over the next two threads.

For H-1B alternatives sourcing, the practical move is to search by nationality and current location, not by current visa status. That is a query LinkedIn's filters handle badly and boolean handles worse. In Refolk, you can just ask: "senior backend engineers who are Canadian citizens, currently in Toronto or Vancouver, with three plus years at a US-headquartered company." You get a shortlist that maps to TN-eligible people without writing a single boolean.

Nearshore is the real arbitrage

The largest sponsorship-free English-speaking engineering pool a US company can access is Canada, and it is roughly 398x the size of the US cleared-SWE pool. Refolk's index counts 42,180 Canada-based SWE, Senior SWE, Staff SWE, and ML Engineer profiles.

Two things this pool is not:

• It is not a replacement for cleared engineers. You cannot TN-hire someone into an ITAR role. Clearance eligibility requires US person status.
• It is not free. TN status is tied to a specific employer and role and needs renewal, and Canadian comp expectations for senior ICs have climbed sharply in 2025 to 2026.

Two things it is:

• It is a legal, uncapped route around the $100K fee for non-cleared work (most SaaS, most infra, most applied ML that is not defense-adjacent).
• It is where displaced international candidates are actively landing. The Sept 2026 HN thread has Landjourney (Montreal) and Attendi (Amsterdam) posting relocation-friendly roles into the exact talent US posters just excluded.

If you are a US recruiter running a growth-stage SaaS pipeline and your Q4 plan assumed H-1B transfers, the fastest correction is to open a nearshore lane. The people your competitor cannot sponsor are one TN petition away from your offer.

What to actually change in your sourcing this week

Rewrite three queries, split your ATS pipelines, and stop treating "international" as one bucket. That is the whole playbook.

Concretely:

1. Split your "needs sponsorship" tag into three: needs H-1B, TN/E-3/O-1 eligible by nationality, and green-card-in-progress. These behave completely differently under Sept 2026 rules.
2. Rebuild your ITAR and cleared search around US person status, not the literal word "citizen." You are leaving green-card holders on the table otherwise.
3. Open a Canada lane if you do not have one. The 42,180 number is not theoretical, it is the pool competing recruiters are already working.
4. Re-check the ITAR engineer hiring language in your JDs. If you wrote "US citizen only" but you mean "US person," you are shrinking your own funnel.
5. Watch the Sept 21 expiration date and the DHS $103,265 rule proposal. Even if the proclamation dies, the behavioral chill and any replacement rule will keep the pool bifurcated through 2027.

The through-line: no visa sponsorship engineering jobs are not a policy story anymore, they are a sourcing-pool story. Half the US roles are quietly locking out half the candidates, and the recruiters who adjust their queries to match what postings actually mean (not what they say) will out-hire the ones who do not.

FAQ

Is the $100K H-1B fee still legally in effect for Sept 2026 hiring?

Collection is currently blocked by litigation after a federal court found the proclamation unlawful, and the proclamation itself is scheduled to expire Sept 21 unless extended. That said, US employers are still writing "no sponsorship" into Sept 2026 HN postings as if the fee were permanent, and a separately proposed DHS rule would add a $103,265 fee under different legal authority. The behavior is outrunning the policy, so plan pipelines around the chilling effect, not around a courtroom win.

How do I source ITAR-eligible engineers when only ~100 profiles publicly signal clearance?

Stop searching for the word "clearance" and start searching for the shape of a cleared career: prior employment at Lockheed Martin, the US Air Force, or defense-focused primes, plus US person status. Refolk's index shows only 106 US SWE profiles with "security clearance" in the headline, but the actual eligible pool is much larger and does not self-label. Describe the shape ("US persons with three plus years at a defense prime, backend or embedded, open to Anduril-adjacent") and let the tool find the profiles that never wrote the keyword.

Are TN, E-3, and O-1 visas really immune from the $100K fee?

Yes for TN and E-3, which are separate treaty-based categories that do not touch the H-1B lottery or its associated fees. O-1 is a distinct extraordinary-ability petition also outside the H-1B system. The catch is eligibility: TN requires Canadian or Mexican citizenship and a listed profession, E-3 requires Australian citizenship, and O-1 requires a documented record of extraordinary achievement. For most sourcing pipelines, TN is the practical unlock because the Canadian engineering pool is the largest of the three.

What should I stop doing on LinkedIn right now?

Stop using "US citizen" as your keyword filter for no-sponsorship roles. It excludes green-card holders, asylees, refugees, and TPS holders who are legally work-authorized without sponsorship, and it also excludes green-card holders who qualify as US persons under ITAR. Filter on work authorization status and location instead, and if the platform's filters cannot express what you actually mean, describe the constraint in plain English somewhere that can, then bring the shortlist back into your ATS.