← All guides

Start Here

Exploring Careers in Computing

A map of the field, and how the rest of this guide series fits together. A starting point for students who want to understand the full landscape of computing careers before narrowing down.

Developed by Hasiba Hasin Royesh, Bucknell University, Summer 2026 Research Project, supervised by Professor Darakhshan Mir

Why this guide exists

If you are studying computing, or even just curious about it, you have probably been asked some version of the question: "so are you going to be a software engineer?" Software engineering is a great career, but it is far from the only one.

The world of computing careers is bigger and messier than most people realize. There are roles that blend technology with law, policy, art, health, education, and social justice. There are roles that never require you to write a single line of code and roles that require deep technical expertise. There are paths into government, nonprofits, startups, universities, and international organizations, and most people's careers touch several of these over time, not just one.

This guide does two things. First, it gives you a way to think about that whole landscape without getting lost in it. Second, since this is now one guide in a series of them, it points you to which of the others to actually read once you know roughly what you are looking for, instead of you having to guess.

A way to think about the landscape: two questions, not three boxes

The easiest mistake to make with this field is treating "public interest" or "mission-driven" as a fourth skill category sitting next to software engineering and user experience design. It is not a separate skill set. It is a question of who you point your existing skills toward.

A software engineer can work on advertising technology at a startup, or on a benefits eligibility tool at a state government digital service team, using largely the same technical skill. A user experience researcher can work on a shopping app, or on the interface for a federal healthcare portal. A data scientist can do fraud detection at a bank, or analyze policing data at a research nonprofit. The skill does not change. What changes is the employer and the mission behind the work.

So instead of sorting careers into fixed boxes, it is more accurate to ask two separate questions, and answer them somewhat independently.

Question 1: What is the actual day to day skill?

For the full catalog of specific roles inside each of these, including ones I had never heard of before this summer, see Finding Your Path: Careers In and Adjacent to Computing. That guide goes deep on this question so this one does not have to.

Question 2: Who or what is the work oriented toward?

If Question 2 is what you are actually curious about, specifically the government, nonprofit, and mission-driven side of it, What Is Public Interest Technology? is the guide that goes deep there, including my own path into it and a list of the key organizations in the field. I am not repeating that here.

Honest finding: When I made my first pass at this guide, I listed "civic technologist" and "software engineer" as if they were different categories of career. They are not. Civic technologist is software engineering, or data science, or user experience, pointed at Question 2 instead of Question 1. Once I saw it this way, a lot of my confusion about where a given role "belonged" went away, because the honest answer is usually both.

You do not need a computing degree to work in tech

One of the most important things to understand about computing careers is that the field is more open than most people think. While some roles require deep technical training, many do not.

People working in tech come from backgrounds in political science, law, sociology, journalism, philosophy, public health, biology, art, and design. What matters more than a specific degree is developing enough technical fluency to understand the systems you are working with, not necessarily being able to build them yourself from scratch.

This is not just true at the edges of the field. Stack Overflow's annual developer survey, one of the largest surveys of working developers in the world, has found that only around half of developers entering the field now have an undergraduate Computer Science degree, down from previous years, as coding bootcamps, self-teaching, and other paths into the field have grown.

Many of the most important people in public interest technology specifically are lawyers, policy analysts, researchers, and advocates who learned enough about how technology works to engage with it critically, without ever becoming engineers themselves.

What Question 2 actually costs or earns you

This is the part most guides skip, and it matters. The two questions above are not just about interests, they have real financial and lifestyle consequences, and it is worth being honest about them before you fall in love with a mission and ignore the tradeoffs.

Compensation in computing follows a fairly consistent pattern across sources: private industry, especially large tech companies and finance, pays the most, often by a wide margin. Bureau of Labor Statistics data puts the median base salary for software developers across all industries at a bit over $130,000, but that number blends everything from regional insurance companies to federal contractors to venture-backed startups. Total compensation trackers that focus specifically on large tech employers report medians closer to $190,000 once bonus and equity are included, sometimes far higher in expensive cities. Government and nonprofit roles for the same kind of work typically pay noticeably less, often by 20 percent or more at the entry level, though the gap narrows or reverses at some senior policy and leadership levels.

What government and nonprofit roles tend to offer instead is stability: more predictable hours, pensions or strong benefits in many public sector jobs, less exposure to the layoff cycles that have hit private tech hard in recent years, and, for a lot of people, a more direct sense of who the work is actually for. Academic and research roles trade even more salary for autonomy over what you work on and time to think deeply about one problem.

Honest finding: None of this means you should optimize purely for salary or purely for mission. It means going in with eyes open. A lot of students, myself included, do not think about this tradeoff explicitly until they are choosing between two actual offers. It is worth thinking about earlier than that.

Careers are not one-way doors

It is easy to assume that picking an answer to Question 2 now locks you into it. In practice, movement between industry, government, nonprofit, and academia is common, and it goes in every direction, not just from industry toward mission-driven work.

People start in industry to build technical skill and financial stability, then move into government or nonprofit work once they have that foundation. Just as often, people start in a mission-driven role, decide they want more resources or a bigger technical challenge, and move into industry. Others move sideways, staying in the same sector but switching between individual contributor and policy or management tracks. None of this is a failure to commit. It is closer to the norm than the exception.

The choice you make right after graduation is a starting point, not a life sentence. What matters more is being honest with yourself about why you are making it.

Where do you fit in this framework

This is a short, practical version of a reflection question, not the deep version. If you want to sit with your values, the problems you care about, and what draws you to mission-driven work specifically, that longer reflection is in What Is Public Interest Technology?, and it is worth doing properly rather than rushing through it here.

How the rest of this series fits together

This guide is one piece of a larger set being built this summer. Here is what exists and what is coming, grouped by what you are actually trying to figure out, so you can go straight to the right one instead of reading all of them front to back.

Understanding the landscape

Searching and applying

Growing as a candidate

Building your network

Graduate school

If you only take one thing from this guide: figure out roughly which of the five clusters above you actually need right now, and start there instead of trying to read everything at once. This guide will still be here to come back to.

References

← Back to all guides Next: What Is Public Interest Technology? →