The best is to work for a low traffic backend/back-office/api used internally.. Less risks of downtime, lower damage if it does go down too. No stress with scal

The best is to work for a low traffic backend/back-office/api used internally.. Less risks of downtime, lower damage if it does go down too. No stress with scaling, online migrations, optimisation... I used to work (internship) for a tiny internal backend which only was used maybe once or twice a day. It could have been down for hours and no one would care or notice. If a bug slipped into "live" environment, the worse that could happen is a co-worker phoning me saying "oh yeah I tried to use that and it didn't work, can you help me?" On the flip side you might learn less than working on an high traffic application because high-volume creates a whole new lot of potential issues and things to watch out for. I think I would choose a chill job like this again when I'm older