>I think one thing that needs to be understood better is the concept of "burnout".
I can explain it pretty well.
You can classify pretty much all jobs into 2 categories - map lookups and reasoning.
A map lookup job is something where you learn to associate a specific problem with a solution. Most jobs are like this. You go work in construction, its pretty much map lookup - supervisor tells you to go prep the concrete, you know the procedure to do it, you go do it. Even high end jobs like VPs are often map lookups, you aren't really thinking about solving any problems, just following the standard procedure of what works and are essentially relying on the actual work of lower ranked people to give you data.
Reasoning jobs are those where you don't have the solution for a particular problem in memory, so you figure it out. For example, business strategy, despite being non technical, is a reasoning problem - there are a lot of variables you have to consider, and success in this regard often involves things like figuring out what you have to do, which is a separate task than actually doing it.
Software engineering is interesting because it can be both. Setting up standard service stacks is often a map lookup job. The interviews themselves test on map lookup really, as most of the problems fall within the scope of pointer manipulation or n-linked lists, with memorizing specific hard ones in case you get asked those. But fundamentally, software development is a reasoning type job.
The burnout happens when someone in software engineering is good at map lookup, but is actually needed to do reasoning, and has no education or training on how to do the latter. For example, I worked at Amazon. Id estimate that if I asked a random sample of 100 engineers to give me http traffic from a service, 1 out of 100 of them would know how to do it, and only about 10 or so would be able to actually go figure it out on their own.
This is why people who are good at reasoning can really do any job well. If you take a software engineer who is extremely competent and can build complex solutions, and make them in charge of optimizing things like delivery, shipping and warehouse storage, or finance management of a company (excluding the emotional response to those jobs), they would be able to do it well.
Whereas people who are good at map lookups tend to be only good at certain jobs in certain quantities.