Matt Cutts on Google, web spam, and fixing government tech

Executive overview

Most government technology is frozen circa 1995 — bug bounties, cloud, and basic UX practices that industry adopted decades ago are still being introduced. The US Digital Service exists to close that gap by embedding tech talent inside agencies on short tours of duty.

Matt Cutts spent 17 years at Google working on SafeSearch, ads, and web spam before joining USDS as interim administrator. The two roles share a core insight: sustainable systems require working with the people already inside them, not around them.

The biggest leverage point in government tech is finding the passionate insiders who know the right answer but lack the power to act on it — and giving them wind beneath their wings.

Early Google: ads, spam, and uncertainty

• Google's survival during the dot-com crash was far from certain; Alta Vista nearly caught up but never got quality right
• The first AdWords prototype nearly melted Google's servers — caching was accidentally left off for 30% of users
• The first self-service AdWords advertiser was a Maine lobster company; it revealed the long tail of niche intent
• Early multi-colour ads had low click-through until A-B testing revealed copy and placement mattered more than format
• The "evil unicorn" problem: when few legitimate pages exist for a query, spammers fill the vacuum — and you still have to show 10 results

Web spam: philosophy and limits

• Spam was not taken seriously inside Google until Cutts demonstrated concrete loopholes (e.g. expired domains repurposed for porn)
• The web spam philosophy: automate what you can, catch the residual with trained human reviewers, use that as training data for the next algorithm wave
• Synthesising new content (deepfakes, GANs) is fundamentally harder to detect than republishing old content
• The SearchKing lawsuit established that search results are protected by the First Amendment
• SEO is energy that can be channelled positively: "make your site faster, easier to navigate" beats adversarial enforcement
• Communicating algorithm direction publicly: point to where the puck is going, not current signals — avoids arming bad actors

Working on SafeSearch and content moderation

• SafeSearch was originally scoped narrowly to pornography; spam meant cheap Viagra and loan consolidation
• Once you develop a "black hat mindset" — seeing every system's abuse vectors — you can't unsee it
• Cutts worked with a whiteboard blocking his monitor from Larry and Sergey's view while searching for SafeSearch leakage

The US Digital Service: what it does

• USDS was created after healthcare.gov failed at launch; the fix required blameless post-mortems, monitoring, and site reliability engineering practices
• Operates like a SWAT team: discovery sprints (2 weeks), months-long, or years-long engagements depending on scope
• Three main roles: ~one-third engineers, one-third designers, one-third product managers — plus procurement and legal specialists
• Tour of duty model: 6 months to 4 years; ~180 people; apply in 90 seconds at usds.gov/apply
• Government IT staff under 30: zero at HUD — one good technical hire can shift outcomes for tens of thousands of people
• The dirty secret: government does less work than its contractors; if you don't know what "good" looks like, you can't evaluate what you're buying
• One procurement success: requiring contractors to submit code, graded by engineers, instead of written proposals — measurably better outcomes

Closing the tech gap in government

• Government tech is approximately 13 years behind industry, down from 23 years — measured by adoption of practices like bug bounties (not used federally until 2016)
• The seams between systems — not the primary systems — are where security vulnerabilities and process failures concentrate
• On backdoor encryption: Cutts's personal technical view is sceptical; as a government employee he participates in policy processes and abides by the outcome
• GANs and fake-identity spam are not yet a major problem at USDS scale; the more pressing work is converting paper processes to functional digital ones

User research and design

• The first 9–10 user interviews yield the largest return; the 5,000th still improves the product
• USDS veterans team talked to 5,000 veterans over four years; built a discharge-upgrade tool that veterans explicitly asked for — not from a product roadmap
• Goodwill is undervalued: Zuckerberg's congressional testimony erased $129 billion in market cap in one day
• Design is not aesthetics — it is reducing pain points; the insurance site that skipped forced account creation won the $400 sale

How tech people can contribute to government

• Show up to city council and state legislature meetings as a technical resource
• Run for office — computer scientists are rare among elected officials
• Civic tech startups are a real path: YC-backed companies based in DC are already working on government problems
• USDS tour of duty can often be taken as a leave of absence from a tech company without forfeiting stock options
• Two-thirds of trust in government is driven by direct service interactions — improving those interactions is a high-leverage point