Last updated on August 23, 2026
Most people have the idea that you can either go into a tech-based major like computer engineering, or you can go into community-centered work that serves people directly, as if these things don’t go hand in hand. There is a whole range of technical fields where building things and helping people go hand in hand, but most people don’t bother to mention them. These are real fields, with real problems and a real shortage of people willing to work.
Start with the people software forgets. The strange thing about accessibility is that the tools already exist. Screen readers turn a page into speech, captions open a video to someone who can’t hear, and voice and keyboard controls can run a whole computer without a mouse. The catch is that a tool only works if the thing you built actually supports it, and most of what gets built doesn’t.
You can see it in the numbers. The most recent testing of the top million websites found that about 96% of them failed basic accessibility standards, and more than half didn’t bother to describe their images at all. That last part is the whole problem in miniature: a blind person’s screen reader reaches the picture, finds no description, and simply says nothing. The technology is working perfectly. It has just been handed nothing to work with. So the job here is rarely inventing something new. It is refusing to leave anyone out, because every site that ignores these tools is a door quietly shut. It’s also an easy place to begin, since tools like the open-source NVDA screen reader take contributors who are still learning.
The government runs on software too, and when that software is bad, someone loses a benefit they qualified for because a form stopped them halfway through. Fixing that seam between a person and the service meant for them is some of the most useful work there is. One volunteer-built tool took a messed up food-stamp application and turned it into something you can finish on a phone in minutes. That isn’t innovative technology, but it means somebody eats who otherwise wouldn’t have.
Then there’s the data nobody has time to use. Many nonprofits sit on information that could show them who is slipping through the cracks or where need is about to spike, with no staff to read it. Turning that into a decision is ordinary data science aimed at a food bank instead of an ad. And when a disaster hits a place that was never mapped, responders arrive half blind, so volunteers trace roads and buildings from satellite imagery and hand them a map that didn’t exist that morning. Humanitarian mapping existed before then, but it came into its own after the 2010 Haiti earthquake, when strangers traced the country from their laptops, and you could take a piece of it tonight.
Beyond these examples are fields tackling some of the hardest problems. Medicine, where software flags the urgent scan before a doctor reaches it. Public health, where a model traces how a disease moves through a city. Climate and energy, where the whole problem is measurement and optimization at a scale nothing else touches. They ask more of you first, but if it is the size of a problem that pulls you, this is where the largest ones are kept.
The skills barely change from field to field and the only change is where you use them. In fact the difficulty is often lower than the work that gets celebrated, not higher. The one rule that outranks the technical ones is that you cannot build for people without them. You need to go out into the world to truly understand what people need. Go out and ask the people who need it. Keep asking while you make things, and the code becomes the easy part.
None of it is a detour from a technical career but instead a corner of one. The barrier is lower than the list makes it sound, because every one of these fields is short on hands. To map a disaster from your laptop tonight, the Humanitarian OpenStreetMap Team breaks it into small guided tasks at tasks.hotosm.org, and groups like the Red Cross use what you make. To build tools for your own city, Code for America runs local brigades you can find at brigade.codeforamerica.org. If your strength is data, DataKind matches technical volunteers to nonprofits on projects measured in weeks, not years. And to stay close to home, Three Square here in Southern Nevada would love a volunteer that’s good with spreadsheets. Ask them what takes too long, and build the thing that fixes it. The idea that technology and helping people belong in separate careers was never real, and the world is far bigger than they tell you.
Comments are closed.