Can you tell me a little more about this? I'm enjoying my current job as a coder, but I'm also feeling a hankering for something like what you describe. Feeling like I'm producing something a little more tangible would be nice.
My computing interests lie in automating tasks previously performed by humans, ETL, and analysis. I was doing web stuff back in the 1990s and went through so very many CRUD apps, but this is where my interests lie. What this means in my current job is that I find time-consuming tasks done by my predecessor and say, "Let's make this faster." Or I can look for subtle errors.
Just as an example, because I am routing emergency services to houses and workplaces, I have a network of streets to deal with. Imagine them as a graph, where most of the data is attached to the edge rather than the node. Now, people have drawn these streets in using tools like ArcMap, but there can be problems. How many different kinds of mistakes might exist in connecting roads together? Try to enumerate the cases.
I have found ten thus far. Each case is something that, if a human eyeballs it up close, they could say "oh yes," but it is not readily apparent. And so I have written code for a number of these cases that takes my human domain expertise of what is wrong with something and translates it into something even a rock (silicon) can understand. And the end result of finding these little mistakes is very real: help gets to someone just a few seconds faster.
I interface with organizations that are not other IT organizations: property records, postal records, phone records, and so on. Sometimes this means wrangling proposed plats from developers. It's all real stuff, and it's all done in service of helping people who have immediate needs.
It's very different from being in a room full of people who have little stickers on their Macs making Agile noises about whatever random shifts have occurred in the "client??" (and doesn't that word encompass a multitude of sins)'s latest wishlist.
My guess is that tons of these kinds of jobs are out there because the real world still exists and the people in it are often using computers, but perhaps not as "centrally" to their jobs. However, people like you and I can provide options to them that they did not have before, and sometimes may not have even envisioned. Just as a case in point, this new place was setting up some machines and had a few tedious configuration problems, so I used batch files and a few more things to save them time and add reproducible results. They were shocked but this was stuff for me where I had to dust off things I had forgotten a decade prior.
In my previous job, I found areas of satisfaction as I noticed above, and they were all tied to people (not users), to physical objects (rather than instatiations of some class), and so on. I noticed how much churn there was, how often things would have to be redone not because anything realistic demanded it, but because of style, or some kind of platform migration, or something else End-of-Lifed, and so on. Indeed, constant platform migration made me realize that nomads are not known for their lasting works of architecture.
I was part of that big "brain drain" where someone says, "Hey, you are good with computers, right?" and off I went. I had figured out that the sciences would be long and without a lot of payoff, so I did not look back too hard.
I suppose I got a reputation as someone who gets a far-off look when an interesting problem is described and was asked to apply to my current job because of it, despite it being a different sector and problem set.