| You need to pressure them. They have no incentives to change this system, so give them incentive. There are so many red flags in your post, if I were you, I'd start looking for my way out immediately (I don't know your personal situation so ymmv). Company culture changes slowly, and based on the number red flags, I'd say it's probably easier to leave and find something better. If you are staying because you like working with some people, ask them to consider joining the same company where you get hired. If you try to change the organization, be prepared that people will stop liking you because you are not the obedient little code monkey anymore and they won't like that you don't let them exploit you anymore. > on-call isn’t compensated with the rationale that it’s part of your engineering duties That's just wrong, do not let them convince you this is normal. If they want you be available at all times, then they should pay. If they don't want to pay, tell them you won't do on calls anymore. > In a gambit to prioritize uptime over engineer time I see they are very generous with your time. > Being able to sleep fully through the night is increasingly rare. Again, it's a sign that your system is unstable. You need to ask them to prioritize fixes to these issues, even if they can't be solved easily. Take a good look at how development is organized. Do you have automated tests, code reviews, knowledge sharing? Are you always working on features and ignore bugs? Running systems should not be this hard. > yeah, we’re looking into it This is an acceptable answer exactly once. > The company could easily afford it, but probably doesn’t want to pay for what it can get for free. I didn't want to be philosophical but: Power concedes nothing without a demand. |