Temporal's $550M Lands 4 Miles From 4,501 Amazon SDEs

On September 14, 2026, Temporal Technologies closed a $550M Series E at a $12.55B valuation, co-led by Lightspeed with Wellington, Goldman Sachs Alternatives, and Tiger Global. The company is headquartered in Bellevue. Four miles down the 405, Amazon has filed WARN notices for 4,501 Washington corporate employees in ten months, most of them SDEs. If you source AI infrastructure engineers, this is the cleanest poach lane of 2026, and almost nobody is sourcing it correctly.

Why this is a mapped poach lane, not a vibe

A funded buyer, a hard deadline, and a displaced seller pool all sit inside a 15-mile radius. That is what makes Temporal's raise different from the usual "Series E, hiring hard" announcement.

• Funded buyer: Temporal, $550M in the bank as of Sept 14, 2026, with an annualized revenue run rate past $250M growing over 200% YoY.
• Hard deadline: Amazon's Oct 28, 2025 WARN set staggered separation dates of Jan 26, Jan 30, Feb 5, Feb 25, Feb 27, Mar 19, Apr 1, Apr 26, and May 26 2026, with follow-on waves still rolling.
• Displaced sellers: 2,303 corporate employees in the Oct 2025 filing, mostly Seattle and Bellevue, where "software development engineers make up the largest group of employees affected." Then another 2,198 in Feb 2026, with 1,400 in Seattle and 600 in Bellevue.

Add the two WARN waves and you get 4,501 Washington Amazon separations in ten months. Temporal's entire global headcount is 570. The seller pool is roughly 8x the buyer. The hard part is not supply. The hard part is picking.

The headline number is Temporal Technologies hiring, but the search term is wrong

The term "durable execution" is a trap for sourcers. In Refolk's index, only 253 U.S. profiles mention "durable execution" anywhere in their headline or bio, and the top titles skew Enterprise AE, Strategy, and Marketing. The technical core employer under that keyword is Temporal itself, with five people.

Meanwhile, 1,200 U.S. profiles list "Temporal" as a skill, and 2,851 U.S. SDE, Senior SDE, and Principal Engineer profiles carry Distributed Systems as a skill, with Greater Seattle tied as the number-one region. That is the real pool.

9%

The mechanism is simple. "Durable execution" is a category Temporal's marketing team coined to describe what the product does. Engineers do not put marketing categories in their LinkedIn skills section. They put the primitives they shipped: workflow engines, saga pattern, idempotency keys, SWF, Cadence, Step Functions, Airflow at scale. Sourcing by the vendor's category word is fishing inside the vendor's own marketing funnel. You will find their SDRs and three of their principal engineers. You will not find the 2,500 Amazon SDEs who built the systems Temporal's product abstracts.

The index numbers, side by side

Here is what Refolk's index and the public filings actually say, with the derived ratios that matter for a sourcing plan.

Three derived numbers do the work in a sourcing plan:

1. 4.7x: the "Temporal (skill)" cohort is 4.7 times the "durable execution (concept)" cohort. Tool-name sourcing beats category-name sourcing by nearly 5x on recall.
2. ~89: if Temporal doubles headcount in a year (the team already doubled in the past year, and the Series E is explicitly earmarked for growth) and keeps its 15.6% Bellevue-local ratio, that is roughly 89 net new Bellevue hires in 12 months.
3. 600: the February 2026 WARN wave alone put more than 600 corporate workers in Bellevue on the clock. The buyer needs 89. The displaced pool in the same city is nearly 7x that.

The Oct 2025 and Feb 2026 waves are not the same pool

The two WARN waves hit different seniority mixes, and the senior talent Temporal actually needs is concentrated in the second one. Treat them as separate lists or you will waste outreach on the wrong SDE level.

• Oct 2025 wave (2,303): concentrated on engineering teams, falling more heavily on newer hires and the managers one layer above them. Good for a growth-stage company staffing out breadth. Less good for the staff and principal roles Temporal is funding.
• Feb 2026 wave (2,198, with 1,400 Seattle and 600 Bellevue): broader cross-org, hits deeper into AWS platform tenure. This is where the Senior SDE, Principal, and Distinguished pool sits.
• Aug 2026 follow-on (121 roles): 52 of 121, or 43%, are SDEs or applied scientists. The SDE I / II / III split is almost perfectly flat at 13 / 12 / 12. 53 Bellevue positions, 49 of them in the SEA106 building. SEA106 is a literal, nameable sourcing target.

For a durable execution engineer specifically, you want the Feb 2026 wave plus the SEA106 slice of the Aug 2026 wave. Those are the AWS Step Functions, SWF, and distributed-systems veterans whose internal-transfer clocks run out through 2026 and into 2027.

Sourcing has to be dated to each engineer's clock, not the WARN date

The outreach window for a WARN-tagged engineer is the final 30 days before their individual separation date, not the day the filing hit the news. Message them earlier and you are competing with Amazon's internal recruiter, who is paid to keep them.

Here is why. Amazon runs an internal transfer window after notice. During the first 60 days, the engineer is actively interviewing on internal teams, often with pre-wired referrals from their old manager. External outreach in that window has a terrible reply rate because the engineer is heads-down on internal loops and does not want to commit to anything outside. The last 30 days are different. By then, most internal options have resolved to yes or no, and the no's are suddenly very interested in outside conversations. The staggered separation dates from the Oct 2025 filing (Jan 26, Jan 30, Feb 5, Feb 25, Feb 27, Mar 19, Apr 1, Apr 26, May 26 2026) and the parallel schedule from Feb 2026 mean the outreach calendar is not one date. It is nine dates, each with its own cohort.

This is exactly the kind of filter that is painful in LinkedIn Recruiter and native in Refolk: describe the slice (Amazon SDEs in Bellevue with a separation date in the next 30 days, distributed systems experience, no new employer listed yet) in plain English and get the matching names back ranked, instead of hand-rebuilding Boolean strings every week as the clock advances.

AI agent infrastructure recruiting is a comp fight you win on scope

Temporal is paying FAANG-plus packages. The $12.55B valuation at a 50.2x revenue multiple means equity is dense, and the Series E is explicitly earmarked for the engineering ramp. For a Senior SDE walking out of Amazon's SEA106 with a decade of workflow experience, Temporal's cash-and-equity will clear Databricks, Snowflake, and most of Microsoft's Redmond offers.

Comp alone does not win these people, though. Amazon ex-SDEs have heard the "we pay FAANG+" pitch from every post-Series-D startup for three years. The actual lever is scope, and Temporal's scope pitch has three legs that nobody else in the Puget Sound area can match right now:

• Platform-defining work on agent reliability. Samar Abbas, Temporal's co-founder and CEO, has said, "As agents take on more critical work across more systems, every additional step creates another place to fail. In production, that work has to survive those failures and finish reliably." Engineers who built retry logic for SWF or Step Functions have been waiting their entire careers for someone to let them design the primitives from scratch.
• Named lineage. Samar Abbas built Cadence at Uber. Maxim Fateev, co-founder and CTO, is ex-Uber and ex-AWS SWF. For an Amazon workflow engineer, this is their lineage. It is the single credential that resolves the "is this a real company" question in one sentence.
• The Jassy counter-pitch. Andy Jassy spent 2025 and 2026 telling Amazon to operate like "the world's largest startup." For engineers who heard that speech and then got WARN'd, the counter-pitch writes itself.

Engineers who were told to behave like a startup can now actually join one, four miles down 405.

Lightspeed co-led the $300M Series D in February 2026 and led the $550M Series E in September 2026. Doubling down inside seven months is the proof that the hiring ramp is funded with conviction, not optionality.

The real competitors are Cribl, NVIDIA, and StackAI

The top U.S. employers of profiles listing Temporal as a skill, per Refolk's index, are NVIDIA, Google, Cribl, StackAI, and Defense Unicorns. That is the actual hiring competition for Bellevue tech sourcing in this niche, not Google and Meta in the abstract.

What this means for a sourcer running outbound against the Amazon WARN pool:

• Cribl is in Seattle. They have been quietly absorbing Amazon distributed systems talent and will move fast on any WARN name with observability or pipeline experience. Expect to compete on same-week offers.
• NVIDIA is remote-friendly for infra roles. For engineers who do not want to switch commutes, NVIDIA is the easiest comp beat Temporal faces. Lead with the Bellevue office as a feature, not a bug.
• StackAI and Defense Unicorns are smaller. Both are credible shops for agent infrastructure work. Both will lose to Temporal on brand and funding, but can win on title and scope if Temporal's recruiter opens with the wrong role level.

The Amazon Seattle WARN poach list is a bigger pool than any one of these companies can absorb. The win condition is not "find the names first." It is "find the right 89 names for Bellevue specifically, before the Feb 2026 separation cohort clears their internal interviews."

4,501

That is the shape of the lane. A funded buyer with a public hiring target, a seller pool roughly 8x its current size, both inside the same metro, both on a calendar that resolves inside 12 months. Sourcers who build the shortlist on primitives (Cadence, SWF, Step Functions, saga pattern) and date their outreach to each engineer's individual separation clock will book interviews. Sourcers who search "durable execution" in LinkedIn will find Temporal's own Enterprise AEs. The gap between those two approaches is the entire article.

FAQ

How many engineers does Temporal realistically need to hire in Bellevue?

Roughly 89 net new Bellevue hires in the next 12 months, if the team doubles again (which the Series E explicitly funds) and keeps its current 15.6% Bellevue-local ratio of 89 out of 570 global employees. The Feb 2026 WARN wave alone put more than 600 corporate workers in Bellevue on the clock, so the local supply is nearly 7x the local demand. The constraint is matching, not volume.

What search terms actually surface durable execution engineers?

Primitives, not categories. Search for Cadence (the Uber predecessor to Temporal), SWF, AWS Step Functions, Airflow at scale, saga pattern, idempotency keys, workflow engine, and orchestration at scale. In Refolk's index, 2,851 U.S. engineers with distributed systems skills have shipped these primitives, versus only 253 profiles that use the phrase "durable execution." The category word misses nine out of ten qualified candidates.

When is the best time to reach a WARN-tagged Amazon engineer?

The final 30 days before their individual separation date, not the day the WARN filing hit the news. Amazon's internal transfer window keeps engineers heads-down on internal loops for the first 60 days, with low external reply rates. Once internal options resolve, external interest spikes. The staggered separations from Oct 2025 and Feb 2026 mean there are nine distinct 30-day outreach windows, not one.

Who else is competing for the same Amazon SDEs?

Per Refolk's index, the top employers of U.S. profiles listing Temporal as a skill are NVIDIA, Google, Cribl, StackAI, and Defense Unicorns. For Bellevue-specific Amazon WARN names, Cribl is the fastest and most direct competitor, with same-week offers common. NVIDIA competes on remote flexibility. The AWS internal transfer process is itself a competitor during the first 60 days of the WARN clock.