Wired's Geopolitics Tech Policy beat sits where regulation, security, and market power collide. Its readers are technically literate, skeptical of corporate framing, and quick to spot a pitch that's really a press release.

This guide is built for speed: how the beat thinks, which angles land, and how to reach Wired Geopolitics Tech Policy reporters without burning the relationship on the first email.

The beat covers how policy shapes technology — and who wins when it does. Expect export controls and chip supply chains, AI regulation, data sovereignty, platform liability, surveillance and encryption, sanctions, telecom infrastructure, and cyber conflict.

Wired's house style favors consequence over process. A bill's passage is not the story; what happens to engineers, users, or supply chains afterward is.

What gets cut: funding rounds, product launches, personnel moves, and "policy experts available for comment" emails.

Beat coverage at Wired is cross-desk. A single story may file under Security, Business, or Ideas, so a static Wired Geopolitics Tech Policy reporters list goes stale within weeks.

Build your list from bylines, not org charts. Pull author pages and 90 days of published work, then tag each writer by sub-angle: export controls, AI governance, privacy law, cyber policy, platform regulation.

Freelancers and contributing editors matter here — they are often first to a breaking angle and frequently convert to staff. Treat them as primary targets, not backup.

Note that directory counts fluctuate and can read as low or zero during quiet filing periods. Verify activity at author-page level before you send anything.

Lead with the artifact. A leaked memo, a procurement record, a court docket, a satellite image, or a dataset you assembled beats a thesis every time.

Best-performing pitch shapes on this beat:

• The gap story: policy language versus what actually shipped.
• The number story: a dollar figure, unit count, or timeline nobody has published.
• The named-source story: an engineer, a compliance officer, a regulator willing to go on record.
• The second-order story: who gets locked out, priced out, or surveilled as a result.

Wired Geopolitics Tech Policy journalists will trade access for specificity. The pitch that says "here is the 40-page filing and the three people who wrote it" will outperform a polished narrative almost every time.

Email is the channel. DMs, LinkedIn InMail, and cold calls are not how this beat works.

Sources for Wired Geopolitics Tech Policy journalists contacts include author pages, Wired's masthead and contact page, verified social profiles, and the press desk for routing when a target writer is unclear.

Keep the first touch under 150 words:

1. Subject line with the concrete peg.
2. One-sentence thesis with a number or document.
3. Two lines on why it's Wired, not a trade outlet.
4. Offer of exclusive or first look, with a clear date.
5. Name and direct line. No attachments on first contact.

Follow up once, after five business days, with a new fact — never with "just bumping this." Assume a US Eastern working day and avoid Friday afternoons.

• Verified the writer published on this beat in the last 60 days.
• Peg is dated: ruling, filing, deadline, or hearing.
• One number or document in the first two sentences.
• Two named, on-record sources identified.
• No attachments, no press release language, no jargon.
• Exclusive or first-look window stated with an expiry.
• Under 150 words, signature block with direct contact.
• Logged in your Wired Geopolitics Tech Policy reporters list with date and response.
• Single follow-up scheduled with a new fact attached.

Run the checklist before every send. Consistency on this beat beats volume — three precise pitches to the right Wired Geopolitics Tech Policy reporters will outperform three hundred to the wrong ones.