Interviews with senior members of departments went well. These included standard "what do you see yourself doing in N years" questions and explanations of their current work, with a good admission of weaknesses, which was why they were hiring.

The issue arose during the technical interviews. The dual panel consisted of team members from separate teams, and one panelist lacked strength in the technical requirements and questions for a deep dive into Linux SRE/DevOps. Questions involving strace, debugging file systems, and similar topics faltered because the weaker panelist was seeking exact answers from a rubric and lacked the knowledge to assess and respond to follow-up and clarification questions. The interview devolved into a discussion about my lack of knowledge of their internal troubleshooting procedures.

It's a shame, as we had previously had amazing conversations about Linux kernel internals, radio-to-user land interactions, systems design, and more.

If a filesystem stops responding, how do you go about troubleshooting this?