What Tech Interviewers are Trying to Find Out

To feel comfortable during the interview process, it helps to know what questions the Interviewer *wants* to ask, but can't. Clearly demonstrating the answers to these questions no matter what technical question you're answering is one of the keys to excelling at the interview process.

[mostafarezaie]

Never ever lie to your interviewer! That's key.

[vVideos]

I was asked in an interview over 13 years ago what my experience in 'Networking' was on a scale of 1-10... I answered honestly, that I'd rate myself a 2 - that I could set up my own LAN but beyond that I'm not sure, and the interviewer responded with, "Well, if you know what a LAN is that's more than enough.".

Point is, never be afraid to be honest about your knowledge or skill... it will almost always benefit you, even if you don't feel like it will in the moment (especially when you're in a situation where you feel you need to be impressive).

[bearforceone]

I burned out working in Windows, when I finally moved to Linux I was too burnt to even start the new job. Now a year later, and a lot of thinking I'm pretty sure I'm still sticking with Linux but still figuring out which direction to go in (probably devops). Thanks for covering the part of burning out too, it seems to be very common in the IT field. :)

[Mo-ollr]

Awesome series, looking forward to the technical topics video's.

[WorldOfZeroDevelopment]

One important caveat, not all technical interviews will go like this. It really depends on the company you're interviewing for and the interviewer. Some interviewers will "spare" with you and perform some weird devils advocate ritual to make your solution wrong. Others will have found a problem 15 minutes before you arrived and not understand it themselves. Some others will be completely disconnected from the interview and be doing their own thing during this whole process. Sometimes they will ask you questions completely unrelated to your line of work: ex: interviewing for some kubernetes distributed services and get asked about writing mobile apps. Other times you'll find someone who wants you to solve their current work problem for them as some sort of unpaid contractor. You can do everything right and still fail your interview for these or other reasons. Some companies do them MUCH better than others, the variety of skill of interviewers ranges dramatically especially at large companies.

[alvin]

Thanks for the tips! Really appreciate them as a new graduate here

[DejiAdegbite]

Thanks for this. It is really encouraging. I guess I should go back to that job search of mine.

[dreadcorpse]

i am always saying the truth, that i don't have much experience, i think because of that until now i don't have a job, even for unpaid practice work ... all of them they want you already with 7 years experience

[ritual]

+2 if they are a H-O-T-T-I-E though, amirite? 😇
E: In all seriousness, this was a great video. As someone who has some experience in giving interviews, you captured the thought process behind it, really well. Thanks!

[Peckingbird]

Well this is well timed. I have my first tech-industry interview tomorrow.

[hubstrangers]

Kubernetes series, is it done, or would be returning to the mini project?, Thank you for the kube series, but not for this, folks are bless with brain cells (99%), like many things out there, they learn, computers are just another tool set out there...

[leavemealone]

Omg I made all these mistakes and still got hired (but I m a student and it was for an internship)

[bheathrow]

"Don't tell no lies your ass can't cash."

[Sumitso]

Unfortunately, a lot of people like to tell the interviewer what they think you want to hear.

[mikejohns]

I barely know enough to get by and I have no idea how I wound up here. Yeah.

[plookploook]

l'm shifting to devops got my technical interview last week. received the result today. guess what's the result.