Maybe this is good generic advice to some, but this is not how to "pass" a technical interview. In a technical interview, the interviewer needs to determine whe

Maybe this is good generic advice to some, but this is not how to "pass" a technical interview. In a technical interview, the interviewer needs to determine where your skills lie - would your skills fit within the team? Does what's listed on your resume match with your answers? Is your learning book-knowledge or from experience? How do you respond when shown a very difficult problem? You can't BS your way out of these by "taking charge" and trying to trick the interviewer to move on to soft skills questions. Maybe your advice works in certain situations but, against a full on neck beard who cares only to see if you know data structures and OOP, your advice would guarantee that you do not pass the interview.