[harshalizee]

Then you shouldn't be asking those questions in the first place.

Why do you want a job?, Why do you want to relocate?, Why do you want to work here?, etc. are BS "no-op" questions that are not relevant to the skills that they are promoting.

If an interviewer asks these types of questions, they are literally showcasing that this part of the interview is a BS "Subordinate yourself to the desires of capital in all areas" conversation. You will predictably get the "no-op" answers you asked for.

The interviewer always sets the tone of the meeting. You can't complain when they chose to play along. If you want a real conversation, you need to make it amply clear.

[BrandoElFollito]

"Why do you want to work here" can be insightful.

I like to be asked this because I can for one tell the truth, and then see how the interviewer responds (when this is at an advanced stage of the process, with real people)

[Aurornis]

> Then you shouldn't be asking those questions in the first place.

> Why do you want a job?, Why do you want to relocate?, Why do you want to work here?,

I never said anything about those questions or even the type of questions. Did you confuse my comment for someone else's?

The no-op answers I was talking about can come from any question, including technical ones. Some candidates will tell talk in circles for 30 minutes about the company's product and how the team did amazing things, but you can't pin them down to explaining what they did or anything that might prove they know what they're talking about.

They will change the subject at every opportunity and talk your ear off with things regurgitated from blogs, but you leave the interview feeling like you wasted 30 minutes because they were so busy dodging every question and combining words together that they thought you would like to hear.

One alternative is to skip the conversational format and go straight into coding and deep technical questions, but hey guess what? There are people who will hate you for doing that too!