Cover photo

The Civic Technologist

The robots report to city hall.

Nye's Digital Lab is a weekly scribble on creativity in an age of rapid change.

This week I'm looking at who actually decides what the robots on your street are allowed to do, and why that's a job opening.


Essay # 105

Six

On October 1, 2013, HealthCare.gov opened its doors. Four point seven million people showed up. Six of them managed to buy insurance.

Not six thousand. Six.

post image

The lazy take is that government can't do technology. That's not really correct, though. The site was built by 33 companies on 60 contracts, led by a firm whose piece of the job roughly tripled in cost before anyone saw it work. The final bill came in around $1.7 billion. Federal procurement was designed to purchase aircraft carriers, and a website got bought like one.

A handful of engineers from Google and a few startups flew in, got nicknamed "the tech surge," and within months the site was enrolling millions. Jen Pahlka was deputy CTO of the United States at the time. She watched a team of about a dozen developers rebuild most of the marketplace in a fraction of the time, and she went on to write Recoding America, the book I'd hand anyone who wants to understand why government software is the way it is. Her point is simple.


Government doesn't lack talent or money. It lacks a connection between the people who write the policy and the people who have to make it run.


Washington took the lesson to heart for about a decade. 18F and the U.S. Digital Service were created in 2014 to put real builders inside agencies. In March 2025, 18F was eliminated in a day and the Digital Service was folded into DOGE.

Um. Whatever you think of that, the federal chapter of civic tech is closed for now.

But, I don't think that's where the interesting work was going to be anyway!


The Robots Report to City Hall

The next wave of civic technology isn't a website. It moves.

In May, food delivery robots showed up on the sidewalks of San José. By July the city was writing rules for them. Miami Beach already had rules:


8 miles an hour, and no idling on the sidewalk for more than 30 minutes. In February, the association of city transportation departments put out a guide for mayors with a title that says it all: Robotaxis Aren't Coming, They're Here.


This is not Congress. Not a federal agency. A city council, on a Tuesday night, with a microphone is making local decisions about robot deployment.

An autonomous system doesn't interact with "society." It interacts with a curb. A crosswalk. A permit counter. A 911 dispatcher. These are a local government domain, and there are 91,438 of them in the United States! Each one buys its own software, writes its own ordinances, and answers to the people who live there. When a robot does something dumb on Broughton Street, nobody calls the Department of Commerce.

They call city hall.

And it isn't just the robots. The AI is already inside the building.

The decisions that shape how machines behave around people are being made in rooms with folding chairs. And the truth is that most of those rooms don't have a technologist in them!


post image
Civic Robot, Leonardo.ai/FlowState

Go Local

Here's my point.

There's a big, established industry that builds technology for the federal government. Deloitte, Booz Allen, Accenture. It runs about $40 billion a year, and it's built to staff a 500-person program for five years, because that's what the federal market pays for. Fair enough. It also means those firms have no reason to chase an $18,000 pilot in a town of 40,000.

That leaves 91,000 local governments to whoever shows up.

Government Technology's list of the top 100 companies selling to states and cities has an average company age of almost 19 years.

It's a slow, relationship-heavy market where incumbents stay forever, which means the ones who get in and stay get paid for a very long time. OpenGov started selling budgeting software to cities in 2012 and sold to Cox Enterprises in Atlanta for $1.8 billion. Ten years ago venture capital treated govtech like a charity. I'm not so sure that's the case today.


So what is a civic technologist?


Someone who can read a council agenda and a model card. Who knows how a permit actually moves through a building. Who can explain to a fire chief what a robot's log says, and explain to the people who built the robot what the fire chief needs. It's a product job, a policy job, and a neighbor job at the same time, and almost nobody is training for it, in Washington or at most universities.

Robots are moving down my street, and the people deciding what they're allowed to do are a short walk from where I'm sitting. That's not a problem. That's the job opening!

Make it Happen.


Colophon

This essay was researched with generative models, then written and revised by a human tapping on a keyboard.

Nye Warburton is an artist and educator from Savannah, GA.

For more information: nyewarburton.com


More from the Lab


Sources

In the order they appear in the essay.

HealthCare.gov and the federal story

Robots, cities, and who decides

The market outside Washington