How to NOT Fail a Technical Interview

What an amazing video :)

When the first question turns out to be a warmup, and the REAL question is a 4-D dynamic programming problem 🙂🔫

No. The interviewer doesn't actively help you. In fact if you don't answer the question in 120 seconds, he presses a button which releases lions on you.

Here I am an experienced dev at a top company and I got super flustered on my coding interview for a job I applied to. I feel like you do a bunch of studying, get the job, then forget literally everything you studied and have to start from one all over again. No one even uses these sorting algorithms anymore without documentation right there in front of you. It’s 90% architectural understanding 10% algorithms

This is legitimately one of the funniest videos on your channel. I couldn't stop laughing. Very informative too, of course.

We need more collabs between you two. Best 2 YouTubers in tech hands down

I wish interviewers were more like Primeagen. In most interviews I did, the interviewers made clear they didn't want to be there by giving half-assed questions without a clear objective and getting pissed when you ask something. Occasionally, the planets align and you are interviewed by someone who doesn't see you as a rival, but as a fellow developer who is going through the same process they once did. Remember: Interviews can say a lot about the company you are trying to join. Great video as always!

I've been in tech for over 13 years and somehow so far I had only 2 tech interviews, while the rest sent me some tech-test/task to do at my own time. 1 of the interviews was essentially an "ABCD test", so nothing special, but when I was not sure of the answer for whatever reason, I voiced my logic in choosing one over the other and interviewer appreciated it (his words). Got that job, but I turned it out for another one (which is mentioned in next sentence). The other 1 had a proper task that I needed to code, something about counting possible combinations of tossed coins, that you need to flip after initial toss or something like that. I barely remember what I did, but I was talking quite a lot, while coding, explaining everything. I remember that it had 3 conditions which were required to be tested and by the end of the time limit 1 of them was partially failing, but I still got the job. Only to be laid off 9 months later 😅

At 6:09 the first condition is actually going to print out just the index, instead of FizzBuzz.

01:20 - Stop Caring too much 02:56 - Can ask the interviewer for questions as he/she wants you to succeed 03:20 - Think out loud and explain your thought process as you code 03:30 - Say Something (unless its shit so just stfu) 03:47 - Explain what you're doing any why as you code. 04:05 - Ask clarifying Questions / Keep Composure 04:54 - Express your passion for code 05:01 - Avoid Majic 05:29 - Don't be too clever 05:58 - Never Believe The Internet 06:22 - Never Mind, Always Believe the Internet 07:00 - Don't say Blazingly Fast (Use BigO notation to express "How Fast") 07:12 - Study Time Complexity 07:43 - Enjoy your job by centering a div or someshit

I used co pilot during a tech interview. they didn't care as long as I was explaining my intent first. but also we weren't coding leet code type of problems. I was implementing at a much higher level than co pilot could be useful for. They even said they were impressed by it and how it drastically sped up the coding allowing me to focus more on the implementation and architecture of the feature

beginning my job search and interview prep process right now. this video definitely made me feel better! I really appreciate the casual, comedic approach to such a daunting topic :')

After 40 years in IT, I had my first technical interview a month ago. It was a lot simpler than what I’d feared. Hashmaps did come up though which seems mandatory.

I just got laid off from my software job and am going back into the job market. I've kinda been freaking out about it for the last couple days since it's been 4+ years since I've interviewed. This video was timely and had much needed levity and some very solid tips that bear repeating: slow down, talk it out, and study Big O Notation! Love your content, keep it up!

This is extremely accurate. I would really value fireship to do a serious or series of technical interview videos.

Just created a summary for myself about what was mentioned: 1) Break Down the Problem: Start by breaking down the problem and creating a flow diagram or writing pseudocode. This helps manage anxiety and provides a strategy to solve the challenge. 2) Ask Interviewers Questions: While interviewers can't give you answers, they want you to succeed. Ask clarifying questions to ensure you understand the requirements. 3) Take Your Time: Before diving into coding, make sure you fully understand the requirements. Investing time upfront prevents mistakes and the need for corrections later. 4) Think Out Loud: Explain your thought process and decisions as you work through the problem. Interviewers want to understand how you approach problem-solving. If you're not comfortable talking while coding, consider explaining your thinking periodically. 5) Ask for Clarification: If you encounter difficulties during the code challenge, ask the interviewer for help or clarification. Don't let frustration affect your composure. 6) Avoid Language-Specific Tricks: Focus on fundamental computer science principles and operations that work across different programming languages and environments. Avoid relying on language-specific shortcuts or tricks. 7) Study Time/Space Complexity: Understand and analyze the time and space complexity of your code. Explain how efficient your solution is and how it performs in different scenarios.

The one day where I felt I failed as a programmer was when I had an interview and was told it was going to be just a simple talking interview but it turned into a huge high speed technical interview. I didn't prep at all and at one point froze like a deer in headlights. I am not proud of that day.

First Joma dropped a video about tech interviews some days ago, now you, life is clearly preparing me. Thanks.

This is great stuff. Really most technical interviews aren't just about how smart you are, it's about how you ask for help and deal with stressful deadlines.

“I blacked out, is this heaven?” 😂😂😂😂😂