How To Pass Technical Interviews When You Suck At LeetCode

hi everyone, this video provides an actionable framework (5 steps) that you can apply and follow in any technical (leetcode style interview)

the basic idea is that there are a lot of other things interviewers look for besides a perfect, highly optimised solution.

this video will teach you how to leverage other elements such as communication, to obtain a stronger interview performance.

btw i realised that coding/non-coding artifacts don't really make sense in the context i used them.... i think what i meant is elements that are directly related to coding implementation, and elements that aren't.

let me know if you enjoyed this video in the comments below, or any criticism so i can improve for next time :)

music:
Creative Commons — Attribution 3.0 Unported — CC BY 3.0

[andrewhu]

I just realised that coding artifacts and non-coding artifacts don't really make much sense in this context... I think what I meant was elements that are directly related to coding implementation, and elements that aren't. But that's kinda wordy so hopefully you still get the point I was trying to make :)

[mrbandithat]

Perfect video tbh, everyone talks about these tech interviews like the implementations are the easiest things ever... they're not; so this is def super helpful.

[charlesabju]

Wow I'm sorry for the people outside the 14k people who watched this video. This was spectacularly practical and useful, thank you so much!

[dogecl]

I like this coding interview framework. We often don't communicate our process, or rush to solve the question without asking clarifying questions, constraints, etc. It can save a lot of time for the interviewee and the interviewer to follow a step-by-step, structured approach.

[alienfunbug]

I've seen a bunch of these style videos over the last two years... this is definitely one of the best by far!

[annlaosun]

I wish each interview could give 5 mins in the beginning just for the interviewee to think about the problem, brain storm, and gather methods. It is kind of ridiculous to ask interviewees to talk, code, and solve at the same time. Then the whole coding interview becomes if you have seen the question before.

[printemps]

I'm now at least a bit more motivated to do this thanks!

[imaginaryvenus]

Watching this 15 minutes before an interview. I only have a week of experience with leetcode style problems. Expecting total failure 😆 Wish me luck!

[natashanatasha]

hello! i really hope that you see this after 3 years

what should I do on the questions part if the task seems very easy, I'm confident about my complexity answers, the implementation as well and really want to start coding right away? should I still ask questions & clarify use cases? I don't think I'm a perfect coder but the task I got was marked 'Easy' on Leetcode as well

I see that this part is graded separately from the code but won't I seem too dumb if I suddenly try to clarify everything for a simple task?

[realnapster]

What if you have never seen the problem before? And are stuck?

[davidye]

Great video! Could I get the song you used for the outro?