I expect front end people to be able to fire up developer tools and tell me where to troubleshoot slow network responses definitively as DNS related before fili

I expect front end people to be able to fire up developer tools and tell me where to troubleshoot slow network responses definitively as DNS related before filing a support ticket saying “my queries are slow because of DNS.” I wound up training network engineers how to use Chrome dev tools at a really large company because so many frontend developers knew absolutely nothing about troubleshooting network issues that they were disproportionately filing network support tickets. I usually try to focus on what the interviewer wants me to demonstrate knowledge on when I answer the question in an interview. As an interviewer I normally avoid the question and make it more job specific. I might ask about troubleshooting slow servers based upon an incident and try to determine the candidate’s thinking pattern and methodology. For developers it’s easier to ask “this block of code is not doing what I expected, what did I do wrong?” where the mistake is a very common one. I actually had a very practical HackerRank problem that asked me to troubleshoot a program and an accompanying docker compose file. If you had prior experience this would take you 2 minutes while you wonder if that’s really the whole problem.