What does the Cloud ES team within Azure PIE group at Microsoft exactly do?What does "ES" stand for? Engr. Services or Eco System or something else? I found that it deals with developing services for monitoring and app diagnostics. If that is true, are these internal services or external, customer facing services? Will this be a great career move in the cloud space as a SDE? Please provide insight.
I think engineering services
@SignDocu what do you think on my other questions? Please share your detailed perspective. Will be helpful .
@Soylearnt @SignDocu ??
Azure SRE took on some other charter (Geneva monitoring) and are now called Cloud ES (engineering services). Check Blind for Azure SRE org and posts would indicate that org has not been as effective in making changes.
Oh thanks. Looks like a lot of livesite as well!
This post is still open for people. I request you to write your perspective on this org and why should / should not I be working here?
When the platform gets bigger day by day, it is more difficult to advance for sure. Majority of the Azure products rely on cloudes infra. How good they are depends on how u see it..
So basically I won't be working on azure cloud services? In other words, my work won't be directly impacting users of Azure cloud services, instead my work will impact Azure service developers in their productivity. That means our team will be responsible for building/maintaining internal tools/infrastructure? Is that correct?
If you have a service engineering background or SRE role, it maybe a good fit. If you want to be working on Azure services, look for jobs in Compute, Networking or Storage.
I am fairly new to the s/w industry and looking to make a background and I don't want to be into SRE/data center/devops type of roles. I thought the cloud ES team deals with developing monitoring/diagnostic services for Azure customers but from your response it looks like I am wrong so I would probably go look somewhere else! ☹️
A monitoring team has been moved under ES. Todd Curtiss moved from Google SRE to Azure and rebranded the SRE org. The org has nearly quadrupled in size but internally I am hearing they are bunch of overhead folks, preaching folks on how to do stuff but no one is taking notice of that. Other than some internal monitoring tools, the exact role and accountability of the ES team is unclear. SRE teams have been dismantled in many parts of MICROSOFT over years, let’s see how this one goes.
Stay away
@Soylearnt: Why???? Please explain in detail.
@Soylearnt: what kind of work are they involved with? Is there no learning curve?