TechCongress, a program which places technologists on Capitol Hill to advise on technology policy, fundamentally changed the course of my career. Like many other high-quality programs, however, it is competitive, and the success of an application depends heavily on the responses given to several short-answer questions.
When I was preparing my application materials, particularly the policy memo, I faced significant writers block. One of the things that helped me get unstuck was a blog post from B Cavello, in which they shared the responses that led to an acceptance into the program.
With this post, I'm also going to share the core of my application, in the hopes that it provides some inspiration to future applicants and helps de-mystify the process. As always, if you're seriously considering TechCongress and would like to chat with me directly, I welcome emails.
Tell us about your qualifications for the Congressional Innovation Fellowship. Think about highlighting how your strengths and experience will help you to succeed in the program and in Congress. (Enter up to 150 words)
As a student, I studied the theory underpinning our digital world. And between semesters, I contributed to that world, building mobile and web applications, Internet-of-Things devices, and open-source projects.
At the General Services Administration, I learned how to engage with users, before writing code. I fostered trust with stakeholders by playing translator, unpacking technical jargon and, in the other direction, writing software according to described needs.
I doubled down on this human-centered approach at Flexport. I prioritized careful design: shadowing users, gathering requirements, and writing plain-term proposals. I observed the impact that clear technical communication could have; in turn, I discussed our software systems in memos, talks, and blog posts.
In Congress, I aim to craft policy that is informed and needs-driven while ensuring alignment with every collaborator, regardless of their technical ability. All my strengths and experiences will, I believe, make me an intensely curious, collaborative, and effective Fellow.
Rapid changes in technology have created a number of challenges for Congress. You are working in a Senator’s office and have been asked to write a memo about a technology policy issue. Remarkably, the issue you've been asked to write about is an issue that you have experience with, but in which the Senator and his or her staff have very little expertise. (You can also pick an issue that you may have less experience with but that you find interesting and think is important for Congress.) Describe 1) the nature of the problem, and its significance (while taking care to explain any complex technical concepts) and 2) your solution and recommended course of action to advance your solution. (Enter up to 350 words)
SUBJECT: Stimulating federal diligence and investment in open-source software
BACKGROUND Our modern economy is buoyed by the work of volunteer programmers. These volunteers write publicly available, free code (known as “open-source software”) that over 97% of businesses depend on. This software fulfills critical needs common to every business and industry: things like operating systems, programming languages, and machine learning tools.
The role of open-source software in our digital economy is akin to that of roads and bridges in our physical economy: it forms the infrastructure upon which all businesses operate. However, there is a key difference. Physical infrastructure is largely built and managed by the government, while digital infrastructure is built and managed principally by self-organized groups and individuals (known as “maintainers”). ISSUE The decentralized nature of open-source software production and utilization presents considerable risks to our nation’s security and economy. Indeed, recent vulnerabilities in ubiquitous open-source projects – like the “Heartbleed Bug” in 2014 and the Log4Shell exploit in 2021 – have threatened user safety and privacy, compromised critical data, and wrought substantial costs to governments and businesses. And due to the interdependencies between open-source software, the “blast radius” of a vulnerability can be both massive and unpredictable. Moreover, attacks on the open-source ecosystem – not including vulnerabilities introduced unknowingly by maintainers – have increased by 742% over the past three years. In the absence of a coordinated, public-private plan to secure open-source software, these risks will continue to fester.
RECOMMENDATIONS
Explain your reasons for wanting to be a Congressional Innovation Fellow. How will the fellowship 1) improve your capacity to effect change and 2) fit with your career plans? (Enter up to 150 words)
When I began studying computer science, I felt that our nation’s biggest problems could be solved with apps and algorithms. After working at several companies, I concluded that software is indeed a tool with the capacity to effect change, but it is so often abused.
In public interest technology (PIT), I observed that same tool wielded for good. My foray into PIT led me to technology policy as another lever arm for change, one that could act as both guardrails and lubricant for technology deployment that actually improves lives.
I then found TechCongress, and I saw in its fellowships the door to the policy world that I was searching for. As I pursue a career in PIT, I want to be fluent as a technologist and policymaker, combining these disciplines to drive technology innovation in the public interest. Serving as a Fellow now is vital to achieving my policy ambitions.