[CoastalCoder]

> Say, I am happy and confident to do all your leetcode/homework assignments + 8h interviews, but I want to be also top candidate as result.

Perhaps not a 100% guaranteed one. Some interviewers just do a bad job.

For example, in some of my recent interviews, the (always young) interviewer posed brainteaser questions that have approximately nothing to do with the skillset and knowledge that the job requires.

I'm sure those questions are good for identifying candidates with very high IQ and/or familiarity with that particular puzzle. But as a very experienced developer, it really pisses me off to be passed over because I didn't answer those to the interviewer's satisfaction.

Long story short: interviewing well is a skill, and as a candidate you can't guarantee a good interviewer.

[riku_iki]

> But as a very experienced developer, it really pisses me off

as very experienced developer, should it be part of your skillset to deal with all kinds of people in the group efficiently and achieve your goal?

As future employee you can't guarantee perfect coworkers..

[CoastalCoder]

> as very experienced developer, should it be part of your skillset to deal with all kinds of people in the group efficiently and achieve your goal?

If you know of a way to convince a 20-something interviewer, during the interview, that the puzzle they picked isn't a good way to winnow down the list of candidates, I'm all ears.

Dealing with people is absolutely a good skill for senior developers. But there are limits to how much interview nuttiness can be overcome by mere mortals.