How do you find a programming job in Auckland?How to prepare for Technical Interviews?

CCI is a fine book, but if you really want to kill it in the coding interview you should check out EPI. After going through that book the interview questions will appear easier in comparison. Just about everyone that I've talked to who got offers at Google used that book. And yes, Leetcode appears to be the industry standard when it comes to preparing for coding interviews online.

I'd also recommend interviewing with a handful of companies and saving the ones you care most about for last since you'll be most well-practiced by then.

I actually can't get any interviews, I've tried to make my portfolio and send my resume to the companys, but.. Even if I try to get into the company as volunteer (to get experience) they don't call me. I'm so unmotivated right now..

Sometimes I just wonder why not send a challenge to the candidate based on the stack that the company uses rather than ask some coding challenges within an hour or so. I think building something real gives so much more insight about the candidate's potential and thought process rather than implementing algorithms that you're probably not going to use in a daily basis, I know it' not true for some cases and this "coding challenges" are meant to see how you solve problems but I truly think (and I see this working where I work) building something real is the way to go when comes to "see what a developer is capable of" and you couldo also bring them over to explain how and why their decisions were made.

After 22 years of experience as a Software Programmer, I had enough, I'm sick, tired, truly disappointed of keep going through this endless nightmare of technical interviews, it has become humiliating. I look aside and I see all my ex-colleagues from High School going to the top of their careers, even those who were truly idiots while I still battling in this endless nightmare. It's not the career I blame, in fact I love coding, but I think the market is a nightmare and I won't recommend anyone to go over this. Seriously, this has destroyed my life, see what the author of that book "Cracking the Codeing Interview" on the 2nd and 3rd paragraph! Sometimes I remember interviews that I would be able to go back in time and have the opportunity to make it different way, I've would never be able to pass it. The outcome is: you can't grow up professionaly this way, you can't dedicate a life to something that add roadblocks any single time in front of you. I read all comments from people quite excited about getting an interview, yeah yeah, I was there before. But you're not going to be young forever my friends, there will be a time when you realize you don't have the same energy in your body and you still have to make a living and pay bills that's when you'll end agreeing with me.

Another important thing, which is briefly mentioned in the book you recommend, is know your technical projects. Especially new graduates; make sure you can talk about interesting team projects you worked on. What was your role? What were the technical challenges? In my experience interviewing, good candidates do much better here. Poor candidates tend to barely remember the projects which suggests that they were not that interested or hands-on.