Not really, most questions have answers and discussion threads - during an interview you can see people just writing up solutions flawlessly - they just memorised them. I have interviewed 100+ people.

I don't think regular coding questions, LC tell you anything meaningful in an interview.

I'm more experienced now, so refuse doing it and recruiters and interviewers get all funny about it. But please, please interview. I know I'm pretty privileged compared to others but I won't ever do a LC question anymore and tell that upfront to Google and the likes. I have canceled loops because of the inflexibilty of some companies in that regard.

Sometimes they tried sneaking it in last minute - also tells you much.

Can I ask why you refuse? For me it is more of a formality at this point. I know it won't tell a lot about me, except I cared enough to put in the hours to get this job, but still you have to do what you have to do. I'm pretty senior as well but don't really see why I should not do this when everyone else has to.

In general though the tech industry has a really hard time hiring senior people, perhaps for this reason. I was at Google for 10+ years and did 100+ interviews, HC etc and once you talked to the people in charge of the process they admitted that the process is really weak for hiring senior (L5+ in Google speak) candidates. They in many ways perform worse than new grads in coding interviews which is not really surprising.

So Google hardly hires anyone experience before you get to the director levels (hardly as a percentage of course).

The other well know secret is that if all of us would try to do an interview unprepared we would probably fail.

As someone who refuse myself I simply think it is a waste of my time. It isn't fun, it doesn't teach me anything I find interesting and it isn't a good way of filtering someone.

I would rather be with my girlfriend, play videogames after work hours, watch netflix, go see some friends.

I lost a team member to Amazon recently, he spent 6 months total (two 3 months stints) preparing for the interview. He bombed in the 1st try and passed in the second.

That's 6 months of your life studying after hours to get a job ... I really have better things to do!

He is there now and he says how his work is not as challenging as the one we were doing from a technical PoV and also how the culture is very toxic compared to ours.

Anyways... he is optimizing to retire early so props to him I guess.

I don't do whiteboard coding. When I thought it was meaningful, or might be meaningful, I did it even though I'm uniformly terrible at it. If I was great at it, I might do it even though I no longer think it's meaningful.

But I'm terrible at it, and I don't think it's meaningful, so I don't do it. Admittedly, it costs me some opportunities, but mainly at companies I'm not sure I want to work for, anyway.

At this stage I'm an old fart with a long resume, and more often than not I get hired by people who already know my work. I guess if I was as bad as my whiteboarding performance makes me look then people who know my work wouldn't want to hire me.

So I think this is partially why these questions actually have value. They cannot completely be faked, you need some level of competence even after months of leetcode.

I witnessed someone who couldn't code fizzbuzz end up at our company (OK it could have been an acquihire or something) then get fired, and then immediately hired at Amazon at a pretty good office. I always had a nagging doubt this person paid someone to stand in for the interviews. Thinking back, who actually cross checks this kind of stuff? Unless they know each other personally or take DNA/fingerprints it wouldn't be very hard to pull it off.

for me atleast that also came with experience. ie that would have been impossible in my first job search. But repeating the process of searching for jobs a few times over a decade, each time i’m preparing for interviews i’m able to build somewhat on previous times to where problems like that are manageable.