Azure cloud solutions architect role interview process
Jul 9, 2021
5 Comments
Asking this for a friend who wants to try at msft for the cloud solutions architect role. Questions-
1. Interview process/ # of rounds
2. How Technical ? Coding is needed or not
3. System design questions are asked or not
4. general guidance
5. Salary range for 63/64 level
6. Any sample questions ( I am aware of the NDA, so not pushing on this one)
Any insights is going to help.
Tc - 220
Location- Seattle
comments
I’ll tell him the details.
Also can I DM you on this ?
2. Again, depends on the team and role. In Infra on my team, we usually look to see how broad they are and go 300/400 level in a couple areas to see where their experience is.
4. Show that you understand business problems and can translate those to a technology solution. You don't need to know all the nuts and bolts, but should be able to connect the dots reasonably well. Show you can work in a team or independently.
5. Depends on area it's a 70 base/ 30 salary role.
What about the system design questions? and whiteboarding needs?
Are candidates get asked to draw an architecture or explain things on the architectures ?
I don't think you're going to get into deep system design, this role touches a lot in Azure, so breadth of experience, or showing that you love to learn technology and can be good in front of customers is more important than how to design around scaling 10000 vm's, imo.
Interviewing for the field is a lot different now, when I started in this role just before Covid, I was instructed to prepare a presentation that included an architecture design and be prepared to talk about why I decided on this, what business problem I solved and technically how I got there. The field is doing a new hiring approach now, so they're looking to see if it's a MSFT fit first, then see if you match up with the role.
All this could be completely different if this is for a CSA role that supports one large customer, I've seen those teams look for specific experience that will be beneficial to the customer (IE: how to approach scaling out 10k vm's or migrate vs modernize applications etc.)