In scientific computing and HPC, I believe the solution to many problems can be accelerated significantly. For example, redesigning the algorithms in a way that can be benefited from GPUs. Unfortunately, it's not just a matter of rewriting the code, sometimes they require one to completely reinvent the algorithms in order to transform them to a form suitable for modern hardware, and it takes expert-level knowledge of the underlying mathematics and physics to do so. So many people just choose to keep running the decade-old existing code.
On top of that, the expert maintaining the HPC code has most likely personally contributed a lot of the things the code is using to run efficiently on CPUs, so proposing large design changes for GPU acceleration also leads to ego clashes because they (somewhat reasonably) don't just want to completely throw out most of their own R&D.
For the application I'm working with, it has taken ~2 years just to get through basic issues like convincing the scientists of the value of GPU acceleration, striking a balance between their existing methods and restructuring large parts for GPU, and convincing them that instead they'll end up having a lot of room to explore new things like methods which utilize both CPU and GPU.
In the real world, though, as a junior developer, somebody with much more expertise in the business and the technology side of things will be the one making these proposals and your job as a junior person will be to implement them. Get good enough at implementing them, show enough initiative, skill and business acumen, and over time you will be the one proposing ideas. You will need both hard work and good luck to succeed.
Do that... or collect a paycheck and live your life. That also works.
On a related note, a LOT of software suffers from suboptimal performance but it's not usually so bad that it obviously impacts the electric bill.