newsfilter.io
Interview

Matt Cutts on the US Digital Service and Working at Google for 17 Years

  • Career Trajectory:

    • Matt Kutz joined Google in the year 2000 as its 71st employee, remaining for nearly 17 years before transitioning to the U.S. Digital Service (USDS).
    • He spent five years as an individual contributor working on Safe Search, Ads, and Quality before managing the Web Spam team for the remainder of his tenure.
    • He currently serves as the Administrator of the U.S. Digital Service, having previously acted in an interim capacity after a political appointee left the role.
  • Early Google Culture & Operations:

    • In 2000, Google operated as a startup where new hires were a rare occurrence (e.g., three people starting on one day) compared to hundreds of weekly starts in later years.
    • Project assignment was informal; Kutz was transferred to the Ads group mid-ski trip based on a manager's observation of his front-end programming interest.
    • Search strategy was driven by immediate partner needs, such as building Safe Search for a specific partner, rather than a long-term product roadmap.
    • Kutz recalled working until 2 A.M. on the first working version of Safe Search, highlighting the intense startup culture of that era.
  • Product Development & Adwords Launch:

    • Google initially struggled with advertising strategy, debating between CPM (cost per thousand) and Cost Per Click (CPC) models before adopting self-service bidding similar to Overture.
    • An early prototype of self-service ads nearly crashed Google's infrastructure because Kutz failed to disable caching, causing dynamic ads to be served constantly to 30% of users.
    • The first successful self-service AdWords customer was a Maine lobster company, validating the "long tail" of small businesses seeking niche search traffic.
    • Initial ad experiments failed due to poor copy and lack of user guidance, not because of the format itself.
    • A/B testing became critical to improving click-through rates once early prototypes demonstrated low engagement.
  • Search Quality & Content Strategy:

    • Google faced the "Evil Unicorn Problem," where searchers looking for low-quality or fringe topics (e.g., "flat earth") forced the engine to display weak results to fill a required number of slots.
    • The company experimented with interface changes to flag untrusted content areas but ultimately decided to maintain standard results unless the quality was egregiously low.
    • Legal precedents established that search results are protected by the First Amendment (Search King lawsuit) and that Google retains the right to manually adjust rankings for spam (Kinder Start lawsuit).
    • Features allowing users to tweak ranking factors (e.g., reputation) were tested and abandoned because users universally ignored them.
  • Spam Detection & Safety:

    • Safe Search required employees to manually review pornography and non-family-safe content, leading to operational changes like placing whiteboards between Kutz's cubicle and the office of Google's founders.
    • Spam tactics evolved from simple keyword stuffing to complex schemes like buying expired domains, creating fake awards, and recycling conference badges.
    • Kutz recalls arguing with early employees who believed Google's algorithm was impenetrable to spam, eventually proving that "good engineering" alone could not stop evolving bad actors.
    • The company shifted its stance from viewing SEOs as adversaries to treating them as partners seeking to improve site quality, focusing on positive guidance (speed, navigation) over purely punitive measures.
  • Deep Fakes & Future Tech Challenges:

    • Kutz identifies deep fakes as a fundamentally difficult problem to detect algorithmically due to the ability to manipulate pixels and histograms.
    • The recommended strategy involves a hybrid approach: algorithmic detection for the majority, manual review for residuals, and using that data to train subsequent algorithms.
    • He notes that synthesizing new content (deep fakes) is harder to detect than republishing existing content, requiring robust policy processes for de-platforming or demonetization rather than full automation.
  • U.S. Digital Service (USDS) Mission & Structure:

    • USDS was formed in response to the healthcare.gov launch failure, applying Silicon Valley best practices like Site Reliability Engineering (SRE) and blameless post-mortems to government projects.
    • The agency operates on a "tour of duty" model, with most employees serving 2–4 years before returning to the private sector or starting civic tech ventures.
    • Approximately 75% of current USDS employees joined during the Trump administration, with about 10% having served longer than Kutz.
    • The team comprises roughly 180 people: one-third engineers, one-third designers, and one-third product managers, alongside procurement experts and lawyers.
  • Government Tech Challenges:

    • Kutz highlights a massive skills gap, citing HUD as an example where the number of IT professionals under age 30 is zero despite having over 8,000 employees.
    • Procurement issues often stem from a lack of technical expertise among contractors and government officials, leading to "snake oil" vendors and ineffective agile implementations.
    • To counter this, USDS has begun requiring code submissions and technical grading in procurement processes rather than relying solely on written proposals.
    • The "paper cuts" metaphor describes bureaucratic hurdles like the four-year process to gain access to Slack or the need to downgrade software versions (e.g., Acrobat) to function.
    • Despite these hurdles, USDS focuses on "leverage points" to shift the "ship of state," such as enabling veterans to claim benefits or reducing the time for business certification.
  • Onboarding & Hiring:

    • USDS uses a streamlined 90-second application process via usds.gov, bypassing the typical slow federal hiring bureaucracy.
    • Interviews include technical coding assessments and "emotional intelligence" checks to ensure candidates do not have "jerky" behavior.
    • Salaries reach up to $165,000, though compensation is secondary to mission for many candidates.
  • Technology Adoption & Security:

    • Kutz jokingly describes government tech as "frozen in 1995," noting that bug bounties were not implemented until 2016 (16 years after Netscape introduced them).
    • He views progress in moving from on-premise infrastructure to cloud adoption (AWS) as significant, suggesting the sector has closed a 10-year gap in just three years.
    • Regarding deep learning and GANs, Kutz notes that while synthetic data generation is a threat to authenticity, USDS is more focused on practical interoperability and digitizing paper processes.
    • He advises against hard-coding specific technologies (like fax) into law, advocating for functional requirements that remain relevant as technology evolves.
  • Public Opinion & User Experience (UX):

    • Kutz emphasizes that "goodwill" is a quantifiable competitive advantage, citing a $129 billion market cap drop for Facebook as a real-time example of lost user trust.
    • He advocates for "human-centered design," noting that user testing often reveals massive gaps between developer assumptions and actual user behavior (e.g., how users search for USB drives).
    • USDS has engaged thousands of veterans (5,000+) at the Department of Veterans Affairs to build specific features, such as a tool to upgrade military discharge status.
    • He argues that simple, thoughtful design choices (like allowing an at-sign in email fields) build more trust than complex features.
  • Personal Perspectives & Advice:

    • Kutz contrasts the "superficial fun" of Google (on-site amenities, talent density) with the "deeply meaningful" but often frustrating work at USDS.
    • He suggests that purpose and mission are increasingly driving tech talent toward government service, despite lower pay and logistical hurdles like mandatory drug tests and DC weather.
    • He advises tech professionals to engage in policy discussions by attending local council meetings, running for office, or working as contractors.
    • On encryption, Kutz personally opposes government backdoors as security vulnerabilities but acknowledges his role as a government employee where he must support policy decisions made by the political process.
    • He highlights openings at the Federal Trade Commission (FTC) for "technology sort of coordinators" to bridge the gap between tech and policy.
  • Forward-Looking Statements & Opportunities:

    • Kutz notes that "two-thirds of trust in government" is driven by direct user interactions, creating a critical opportunity for digital services to restore public confidence.
    • He encourages short-term commitments (e.g., six-month leaves) for tech workers to contribute without sacrificing long-term careers.
    • He predicts a potential cultural shift toward "digital wellbeing," citing the rise of features like grayscale modes and time-limiting apps as the pendulum swings away from endless scrolling.
Matt Cutts on the US Digital Service and Working at Google for 17 Years — Summary