Tier 2 Vendor (Core .Net) support

MSBuild familiarity: Be able to understand MSBuild output and project file format with the ability to track down the source of an error. Ideally should have at least some experience with both desktop and .NET-Core-based MSBuild

-VSTS familiarity: Be able to use VSTS online to look through build history, agent pools, and other aspects that may help understand a specific build failure reason.

-GitHub familiarity: Be able to navigate issues in GitHub, using the ZenHub Kanban plugin, updating, assigning, and labelling issues as appropriate.

-Operating Systems: Be able to use systems running MacOS, Windows, and Linux enough to troubleshoot common file system issues (file ownership, file handles, disk space, etc) and find system logs. Investigations where the problems appear to be related to machine state will require investigation of the machines used for builds.

-Scripting languages: Python, Powershell (both Desktop and Core versions), Bash, and cmd scripts are all used as part of our builds. While you won't be expected to write in these languages, being able to understand and debug them is essential for understanding build issues.

PREFERRED SKILLS

These skills are not mandatory but will help:

-Basic use of command line debuggers: Be able to attach a debugger, get a managed call stack, and create a minidump using windbg/cdb on Windows, lldb / others on *Nix systems.

-VSTS Yaml-based definitions: Be able to parse the new .yaml build definition format and debug issues

-Git: Be able to use GitHub or other sites to track down change histories, "blame" specific changes on users, and in general be able to navigate through Git as a source control system.