Are you interested in working on a team that enables developers across Windows to deliver their innovations on any platform, whether Desktop or Server, HoloLens, ModernPC or other devices? Hundreds of millions of devices run Windows, and they all have to be composed, manufactured, deployed, and kept up to date. Would you enjoy applying your development and problem-solving skills in making any of these areas even better?
The Deployment team consists of the Composition, Servicing Platform, Setup & Imaging and Deployment Solutions teams. Let’s look at how they collectively build the OS deployment story.
|
Responsibilities
The building blocks of Windows are the packaging system. Investments here enable the organization to enable new device form factors and help with the developer experience so that developers can focus on building their features without worrying about how Windows is constructed. This package graph is processed and turned into thousands of files and registry entries and captured into Windows images. Tooling allows OEMs, System Builders and Enterprises to take these images and customize them and add content to them. This tooling also serves as a platform for other Windows teams to build extensibility stories for these images.
Windows images then need to be deployed - this can be done locally, over the network, or via flashing directly to disk. Optional features can be added or removed from these images, and various Editions can be selected. When it comes time to update images, whether via Quality Updates, Feature Updates or WCOS Updates, update payload is managed in package repositories and acquired from WU and other sources. This content has been compressed in the build labs and just the necessary bits are sent to each device. Users are notified if there are update blockers and can resolve them. Enterprises can manage this update flow as well, with as much or as little control as they’re comfortable with. As much of the update as possible happens in the background, invisible to the user. With the Non-Event Objective (NEO), the downtime taken by these updates is driven ever downwards for minimal user interruptions. During the update process, user and system state is carefully safeguarded and preserved and carried across the update, via migration, diffing, or state separation. Teams throughout the org integrate with the update process to ensure their content is updated and preserved as necessary.
There are many exciting opportunities in all these areas and more, far more than can be listed in this email. If this has piqued your interest, please let us know!
|
Qualifications
- B.S. in Computer Science or a related field, or equivalent industry experience
- 4+ years of coding experience with C++/c#/Java and rigorous quality engineering practices across all phases of product development, deployment, and validation
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. We also consider qualified applicants regardless of criminal histories, consistent with legal requirements. If you need assistance and/or a reasonable accommodation due to a disability during the application or the recruiting process, please send a request via the Accommodation request form.
Benefits/perks listed below may vary depending on the nature of your employment with Microsoft and the country where you work.
Get email alerts for the latest"Software Engineer II jobs in Redmond"