Wired's Politics desk sits at the intersection of technology, power, and policy — not horse-race politics. To break in, you need a document, a data set, or a demonstrable consequence, not a position.

This guide covers how Wired Politics reporters actually work, how to read the Wired Politics reporters list, and how to reach the right bylines without burning your credibility.

The beat is defined by tech-policy stakes: platform regulation, Section 230, antitrust, AI governance, election security, deepfakes, surveillance, data privacy, and cyber policy. Congress and the White House matter insofar as they move those levers.

Wired Politics journalists rarely write straight political process stories. A committee vote is only a story if it changes how technology is built, deployed, or policed.

• Strong fits: state privacy laws, FTC/DOJ enforcement, AI executive actions, police tech procurement, disinformation operations, election infrastructure.
• Weak fits: polling, campaign strategy, partisan horse-race analysis, general "techlash" commentary.

Work from the Wired Politics reporters list in your directory before you send anything. The desk is small — 5+ active bylines — so misrouting a pitch by one seat is visible fast.

Use byline archaeology over bios. Read the last 90 days of clips to find who is actually covering your issue, not who owns the title.

Treat this table as a starting map, not gospel. Confirm current coverage before every pitch — beats shift quarterly.

Frame every pitch as a power question: who controls the system, who is exposed by it, and what changes if nothing is done. That framing matches how the desk edits.

Data beats adjectives. A novel dataset, an original analysis, or a first-of-its-kind document outperforms any quote you can offer.

• Exclusivity of evidence — documents, logs, contracts, model outputs.
• Consequence for users — who gets surveilled, denied, misclassified, or misinformed.
• Institutional accountability — agencies, vendors, platforms, universities.
• Expert access — a named researcher or whistleblower willing to go on record.

What gets ignored: vendor announcements dressed as news, "experts available to comment" emails, and think-tank reports with no original reporting hook.

Use direct email over social DMs for first contact. Keep the pitch under 150 words: hook, evidence, why now, what you can provide.

Accessing Wired Politics journalists contacts means working from verified directory entries and published bylines — never scraped or guessed addresses. A bounced or wrong-desk email costs you the story window.

• Subject line: the finding, not the pitch. "State police bought X system without disclosure" beats "Story idea for Wired."
• Offer the document first, the interview second. Reporters self-assess faster with material in hand.
• Never pitch the same exclusive to two desks. The politics and business teams talk.
• If you have a feature-length investigation, flag lead time — the desk plans weeks out, not hours.

For fast-moving news, send a two-line heads-up with the link or attachment and an offer to brief within the hour. Speed signals reliability.

• ☐ Primary source attached or linked (filing, FOIA, dataset, memo)
• ☐ One-sentence "why this matters for tech and power"
• ☐ Named expert or document-holder available on record
• ☐ Correct reporter chosen from the Wired Politics reporters list
• ☐ Contact pulled from verified Wired Politics journalists contacts
• ☐ Under 150 words, no attachments over 5MB, no marketing language
• ☐ Single follow-up scheduled for 48 hours
• ☐ Alternative angle ready if the desk passes (data viz, op-ed, regional peg)

Pitch the evidence, route it precisely, and let the consequence carry the story. That is the whole game with Wired Politics reporters.