Stripe and Shopify Out-Hired Big Tech in 2026. Re-Rank Your List.

If your 2026 account list still opens with FAANG, you are sourcing against a 2022 market. The volume leaders in tech hiring and the growth leaders have split into two different sets of companies, and the pool sizes behind the fastest-growing sectors differ by more than two orders of magnitude.

The Pragmatic Engineer's 2026 "State of the software engineering job market" report says top tech is hiring 20% more year over year, Apple, Amazon and IBM lead by open roles, Meta fell off the top 20 after layoffs, and Stripe, Shopify and Atlassian all out-hired Big Tech. That single split reshapes the target list, the candidate-supply map, and the way you weight reqs.

The 2026 target list splits into volume leaders and growth leaders

Volume leaders (Apple, Amazon, IBM) and growth leaders (Stripe, Shopify, Atlassian) are now different companies. Sourcers who treat "most open roles" as their target list will spend the year fighting for reqs that sit open longest.

Here is what the Pragmatic Engineer report (built on Workforce.ai's 1M+ monthly job changes and 300M+ employment validations, plus TrueUp job data) actually says:

• Top tech companies are hiring 20% more year over year.
• Apple, Amazon and IBM lead by number of positions listed.
• Stripe, Shopify and Atlassian each hired more than Big Tech over the same window.
• Microsoft and Amazon were flat; Google and Apple hired devs consistently.
• Meta dropped off the top 20 after layoffs.
• US and UK vacancies are up; Canada is flat; Germany and France declined.

The mechanism matters. Volume leaders post a lot because they are large and re-fill attrition. Growth leaders post because they are adding headcount. Reqs at growth-mode companies close faster and refer more, which means placements per hour are higher even when the raw req count is lower. Weight your target list by growth rate times req age instead of headcount and the ranking flips.

20%

Meta's fall-off is the biggest candidate-supply event of the year

Meta dropping out of the top 20 is not just a hiring story. It is the single largest recently-vetted L4 to L6 backend cohort to hit the open market in years, and Stripe, Shopify and Atlassian are the natural absorbers.

The stack overlap is the reason. Stripe's public careers page lists Java, Ruby, JavaScript, Scala and Go as the working stack. Shopify is Ruby and Rails heavy. Atlassian ships Jira, Confluence, Loom and Rovo out of a distributed-first org. Meta seniors who wrote polyglot service code map cleanly onto Stripe's stack in particular.

Three sourcing implications:

1. Ex-Meta L5 and L6 with Scala or Go on GitHub are the top of Stripe's inbound funnel right now. Anyone still cold-emailing them for a Series B is late.
2. Ex-Meta infra engineers with JVM experience map onto Atlassian.
3. Ex-Meta product engineers with Rails, React or GraphQL show up in Shopify's referral graph within weeks of leaving.

This is the exact scenario where a plain-English query beats a Boolean string. Asking Refolk for "senior backend engineers who left Meta in the last 12 months with Scala or Go shipped to production" returns a ranked shortlist across GitHub, LinkedIn and the open web instead of a keyword-matched list you still have to re-rank by hand.

Fintech, observability and security are the growth sectors, and they are not the same size

The three sectors pulling reqs in 2026 - fintech, observability and security - are wildly different sourcing problems because the US talent pools sit orders of magnitude apart. Treating them as similar searches is why observability reqs sit open for 90+ days.

Here is what Refolk's index of US professional profiles shows, side by side:

Fintech engineering in the US is 376 times larger than the tight observability craft pool. Security sits in between, roughly 9x smaller than fintech and 42x larger than observability. If your intake process runs the same playbook for all three, two of the three will fail.

176

Sourcing fintech engineers: density, not scarcity

Fintech sourcing in 2026 is a density problem, not a discovery problem. With 66,235 US engineers currently at Financial Services companies, the game is targeting and messaging.

The Refolk index shows the tightest clusters at Ramp, Coinbase, Capital One, Jane Street, Block and Bridge. That is your first-pass account list for payments, ledger, risk or trading infra. Ramp in particular has become the fintech density anchor early Stripe was in 2018.

Pragmatic tactics:

• Weight recency of tenure. Ramp engineers who joined in the last 18 months are inside a strong equity refresh; ones past three years are the ones taking calls.
• Filter by payments primitives (PSPs, KYC, ACH, card networks, Stripe API surface) rather than by "fintech" as a title token.
• Cross-reference Jane Street for anyone doing latency-sensitive work; those candidates convert into Bridge in a way LinkedIn keyword searches will never surface.

Observability engineers: a named-account game

Observability hiring in 2026 is a named-account problem, not a keyword problem. With only 176 US profiles matching the SRE or Platform title plus Prometheus and OpenTelemetry, you cannot filter your way to a shortlist. You have to know the accounts.

The named-account universe:

• Datadog (also a top security-engineer employer, per the index)
• Honeycomb
• Grafana Labs
• Chronosphere
• Teleport (appears in Refolk's top-employer signal)
• Infra teams at Apple, IBM and JPMorganChase

Anyone running "observability engineer" as a title search on LinkedIn is missing the roughly 90% of the pool who carry SRE, Platform Engineer or Infrastructure Engineer titles and only reveal the OTel and Prometheus work in GitHub commit history or a conference talk. This is exactly the multi-source problem Refolk is built for: ask for "US SRE or platform engineers with production OpenTelemetry and Prometheus work in the last 18 months, alumni of Datadog, Honeycomb, Grafana Labs, Chronosphere or Teleport" and get a ranked list stitched from GitHub, LinkedIn and the open web.

Security engineers: the Datadog cross-signal nobody is reading

Security engineering sits at 7,377 US profiles, and the non-obvious signal is that observability vendors are quietly becoming top security-engineer employers. Datadog appearing alongside Google and AWS in Refolk's security top-employer list is the tell.

Why it happens: observability platforms handle regulated customer data at massive scale, which forces them to build serious AppSec and ProdSec teams. Those engineers get poached into fintech (Coinbase, Ramp) because the skills transfer cleanly. Sourcers who only look at pure-play security vendors miss the Datadog-to-Coinbase migration path entirely.

"AI Engineer" is the biggest title trap of 2026

The AI Engineer title is real, but sourcing by it will cost you the actual talent. LinkedIn named it the number one fastest-growing job title in the US, AI/ML postings grew 163% from 2024 to 2025 and are up another 74% YoY in 2026, and agentic AI postings alone grew 280% to 90,000 listings. Almost none of the good candidates carry that title on their profile yet.

Most 2026 AI Engineers are still called Backend Engineer on LinkedIn. Source the work, not the title.

What to source for instead:

• RAG pipeline work in production (chunking, embeddings, eval)
• LLM eval frameworks (Braintrust, LangSmith, in-house)
• Agent orchestration (LangGraph, CrewAI, custom state machines)
• Prompt regression testing in CI
• Vector DB tuning (pgvector, Pinecone, Turbopuffer)

For scale, a January 2026 analysis found 140,068 postings matching "Software Engineer" and 137,176 mentioning Python. Against that denominator, running Boolean strings on the "AI Engineer" title token is a signal-to-noise disaster. Source by the artifact.

Europe is a candidate arbitrage, not a hiring market

For sourcers filling US roles, Europe in 2026 is a net exporter of candidates, not a competitor. US and UK vacancies are up; Germany and France are down. That gap is a hiring lever if you use it right.

The most obvious play is Atlassian, the distributed-first company behind Jira, Confluence, Loom and Rovo. Geography is not a filter at Atlassian; skills are. A strong Berlin or Paris engineer whose local market just contracted is a qualified candidate for a US-headquartered role that ships to the same product surface.

Concrete moves:

1. Pull senior backend engineers out of the German and French markets into Stripe, Ramp and Atlassian.
2. Target Paris observability and infra alumni for US growth companies.
3. Skip trying to fill Munich or Frankfurt reqs from a US pipeline; the flow goes the other way now.

Asking Refolk for "senior backend engineers currently in Berlin or Paris, open to US relocation, Scala or Go on GitHub" is a five-second query that would take an hour of LinkedIn X-ray to approximate.

The re-ranked target list for 2026

Run this account list in order of placement leverage rather than open req count:

1. Stripe (growth + stack overlap with ex-Meta)
2. Shopify (growth + Rails ecosystem depth)
3. Atlassian (growth + distributed-first, so EU arbitrage works)
4. Ramp (fintech density anchor)
5. Coinbase, Block, Bridge (fintech absorbers)
6. Datadog, Honeycomb, Grafana Labs, Chronosphere, Teleport (observability named-account universe)
7. Apple, Amazon, IBM (volume leaders; use for backfill and passive candidate discovery, not primary targeting)
8. Google (consistent hiring, high bar, long cycles)

Meta belongs on the candidate supply side of your spreadsheet, not the demand side. So does anyone whose growth chart went flat this year.

The old sourcing map assumed Big Tech was where the reqs were and everyone else was where the candidates were. In 2026 the reqs moved and the candidates moved with them. Update your account list before Q1 planning locks it in for another year.

FAQ

Who is hiring engineers the most in 2026?

By raw open-role count, Apple, Amazon and IBM lead, per Pragmatic Engineer's 2026 report. By growth rate, Stripe, Shopify and Atlassian all out-hired Big Tech over the same window. Sourcers should weight their target list by growth rate and req age rather than raw volume, because reqs at growth-mode companies close faster and generate more referrals per placement.

Where should I source fintech engineers first?

Start with the density clusters in Refolk's index: Ramp, Coinbase, Capital One, Jane Street, Block and Bridge, in that order for most payments and ledger roles. The US pool sits at roughly 66,235 fintech engineers, so the problem is targeting and messaging, not discovery. Filter by payments primitives (PSPs, KYC, ACH, card networks) rather than the "fintech" title token, and weight recency of tenure heavily since equity refresh cycles drive who takes calls.

Why is observability sourcing so much harder than security or fintech?

Because the tight observability craft pool in the US is roughly 176 profiles, versus 7,377 for security and 66,235 for fintech, per Refolk's index. That is a 376 to 1 ratio against fintech. You cannot keyword-filter your way to a shortlist that small; you have to work named accounts (Datadog, Honeycomb, Grafana Labs, Chronosphere, Teleport) and read GitHub commit history and conference talks to catch the roughly 90% of the pool who carry SRE or Platform Engineer titles instead of "Observability."

Is "AI Engineer" a real title to source on?

It is real but it is a trap. AI/ML postings grew 163% from 2024 to 2025 and another 74% YoY in 2026, and agentic AI postings hit 90,000 listings, but most strong candidates still carry Backend Engineer, ML Infra or Platform titles on LinkedIn. Source by artifacts (RAG pipelines, LLM eval frameworks, agent orchestration, vector DB tuning) rather than the title token, or you will miss the actual builders.