Becoming a civic technologist out of college


I’ve been reflecting a lot lately on my time as a civic technologist—how I got into it, why I do it, what it’s meant for me as a person, and what my life goals are going forward.

The key moment for me came when I saw a talk by Amen Ra Masheriki, the former Chief Analytics Officer of New York City. Amen introduced me to the concept of "open data", explaining how the data that the government (the City of New York, in this context) collects ought to be openly available for all of its citizens to take advantage of and learn from. This was a newfangled concept for me, an aimless college student with uncertain prospects. Before long, I was hooked.

My path has been very heterodox. It’s been intensely exciting at times. In truth, it’s been intensely lonely, even scary, at others. But I know that, especially in these uncertain political times, more and more smart people have, as I did, turned towards civic technology as a way of making a difference.

In this post I'll share some lessons I've learned on my own journey.

Start Local

Particularly among "hacktivists", there is a tendency to want to focus on highly visible national issues.

However, it’s very difficult to break into the federal space. As someone who’s considering putting time and effort towards making a difference with technology, you are likely internally motivated by a desire to create change. However, it’s very difficult to do such a thing on a national stage. You’re less likely to succeed and more likely to simply burn out.

Especially if you’re just starting out in this space, I highly recommend starting locally. Find an issue in your city, town, university, or even neighborhood that you identify with. Find the people in your community that are already working on this issue or in this space; get in contact with them, and offer to help. You have programming skills that are extremely hard-to-get in local organizations, and, consequently, extremely valuable.

For example, a friend of mine became incensed over recent fiascos in New York City’s subway system. I told him that he should get in contact with the Transit Center and the Straphangers Campaign here in NYC and ask how he can help. These are two local organizations whose staff and volunteers that are already actively dedicating their time to this issue, and anything he could do to help these organizations platform their issues would be far more impactful than attacking local politicians’ phone lines.

If you don't have a specific area of focus in mind, the best place to start is probably your hometown (or adopted hometown) Code For America affiliate. Most large cities in the United States have one. In New York City, this is BetaNYC; in Chicago, Chi Hack Night fills this need. Go to their events and get to know the other civic hackers there. Ask around and see what projects people are working on. See what interests you and try to get involved in that. You’ll be in on something in no time!

And if you can’t find such a group, consider creating one! In this political climate, the supply of concerns and people wanting to work on them has never been higher.

Know Your Impact Community

Whatever the issue or area of focus you end up deciding to work on, make understanding your community a top priority.

Be cognisant of who your end users really are. It’s easy to put on blinders and ignore the fact that as nice as your algorithm is, it’s pretty much meaningless to end users without technical experience. The onus is on you to go beyond generating a result: contextualize it, explain, make it obvious to others what your result is and what it says about you want them to learn. Simplify whenever and whatever you can.

For example, the most successful project I've ever worked on in visibility terms was my Starbucks analysis. This project was motivated by a simple question: how commonplace is the Manhattan Starbucks? It is executed using a simple metric: mean distance to Starbucks. And it is bookended by a simple presentation: a bar chart comparing this distance for various chains. It caught lightning precisely because of how simple and identifiable these concepts are.

Such presentational skills are something many newly minted software engineers struggle with precisely because they are not emphasized rigorously in collegiate computer science programs. But technology in government is much less cloistered than it is in industry. For a civic hacker explanatory skill is a day one necessity.

Secondly, you need to know and learn from others working in your space. You fail to take advantage of the experience of others at your own peril. No matter what issue you're interested in, there are folks that are already working in this space, potentially for decades. In government, details are proprietary: procedures are established ad hoc, don’t always follow set rules, and are never completely documented anywhere. It’s incredibly easy to go into a problem thinking you know something, only to discover later that actually you were utterly, foolishly wrong. Flawed assumptions can tank even the brightest-looking of projects. Make working with stakeholders and verifying the ground truth a first-order priority.

Have a Portfolio

This website has been immensely helpful for my career. I strongly encourage anyone working in this space to have an online portfolio. The people that will hire you, work with you, and volunteer with you will rarely evaluate you based on whiteboard algorithms - they will want to see that you have experience in the field, that you’ve worked on hard problems in this space and solved them, and that you’ve got a talent for explaining your results. Give that to them!

Go Where You Will Have Impact

This is likely the hardest one of all: work on projects at places where they are likeliest to have the impact that you want to have.

The world consists of many people doing many things, and the great and exciting and sometimes scary thing about civic technology is that it exposed you to many of them all at once. There is always more than one way to do something.

If you want to hack on transit data, for example, you might want to find work at the MTA data team; or work on it in City Council; or at a non-profit like Transit Center; or a for-profit company in the space (like Google Transit or the Transit app team); or a research project at NYU CUSP or Cornell Tech; or keep your day job and hack on it nights and weekends; or set up a hackathon or ideathon at a local tech meetup; or create or work in a startup (like ARGO Labs or Sidewalk Labs); or hack on it with/for a local publication like amNY; or enroll in a degree program at NYU CUSP or Cornell Tech, and launch into it that way.

All of these approaches have pluses and minuses. As someone very early in your career, it’s very hard to know which way works best for you. The only advice I can give is to try to explore as many of these options as possible. Talk to people that have gone particular ways, and learn from their experiences what the tradeoffs are. Try and get some first-hand experience by working on projects with a variety of organizations. The experience will guide you down the road.

Oh, and if you’re on the Google/Microsoft/Amazon/Facebook et cetera career track, know that anywhere else you go will be far more financially precarious. Later in your career, the pay and prestige that comes with working in privileged tech companies like these will matter far less; but when you’re in your early 20s the feeling that you’ve "made it" by working there feels terribly important. Many, many people work potentially unrelated jobs in the daytime and moonlight on civic projects nights and weekends. It's a valid thing to do.

Create and Maintain Connections

Finally, my last piece of advice is: work hard to create and maintain connections to the other civic technologists.

In the government, who knows what matters less than who knows who (just ask lobbyists). Positions and places that you will want and that will want to hire you and/or work with you will rely very heavily on reputation, and knowing you ahead of time. You need to have a strong network in place in order to be able to find and capitalize on opportunities, a network you can only form with work, time, and exposure.

So put yourself out there!