I have worn many hats for many roles throughout my experience, and at the end of the day my passion is about driving software quality through data. You know you've made it when you can confidently deploy to production on a Friday because you're system will automatically do a rollback based on the data if there's anything wrong with the update. Then send a notification to the update author as to why it failed and was rolled back. Coordinating this effort often means frequently switching between the roles of a software developer, an operations engineer, a data analyst, a software tester, a modern testing evangelist, product manager, and a cross-services systems engineer.High quality needs to also be business sustainable. If the latest new feature reduces the error rate of your service by 10% but now for every $1 you make you spend $3, then while you have temporarily increased quality, you are also guaranteeing the eventual financial death of the service beyond which quality can no longer be delivered and decreases quality long term.