The Exchange Service Engineering role is a distinguished role, specialized in troubleshooting and finding ways to minimize service downtime, that is a result of an impacting incident. The Exchange Enterprise Cloud team is the last line of service engineering engagement, before the need to involve the feature developers. Most importantly, we are part of the Exchange Development Product group.
Here, you will be using your in-depth technical skills in troubleshooting service related incidents, that could be impacting multiple technology areas, but primarily Exchange, and your role is to ensure service is restored as quick as possible.
What does a day in this job look like?
Exhilarating, challenging, collaborative and fun are just a few words that come to mind
At the core – resolving incidents, either that have been raised through our monitoring systems or customer escalated
You could be either troubleshooting Exchange related incidents, or Active Directory, DNS, ADFS, Networking to name a few
When incidents are impacting, typically, they would be impacting multiple users in a customer environment or multiple customers
An impacting incident results in an internal conference call, with the engineer driving it to a resolution; during these incidents, you will be working with some of the brightest minds from various teams, including the Exchange software developers
You will have access to a wiki with extensive troubleshooting articles, a tools repository to aid in troubleshooting
When you are not working incidents, you could be working on scripts to aid in faster resolution time
Qualifications and attributes:
Engineers who love problem solving skills, and think out of the box; who are extremely passionate to learn and grow their technical and coding skills
Someone who is a team player, and enjoys collaborating with smart engineers; who takes customer satisfaction seriously, and takes whatever necessary action to attain it
Someone who is relentless when it comes to getting the problem solved either themselves or knowing to engage whomever is required to solve the problem
Engineers with coding skills, irrespective of the language
You’ll be at a great advantage if you have strong PowerShell scripting skills
Last but not the least, good understanding of all Exchange components
Once every two weeks, you will have an entire day dedicated to training, where you can choose to either grow your C# skills, work on scripts, develop training on certain topics, work on a group project for service improvements, or help contribute to troubleshooting wikis
Deep understanding of all Exchange components, right down to the software code level
Opportunities to learn from very talented Service Engineers, Software Developers, Program Managers and many other disciplines
What about the work days and hours?
This team works on shifts. Before you balk at the word ‘shift’, please hear the rest out!
You will work only 4 days a week, and you will be off for 3 days!!
There is a slight shift rotation, you will work in one of two shifts
1 week working Sunday – Wednesday: 6am – 4pmUTC (8am to 6pm EET)
3 weeks working Monday– Thursday: 6am – 4pmUTC (8am to 6pm EET)
1 week working Wednesday – Saturday: 6am – 4pmUTC (8am to 6pm EET)
3 weeks working Tuesday – Friday: 6am – 4pmUTC (8am to 6pm EET)
Microsoft is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to age, ancestry, color, family or medical care leave, gender identity or expression, genetic information, marital status, medical condition, national origin, physical or mental disability, political affiliation, protected veteran status, race, religion, sex (including pregnancy), sexual orientation, or any other characteristic protected by applicable laws, regulations, and ordinances.
If you need assistance and/or a reasonable accommodation due to a disability during the application or the recruiting process, please send a request to email@example.com.