I changed 4 jobs in the last 6 years and the last one was 4 months ago. So yes, I'm confident. (changed 9 jobs in 16 years for variety of different reasons) Th

I changed 4 jobs in the last 6 years and the last one was 4 months ago. So yes, I'm confident. (changed 9 jobs in 16 years for variety of different reasons) The average software we build is more complex than before too. I guess that's why interviews have become harder. I think I have done around 100 interviews as interviewer too and the biggest problem I see is that many of people that advocate different training programs for passing interviews have wrong idea about the interview process. You shouldn't practice for puzzles. The whole purpose of live coding interview is to see how you communicate and how you approach to solve a new problem. Nobody expects you to implement algorithm in less than an hour and without studying it first. Nobody actually expects you to complete the assignment, even though it's definitely a plus point if you do it. That's the only part of the interview process that doesn't require practice in my opinion (if you know how to code). Instead you should practice your communication skills, debugging skills, best practices, and focus the actual requirements for the job. If they are building distributed systems, they are obviously looking for talents that at least understand distributed systems.