I see how working on a SaaS can be exhausting, I have experienced it myself multiple times. Even if the SaaS had no users yet, there was a pressure from the fou

I see how working on a SaaS can be exhausting, I have experienced it myself multiple times. Even if the SaaS had no users yet, there was a pressure from the founders to get a lot features quickly etc. Although on the other hand, it depends a lot on the company itself and its founders. I know a SaaS where founders are hard-core & experienced engineers themselves, and they understand and work with their team much better, because they know what they can expect. From my (limited) perspective and experience, "deeper" you go (closer to the research, or put in simpler words, less people understand what you do :D), less direct outside pressure is put on you. Which is kinda logical, often when non-dev people can visualise the end result (and believe they understand it) they get impatient and cannot understand "why does it take so long to get it done". So I would say these might be the important factors: 1) Founders coming from the engineering/scientific background 2) More hard-tech work domain (e.g. crypto, AI/ML (although a lot of fakeness here), system performance, compilers, ...) 3) Bigger company/institution that can afford to work on such problems