Microsoft Visual Studio -- Senior/Staff Engineer

Summary We're looking into the developer tools space and want to understand in detail, how engineering teams build software. What you'll do (5–10 hrs/week to start) Showing us your real workflows in Visual Studio: how you structure and navigate a large multi-project solution, debug a failing build or flaky test from breakpoint to root cause, profile and fix a performance bottleneck, and take a change from feature branch through review to a clean merge without leaving the IDE — and answering questions along the way: why this step, what's the shortcut, where do people go wrong? If you use Visual Studio regularly and can talk through your process clearly, you're exactly who we're looking for. No prep needed, just your day-to-day expertise. Who you are — any of these backgrounds fits - .NET / Backend Engineer — you live in large C# solutions: project references, NuGet management, build configurations, and the debugging and test workflows around them. - Enterprise Desktop / Native Developer — you maintain long-lived WPF, WinForms, or C++ codebases, and keep them building, debuggable, and shipping through framework and toolset upgrades. Must-have: 5+ years of hands-on, near-daily use of Visual Studio (not just VS Code); fluency with the debugger (breakpoints, watch windows, call stacks, diagnostic tools), solution and project management, Test Explorer, and the built-in Git tooling; able to articulate why you do what you do, not just click through it. Nice-to-have: experience across more than one of the profiles above; migrations or modernizations touching Visual Studio (.NET Framework → .NET 8+, MSBuild customization, ReSharper, Azure DevOps or GitHub integration) or admin of enterprise rollouts (licensing, extension policies, standardized environments).