|||

Some thoughts on hiring, quality & public service

What people often misunderstand about hiring in public service is the sheer quality and commitment of those who choose to work in government, especially at places like TTS. Here’s my perspective as someone who led design hiring for years.

Full disclosure: I’m responding to media coverage and have no insider knowledge of current GSA happenings. However, as someone who handled tech hiring within TTS for years, I feel compelled to speak up given recent discussions about staffing. This is written strictly in a personal capacity.

Here’s the thing people don’t realize about jobs specifically within TTS, especially at 18F: For whatever reason, people across industries who work in tech knew about us. Over the years, as civic tech’s lore” (RIP civic tech) grew as the place you go in government when you want to do good stuff or help people, it meant that people actively sought out our job postings when we were hiring.

I was Head of Design for close to four years, overseeing the largest in-house team of human-centered designers anywhere in the federal government. Before that, I spent two years as a first-level manager over product designers. I’ve been involved in a lot of hiring over that time, especially when I led Design at 18F. We’d had attrition over the years that we couldn’t backfill for a long time, but when we finally could, it enabled us to pivot and focus on big priorities like:

  • Growing our UX engineering and product design expertise
  • Expanding our content strategy outfit — still the best in the entire government
  • And, most importantly: building the first in-house service design unit anywhere in government

There might be a few service design leads here and there, but 18F was the first and only place to build a dedicated practice around service design.

Here’s the reality: our job postings would go up for a week — a quirk of the hiring rules — and sometimes they were only allowed to be up for a single day. Even with those restrictions, we’d consistently get 1,000+ applicants for every opening.

A lot of these applicants came from companies you’ve heard of. I saw it not only in the applicant pool but also in the backchannel messages I’d get from people at some of the most well-known Silicon Valley firms who were looking to make a difference. There was a clear pattern: some people had made their money and wanted to contribute. Others were drawn to the decent work-life balance — or at least, what we used to have — and the flexibility of remote work.

But not everyone fit that mold. We had applicants from all walks of life, with all sorts of professional backgrounds, and from all over the country.

Our staff represented the country. I had colleagues from Alaska to rural western states like Montana, from Puerto Rico to the Deep South. There were far more people living on farms in rural states than in big cities. This felt right for the kind of work we were doing — work that impacted people everywhere.

It might surprise some people that public servants genuinely care about their neighbors — even those they’ll never meet. People want to contribute to something bigger than themselves.

Make no mistake: quality was never the issue. Every single designer we hired was top-tier. Even our backups — and the backups’ backups — would’ve been fantastic hires. That’s how strong the talent pool was. In recent years, as people began feeling like it might be okay to work in government again, the pool only got stronger.

I’m not worried about the people we hired finding new opportunities. I’m disappointed they won’t be able to work on the things they cared about. I’m disappointed for the people who won’t get a chance to learn from them. And ultimately, I’m disappointed for the country.

Public service isn’t a consolation prize. Every workplace has its share of challenges — difficult people, inefficiencies, or those who struggle to meet the task. But at TTS, our processes and standards ensured we didn’t let those challenges take root. No one I’ve worked with or seen dismissed in the news fits that category — not today, not ever during their tenures.

Up next Notes on Modernization and System Change Look, we need to talk about what happens when we let “making things more efficient” become the only way we judge system changes. Because right now, Context-Aware Agents: Designing for Alignment in AX AI agents don’t just execute tasks—they shape decisions, workflows, and institutional evolution. If we design them without considering context,
Latest posts March Office Hours The Interface Trap: How Administrative Systems Create Unsolvable Problems Context-Aware Agents: Designing for Alignment in AX Some thoughts on hiring, quality & public service Notes on Modernization and System Change Why would you take a promotion without a raise? Service Design for AI: Why Human Experience (HX) Matters On adapting my coaching philosophy Writing about personal stuff On Goals & Invisible Lines On Secret Hobbies (or About My First Talk of 2025) On Resolutions From Tools to Territory: How Systems Become Infrastructure On Lasting Resilience Scoring Baseball’s Golden At-Bat: Why Finland’s Pesäpallo Already Has a Better Solution Dismantling Things Takes Time What I’ve learned about posting in a post-Twitter world Rushing into the elevator to avoid saying hello Wrote about that one time I was a game designer On AI and Care On House Rules Robbed of thoughts Civil Futures and the speculative present Using a AAAA major league + winter major league to develop fringe prospects Why the pricing out of youth sports so personal 8 Arenas of Action Matrix Assessing the worthiness of posting in the AI era On social media platforms & separation of concerns Why we ought to be (civil) cartographers, not “experience” designers Bringing (advanced) stats to junior tennis Measuring the impact of (design) consequences