I recommend the pharma industry or any other science-heavy field. It's sort of hit and miss, but sometimes you get a research project where it's the experiment

I recommend the pharma industry or any other science-heavy field. It's sort of hit and miss, but sometimes you get a research project where it's the experimental results which make or break the whole thing - your role is to support the experiment with the software you write. Example, since this may sound too vague: I'm currently in a project that started off as a research paper and associated Matlab code. Problem is, you can't ship this to people who just want to see the results and don't have the proper computing power on their work laptops to perform the necessary calculations, so we built a whole web app which does all that at scale. Other times you do a boring compliance/business application, but such projects are usually timeboxed and with unchanging scope. Example: 9-months, 11 devs and the result was an app where the user clicked a button once a month which made the backend talk to 15 different APIs that in concert created the last section of a 2k page PDF file because regulations said so. Boring as hell but it was over soon enough and even got an internal award for "least(zero) complaints".