Coming from CSS (Customer Service and Support) I was used to work under pressure. As you can imagine, when a customer opens a support ticket it means something is broken or at the bare minimum is not working as they would like, so being able to quickly figure out the root cause of the problem and suggest how to resolve it a key component to the role. Equally important is to be able to manage those situations when things are really broken badly and the stakes are high: imagine an e-commerce website where transactions keep failing for some reason. The customer is losing money and his customers are unhappy (frustrated? fuming?) and likely taking their business elsewhere. Not nice. As Service Engineer in Azure, when one of our services is down it does not impact one customer, it impacts half a Continent! ? Something I learned quickly in my new role is to think in terms of livesite. What happens if I need to do “x” during a livesite incident? How quickly can I find that information, or get to that tool? This applies to almost everything I do, from seemingly negligible decisions (I need a new Storage Account, how…
Automate Everything