Earlier quoted context omitted.
Even if you do work on Windows in-box code only, it might not be so easy. Here's another issue you raised with your old job: > 2. Debugging exclusively via metrics and logs, since I can't just attach a debugger to a running server. I find debugging Windows issues fun, but it might not be for you. On rare occasions, you might be lucky even to have telemetry and logs, for customer issues that can't be reliably reproduc…
To be fair, Watson post-mortem debugging is something that pretty much every team that ships a product running on users' hardware has to deal with.
As an aside, if you are a third-party Windows application developer, I highly recommend you register your apps with the Windows Desktop Application Program: https://docs.microsoft.com/windows/win32/appxpkg/windows-des... - this will give you access to the same app reliability telemetry, including user-mode crash dumps (.DMP / .CAB files), that Microsoft has. This is only the latest of several iterations of this data access over the years, but it and its predecessors are still badly underused in my non-Microsoft experience.