How do Splunk alumni split, and who penetrates most?
Wire mix first, then share of each destination bench. Penetration lead CrowdStrike at 1.4%.
Data & notes
| Name | Value | Share |
|---|---|---|
| Palo Alto Networks | 169 | 48.1% |
| CrowdStrike | 129 | 36.8% |
| Zscaler | 53 | 15.1% |
Read the lead wire and penetration
Use this page's scope if you want the named list. Name the same employers and experience cut this page measured.
Key takeaway · How to cite
Data & notes
| Name | Value |
|---|---|
| CrowdStrike | 1.4 |
| Palo Alto Networks | 0.9 |
| Zscaler | 0.6 |
Palo Alto Networks: 169 people
Ranked by wire headcount, as of 2026-10-25 PT.
Data & notes
| Name | Value |
|---|---|
| Palo Alto Networks | 169 |
| CrowdStrike | 129 |
| Zscaler | 53 |
Which talent-flow paths leave Splunk?
The cut requires both: current at the destination, previously at Splunk. Titles are not filtered on this page.
Data & notes
| Source | Destination | Value |
|---|---|---|
| Splunk | Palo Alto Networks | 169 |
| Splunk | CrowdStrike | 129 |
| Splunk | Zscaler | 53 |
Absolute vs penetration: Palo Alto Networks vs CrowdStrike
The two rankings can diverge: volume and density are different decisions.
Data & notes
| Category | People on wire | Share of bench % |
|---|---|---|
| Palo Alto Networks | 169 | 0.9 |
| CrowdStrike | 129 | 1.4 |
| Zscaler | 53 | 0.6 |
Where does Splunk talent flow? Wire vs destination bench
Read the ledger first, as of 2026-10-25 PT. The wire and the bench are two different numbers.
| Destination | On the wire | Destination bench | Share of bench |
|---|---|---|---|
| Palo Alto Networks | 169 | 18,339 | 0.9% |
| CrowdStrike | 129 | 9,362 | 1.4% |
| Zscaler | 53 | 8,621 | 0.6% |
Get the named list of people on these Splunk wires
Ask for the named list when this scope matches the search. The page already fixes the companies and the titles.
What it means for Splunk flow: what to do this week / how to use it
- For list density: prefer the CrowdStrike penetration line (1.4%, 129/9,362).
- Treat other destinations as narrow lists; wire sum is 351 — do not expand past measured hosts.
Cut stays on Splunk → measured destinations
The cut requires both: current at the destination, previously at Splunk. Titles are not filtered on this page. Destinations not listed here were not measured. As of 2026-10-25 PT.
As of 2026-10-25 PT · Source: Metix AI
Notes & method
Methodology
Wire headcount requires both a current destination and a prior Splunk stint. As of 2026-10-25 PT, the bench is the destination's whole current population. Metix AI is the source.
FAQ
- Who is counted on the Splunk into Palo Alto Networks wire?
- A counted person works at Palo Alto Networks now and worked at Splunk before. 2026-10-25 PT is the date, and the lead wire is 169.
- Is the bench the same as the wire for Splunk into Palo Alto Networks?
- The bench (18,339) is not the wire (169). Use 18,339 as the destination denominator.
- Who is the Splunk into Palo Alto Networks list for?
- The list is for sourcing Splunk alumni now at Palo Alto Networks. Start with Palo Alto Networks before the smaller wires.
- What date is the Splunk into Palo Alto Networks cut?
- The cut is dated 2026-10-25 PT. The publisher is Metix AI.
Request the Splunk feeder list
Take the named list for the employers shown here. Name the same employers and experience cut this page measured.
Start a Mira trial