How to NOT Fail a Technical Interview

[@ThePrimeagen]

What an amazing video :)

[@mcp866]

The man himself

[@diegovulcan1]

THE MAN THE MYTH THE LEGEND HIMSELF

[@HacksoreDEV]

FIRST TRY BTW

[@ThePrimeagen]

@@HacksoreDEV yayaya

[@gergelynemeth8244]

Blazingly correct :D

[@magicsweet]

"stop caring" I think that's the most valuable advice I've ever got wtf

[@Sakuta7]

basically "stop giving a fuck and go"

[@user-he4ef9br7z]

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.

[@Md-sl2sy]

Happened to me

[@cruisethomas3244]

me 2​@@Md-sl2sy

[@ChazWalkerWonders]

That's only at Amazon.

[@Submersed24]

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

[@ccampau]

Same here. Seems like every tech interview or skills assessment is just some way for them to score a gotcha question. Of all the development I've done, I have never had to come up with a brand new algorithm doing x, y, z and sometimes a if x and z are not divisible by the square root of 7 and it's a Tuesday all in 15 minutes. It's like asking a building contractor to show you how to make a hammer, nails and a saw from scratch on the spot.

[@MinecraftMasterNo1]

@@ccampau to be fair, making you fail on purpose is a good way to judge how you handle not knowing or not being able to solve something. If every question was like that then it'd be sketchy, but one curveball isn't gonna ruin the interview. If it does, you're better off not working for said company anyway.

[@davidcarlsson1396]

I went into a argument with 3 other devs. It was regarding: "Find the minimal value in this list of 10k elements" They just did list.sort()[0] I wondered if they were idiots (without saying the word idiot). Algorithm-understanding has its place.

[@laughingvampire7555]

it is pretty retarded in my opinion but is the standard of the industry because code interviewers have no clue on how to interview so they jump to the low hanging fruit, "algorithms" and then they justify it with random nonsense like "oh, I wanna know if you can ask questions before coding or you will make the company waste time"

[@marceldiezasch6192]

@@davidcarlsson1396 Sure, you can find the minimum of an unsorted list in O(n) manually, but O(n*log(n)) isn't that terrible for most reasonably sized datasets. It's one of those things where being too lazy/ignorant to see the good approach probably won't have any relevant effects.

[@NeetCode]

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

[@CulesCoding]

The first one was a joke

[@swapnilgohil7280]

Yooooo im preparing for interviews by following your website

[@CreeperFace75]

didnt expect this crossover

[@csmastery1337]

using your site

[@halfbakedproductions7887]

Or you're asked about CS theory at interview, but you're hired and your actual day job is writing Java 5 test cases for the com.megacorp.EnterpriseFrameworks.Factories.Bullshit.BullshitFactoryFactory.BullshitFactory.Collections.SomethingAlreadyImplemented - which was written in 2009 and hasn't been touched since.

[@thedukebelmondo]

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!

[@patterntrader690]

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

[@wtho]

I think he meant best dev KZbinrs. For me there's a clear distinction between tech device reviewers and software developers, but they both are called tech KZbinr/tech Twitter 🤔

[@NithinJune]

what about Ben

[@patterntrader690]

@@NithinJune good point, he’s up there. Although I always felt like his content lacked the depth that Fireship and Primeagen have

[@ES-cf4ph]

And funny ones, too

[@tjgdddfcn]

Mental outlaw pretty good too

[@berhell.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.

[@i_am_called_glitchy]

🤓

[@rudolfkorcsmaros]

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

[@johningles1098]

Ok great, I thought I was an idiot for a min there.

[@rondamon4408]

I saw the same

[@dmitrykonstantinov7723]

Hm, mistake or byte? 🤔

[@ensar8177]

It is probably a Fireship sarcasm or maybe he is a bad programmer.

[@RavenGhostwisperer]

Yeah, just wanted to comment on this as well :D

[@DerkerBluer]

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

[@ZuriPOL]

imo java for the haters was funnier

[@vaisakh_km]

@@ZuriPOL ofcourse🤣

[@ZalexMusic]

7:49 😂 😂 😂

[@MRWTrades]

im in hysterics

[@Soulxstar]

Weird to see you here i knew you were a programmer but didn't know you were suscribe too

[@waffle8364]

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

[@crownie9652]

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

[@Dyanosis]

Explain what you're doing as you code* Avoid Magic* Enjoy your job* How did you edit this post and you still have spelling mistakes?

[@crownie9652]

I just don't understand why people always have something to complain about. It's just a freaking typo but you can still read it.

[@YannMetalhead]

Thanks.

[@gianclgar]

am i job?

[@omarhamdy2166]

@@gianclgar 😂😂😂

[@timothyhuynh6592]

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 :')

[@fiskebent]

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.

[@monsterhunter445]

Depends on the company and the role. It can be easy to medium to very hard depends on whether the company wants junior developers or someone working on something very algorithmic. Personally I have gotten various degrees of difficulty. I would say Amazon was the hardest so far from the FAANG. Microsoft was easy but I lacked communication skills.

[@samuelbaird4983]

Hashmaps are also the only advanced data structure I've actually used in a real-world codebase as well

[@MilanDrazic]

What is hashmaps? is it spread on bread

[@MRWTrades]

@@MilanDrazic hash you smoke but on js toast

[@imad644]

How long did it take you to get “40 years” of experience? 🙃

[@autisticscooterdriver]

I loved that time I went on a job interview series with 5 rounds, being upfront beforehand that I didn't know C++ particularly well, and they assured me that it was not an issue, and that I could code in any language. I assured them I would get up to speed quickly if I got the job. I go through all the motions, do pretty alright in all of them, using Java where necessary. Then comes an e-mail, oh, by the way, we'd like you to have another final round with two of our more senior developers, and it will be in C++. Medium complexity task coupled with unfamiliar syntax made it a complete mess for me. I simply got stuck and had no way of completing the task.

[@byrondumont-eve]

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!

[@joseyo93]

I'm sorry to hear that man. I think you'll be just fine. Maybe big tech is slowing down a little, but there are several other companies still hiring like crazy right now.

[@byrondumont-eve]

@@joseyo93 I've got opportunities for what I do, it's just fighting the impostor syndrome long enough to succeed in the interview. Thanks for the vote of confidence though 👍

[@blackkitty_42]

hey man, i know interviews are scary, but honestly as long as you be confident (even if you have to fake it) its gonna be okay! good luck to you dude, i believe in you.

[@Dyanosis]

Big O Notation, I've found, is hardly ever actually discussed/cared about in actuality. You'll talk about "is this efficient enough", but you're not going to be saying "It's O(n*log(n)+1) and we need to make it O(n)". So don't stress it.

[@nieczerwony]

Man why are you freaking out? If you have been working constantly for last 4 years as dev, then you will be set for interviews. Unless you go for like principal/senior role and you have to do like design patterns etc. Technical stuff you use all the time, but when it comes to design, algorithms and data structures these are not used on daily basis.

[@howardleen4182]

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

[@edwardrhodes1518]

Fusion of programming experience, logic deduction, js capabilities, video production skills, and story-telling potencies - leading to a high-quality, edifying, gratifying, and satisfying experience. Thanks much.

[@edwardrhodes1518]

@ಶ್ರೇಯಸ್ The truth told - just.

[@Kayzewolf]

Every tech interview I've had, haha. The performance anxiety is real, where I overthink the issue and despite talking out loud, I start to forget what math is and go into "maybe if I keep clarifying and talking about the issue and stuff that could go wrong, that will be enough"... But sometimes I get lucky and my brain reboots fast enough to actually get the problem worked on. Some people will be naturally (or prepared) more comfortable or at least comfortable enough to be good at it. This video helped me feel it's not just me at least, though iffiness of being able to pick myself back up might be a just me issue.

[@simbiat]

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 😅

[@IffyEdem]

Word

[@klirmio21]

@simbiat so we have to practice talking out loud?

[@sherbertgerbert9719]

why were you laid off?

[@simbiat]

@@CAPS_AMERICA nope. never used it even once. nothing similar even. and I did not have access to DB (only though some UI features, that essentially returned JSON).

[@sammyjones8279]

Oof!! Almost the exact same happened to me. Big scary tech corp hired me and said they'd train me since I was a little green... Then sat me in a corner for 9 months until my manager got sick of it and dropped me like the hot garbage I was.

[@aCitizenJOSerased]

Whoa, that's probably your best video! immense quality on all aspects.

[@RemnantCult]

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.

[@simpan197]

That's not your fault frankly.

[@hakametal]

We've all been there. I think we have to go through that pain to become better developers. Fail upwards.

[@Aschentei]

i'm only speaking anecdotally but my tip is to never trust when they say "simple talking". In one of my interviews I was asked to talk about my favorite classes, ended up baiting me into explaining super technical terms and I almost choked

[@attackemartin]

I still feel the emotional damage from my failed interview 🙈 usually I'm very confident in what I do and what I know and being capable of. But that day, after the interview, I considered switching jobs altogether

[@hakametal]

@@attackemartin That feeling is your ego getting destroyed. We all have the same reaction, no human enjoys being rejected especially like that. I remember my first interview, and I legit got FizzBuzz like in the video. It was for a junior frontend role and I was like, "what the fuck is this shit". I had no idea what modulo was either. Got completely obliterated and was depressed for a good few days. Joined CodeWars a few days later and made sure it wouldn't happen again (bombing so hard I mean). That feeling you felt is your ego, you HAVE to learn how to deal with it when things go bad. Keep moving forward and be consistent.

[@lord_nikon_010]

The sudden change from answering about Big O notation just to able to change button's colors got me. Unfortunetly, so accurate!

[@mericet39]

Last time I was in a live coding interview, I padded out the time by writing unit tests. You can never go wrong with them. Writing them gave me the time to work out what to do next, as well as earning kudos from the interviewer. I got the job. I turned it down.

[@thisismyplaylist]

were you padding out an unit test ? how was it ?

[@bishalkar5614]

Give me a job bro. I need it

[@pairofrooks]

That's low key brilliant 😂

[@backgroundnoiselistener3599]

I have given more than a few interviews and this is how it exactly goes.In my previous job the interviewer asked a question whose solution was a heatmap algorithm but I ended up working on angular there. No algo, no nothing.

[@Dyanosis]

Classic example of interview not actually assessing your ability to do the job they need you for. I hate those interviews.

[@Ivcota]

@@Dyanosis I'm starting a new job and I'm so happy they tested me on React and graphql lol

[@ohmegatech666]

8:07 This literally just happened to me. Got a job with an Apple contractor, and 10 minutes *after* finishing all of the onboarding, I got an email saying they rescinded the offer... again, after I already was legally their employee

[@joseville]

Did you at least get a severance package?

[@Mutual_Information]

I give a lot of machine learning interviews.. the one piece of advise I can give: Don’t fake it. It’s very hard to trick an organization into thinking you know a subject when you actually don’t. If you want to pass ML interviews, study ML frequently and consistently, not to pass interviews, but to grow a valuable skillset. Companies will then seek you out.

[@ouo5634]

One question, they don't ask questions like in thw video in ML interviews right? What kind of questions do they ask?

[@Mutual_Information]

@@ouo5634 I can’t say what we do at Lyft, but broadly, companies test statistics and probability theory first. So the book “All of Statistics” is a great place to start. Outside of that.. there are a million probability puzzles out there. Things concerning decks of cards, flipping coins, spinning a roulette wheel, etc..

[@doc8527]

that's fine and reasonable for most devs, the core problem is always leetcode, which you can "fake" it somehow. Though tons of ppl I had known said you just need to understand the pattern, but 100% of them are just spending tons of time to hard memorize all the patterns and solve 200+ lc questions, and hope they will get the same types of questions during the interview. In fact, this trick is 100% working so far whether I like it or not.. You could say its a fair game, but the truth is that it will cause the bar higher and higher as more ppl jumped into this game. It's just like there is always someone accepting a lower salary than you in order to get the job. It's bit of cliché I guess.

[@InvictusM0n]

So for ML interviews Statistics and Probability seems like a must and apart from ML algorithms how much do you guys (as an ML interviewer) value DSA, like a full grind or is it not that valuable for ML?

[@doc8527]

there is a huge advantage for employer side because it doesn't require high abilities from the interviewer to setup the meeting. The interviewer just need to build thing upon that leetcode question. When it comes into the type of interviews you mentioned, it actually required the asker has a lot of insights from many aspects. There are so many times the interviewers(they are software engineers) have no idea what they are talking about, randomly use some technical terms, don't know how to continue the talk because they are just more junior than you when the topic is out of their boundary.

[@0ne0fakind]

lil Bro in thumbnail really was in a tough situation😂

[@salsamancer]

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.

[@gholin]

I'm really glad this video was made. I was recently laid off and I am now in the process of panicking that I have to do these tech interviews. I have only had to do these one other time (I tend to last around 4-7 years at a tech company), and I was miserable. I'm also a Sr. SDET, and these feel so insane to me. Give me a puzzle to solve, anything but an algorithm to code that I don't know! Having you stare at me while I code kills me anyway. Heck, someone watching while I code at work always made me goof up. Anyway, thank you for showing me even hardened engineers hate these things, and making me feel like I might be able to tackle them if I think of them simply and visually!

[@justanotherhotguy]

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

[@Illmare]

Stay strong brother we're in this together

[@justanotherhotguy]

@@Illmare Thanks, kind stranger! Good luck in all future and life!

[@classicwannabe7710]

@@justanotherhotguy You're welcome. Remember to use hashmap BTW

[@bobDotJS]

God damn, I love meditating

[@talesfromspace]

@@bobDotJS USE A HASHMAP!!

[@l.halawani]

Man you have such a good sense of humor! And you do the internet memes implementation like boss! One of the best out there.

[@phila4574]

I think at 6:49 it should just be: out = "Bazz" for the last modulo as otherwise you will get FizzBazz or BuzzBazz combinations as well :)

[@MortyMortyMorty]

I feel like a programming god for thinking about doing it modulo way and not the first way you solved it :D

[@smikkelbeer7890]

I've barely ever used modulo but I remember it solely because of this problem lmao

[@h2o848]

fr i bet modulo is used more than 70% of the time in some (x % n == 0) than in any other use case

[@muhammadumarwaseem]

Man you're the best, well edited videos, no useless stuff, subtle amount of comedy. 🔥

[@MeshTheSnake]

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

[@aaaaanh]

the collab I never knew I needed

[@anch072]

this happened blaaazingly fast! Great to see the two of my favorite creators together!

[@dragonicplayz9069]

fizzbuzz is like introduction to programming 101 question. I actually liked the last concatenation code never thought I could approach this code this way.

[@strajkz]

Whenever I see these videos I feel like a massive imposter, landed a job as a developer for an Industrial Engineering system like WinCC. The interview had no coding or technical questions at all, just asked for my experience and what I studied, got the job, been employed at the same company for 10 years and they're massively satisfied with me, pays incredibly well and have been raised several times, clients love me as well so I have a massive network now. These kinds of videos make me feel like that if once this company shuts down, I'm not going to get another job in the same field.

[@cybebe6679]

I love your videos man I promise when I get hired ill donate my 1st salary to you for you to create more videos like this I Love you man!

[@jonsantos6056]

I feel better cos I just did fizzbuzz. I feel good cos you used an easy example and showed even experts may sometimes initially stumble on easy qns.

[@jgod722]

Thanks Jeff for the amazing tips! Your content is always dead on. Keep 'em coming!

[@liondevelops]

The Nickelback part at 7:15 absolutely killed me mate. Too funny! I love this channel so much as a beginner programmer.

[@Code_Machine]

Seeing as I just landed my first proper interview and now have to do a technical interview in a few days, this could not have come at a better time for me

[@cineverseproductions]

Banger, keep the quality content going. 👊🏻

[@grimm_gen]

I passed a technical interview 2 weeks ago! My first time doing a whiteboard interview also, and I got an offer!😁

[@udemyaccount4082]

IT'S TAKEN ME ABOUT 1.5 YEARS OF WATCHING FIRESHIP VIDEOS TO REALLY VALUE THEM. THEY ARE A FUNNY WAY OF PRESENTING REALLY COMPLICATED COMPUTER SCIENCE THINGS AND I AM VERY FAVOR OF THAT. THANK YOU FIRESHIP YOU HELP MY LIFE SOOOOOOOO MUCH THANK YOU FOR BELIEVING IN BUDDHA

[@xhenryx14]

I had my final interviews with Amazon last Friday, definitely felt like the video. I'm going to talk with the recruiter today to get an update on that 😱

[@halfbakedproductions7887]

I've known people who interviewed with Amazon for various technical roles. As much as *FIVE HOURS* cumulative interview time. Fuck that. I've been through the hiring process at other high profile megacorps and it was about 60-90 minutes interviewing total before I got an offer. And most of the questions I was asked were sensible ones regarding the technologies and the concepts, not banal riddles like "Jenny has four teacups and her grandfather served in Vietnam. Calculate how many cats there are in Albuquerque".

[@xhenryx14]

Yes, it was a total of five hours just interviewing for me, much more studying for that and they said no today 😕

[@stormy1514]

@@xhenryx14 let us know

[@kalesantosh]

@@xhenryx14 There is always next try!

[@xhenryx14]

@@kalesantosh true, now the period to reapply at Amazon is after 2 years

[@jimihenrik11]

I didn't study CS, and in germany that makes most interviewers very sceptical. No matter that I have worked as a full time dev for almost 5 years and that I have a bachelors and masters degree in math. So the coding interview is usually my oportunity to shine. One of the things I like to to is strict TDD. While I type the test cases I talk about the requirements and ask further questions if needed.

[@ashrasmun1]

I totally adore how informative and hilarious at the same time both of you are. Thank you!

[@5inque_wu]

Finally! A FizzBuzz question I studied last night, I can finally understand your video!

[@azrafal]

It's wonderful to see you two together. Big fan of both ♥️

[@Gumitto]

The only real coding interview mockup on youtube.

[@Sheharyar69420]

for i in range(1, 100): print(i) if i % 3 and i % 5 == 0: print("Fizz Buzz") elif i % 5 == 0: print("Buzz") elif i % 3 == 0: print("Fizz")

[@web3js]

It’s only getting better. I wouldn’t even know all the good stuff that exists in js if I didn’t watch your channel

[@benoitchouinard4240]

Almost everytime I've done an interview I'm nervous going in but then you start talking with the employer and you see that they are pretty chill (all of the ones i've met anyways) and almost all that nervousness goes away.

[@CimolOk-nz5yj]

🎯 Key Takeaways for quick navigation: 00:00 *🎭 Introduction to Technical Interviews* - The stress and stakes involved in technical interviews for software engineers, - The process begins with overcoming tutorial challenges and impressing resume-reading algorithms, - The importance of playing the "interview game" despite its perceived flaws. 00:41 *🚀 Preparing for the Interview* - Dedication to learning and sacrificing personal time to prepare for software engineering interviews, - The candidate's confidence bolstered by practice and online courses. 01:10 *😰 The FizzBuzz Question Panic* - Initial panic and self-doubt when faced with the FizzBuzz problem, - The realization of overthinking the problem and the shift towards a more analytical approach to breaking down the problem. 02:07 *🧠 Analyzing and Solving the Problem* - Approaching problem-solving by discussing and breaking down the problem before coding, - Utilizing pseudocode and a step-by-step logic to tackle coding problems effectively. 03:03 *🛠️ Coding the Solution* - Implementing the FizzBuzz solution with careful consideration and verbalizing the thought process, - Importance of explaining decisions and understanding requirements over rushing to write code. 03:58 *🗣️ Communication is Key* - The significance of verbalizing thoughts and problem-solving strategies during the interview, - Encouragement to ask questions when stuck to maintain composure and show engagement. 04:53 *🔧 Refining the Code* - Optimization and clarification of the initial solution through iterative feedback, - Introduction of more efficient coding practices and techniques in response to interviewer's prompts. 06:30 *📈 Scalability and Performance* - Addressing additional complexities and conditions by refining the solution for scalability, - Discussion on the performance and efficiency of the solution, with an acknowledgment of its time complexity. 07:43 *🏁 The Unexpected Conclusion* - The emotional rollercoaster from receiving a job offer to having it rescinded due to a hiring freeze, - A humorous yet insightful look into the unpredictability and challenges of technical interviews. Made with HARPA AI

[@vintprox]

1:44 It's a peak comedy when you witness Fireship depicting the anxiety from interview memories with memes and his usually calm voice getting cracked XDDD

[@rauldavidsaavedramedina835]

This video is so so good men two of my favorite KZbinrs in just one video blazingly amazing! 🔥

[@MyPing0]

Now all we need is a video of how to actually GET to the technical interview and things will be golden!

[@abudhabi9850]

Outdone yourself again. Happy for every new video you make!

[@banditosdoritos]

My two favorite KZbin programmers in one single video!? Christmas came early this yeah, damn.

[@KingGrio]

I'm not a very smart maths guy but the video did spark some thinking for me: Every number ending in 5 is divisible by 5, and numbers not ending in 5 aren't divisible by 5. So just check if the last digit is 5 and it's divisible by 5. In C or C++ you could check that the last 3 bits of the int are 1 0 and 1. For divisibility by 3: the number is divisible by 3 if and only if the sum of its digits is divisible by 3. You could repeatedly add the digits of your number and subsequent numbers from your algorithm until you shrink it to 3, 6, 9, or some single digit number and decide if it is divisible by 3. I think this scales better because adding up the digits of your number shrinks the number rather fast, because you are dropping power of 10 coefficients and also because summing is computationally inexpensive. I'd have to check though in theory how much more effective that is compared to using the modulo operator. Of course this is a DIY optimization thing and unless you are being hired to write maths algorithms probably you shouldn't worry about this or try to show off. My guess is that 1) nowadays there are math libs that check complicated stuff efficiently for you and you should just use those unless you can compete with maths nerds and 2) I've seen instances where a mathematically more efficient algorithm is slower that some other implementation because you are running the code on a specific CPU or DSP where its registers are setup in such a way that the manufacturer's implementation of some maths will win out against some theoretically better maths algo.

[@mimonbaraka5454]

Numbers not ending in 5 are not divisible by 5? Bruh

[@sage_gamers]

Please make video on your journey as a developer and the ups-downs you faced. btw love watching your video and it inspires a lot 👍🏻

[@ns8928]

The interviewer wants you to succeed. Man that gives me confidence.

[@rashmiranjansahu8271]

Some of those tips are valid for every interview out there not just tech. So good that I wrote them down.

[@attackemartin]

Had such an interview a month ago and it crushed my confidence through the ground. I'm a frontend dev since over 10 years, but this interview had left me feeling I just started to know what HTML is, although I know my stuff. I don't think these interviews are the right thing for those jobs. Let people program a thing in x days and code review the result together

[@bhargavpandya9189]

This was so funny! And always wonderful to see Prime!

[@rishabhmittal1240]

Great video! Quick question: At 6:06, shouldn't the first if statement be logging "FizzBuzz" instead of the number i?

[@daymenpollet4202]

yea, and also, he should write && !== 5 after the mod3 aswell as write && !== 3 after mod 5 in the 2 first else if statements, otherwise it just be writing fizzbuzz fizz buzz when a number is dividable by 5 and 3

[@joseville]

​@@daymenpollet4202the extra != checks are not necessary because he's using "else if", not "if".

[@womz8203]

@@daymenpollet4202 That's not correct/necessary. Technically it won't hurt, but it's redundant. The else-if will only be entered if the number isn't divisible by 3 AND 5. You don't have to check again whether the number is not divisible as the combination case has already been checked against. If both aren't divisible and you enter an else-if to check whether the number is divisible by 3 for example then it's already known at that point that the number can't also be divisible by 5 otherwise the initial if statement would have been true. Also as soon as one if/else-if evaluates to true no other else-if or else will be evaluated, so again no need to check for the inverse. This is easily verifiable. Just run it and see.

[@abdullahmujeeb3649]

I am in the process of technical interviews since the last few months, bombing most of the ones I went and took with little to no guidance from the internet. I swear man, this is the best funniest video on technical interviews I have seen for a while now xD

The tricky that always works for me is to think I'm solving a problem with friends. The pressure really goes away, specially if you find the space to throw some bad jokes and laughs.

[@katjafed]

It's a great tip because I used it on my first screening interview and it works! Tomorrow I have a tech interview and hopefully it helps me again.

[@ewilso22]

@@katjafed How'd it go?

[@katjafed]

@@ewilso22 It was OK but they chose another candidate

[@anumcodes]

What a wonderful breakdown! The end had me laughing 😂

[@omarmahmood4209]

A video on ATS-friendly resumes would be a great addition!

[@DankMemes-xq2xm]

At this point I just looked up the standard AST friendly template and copied it completely. RIP to the work I spent making a pretty resume last year

[@mozartmaia6333]

The crossover we didnt know we needed, until now. Blazingly amazing!

[@WilbertVerayin]

7:20 I bursted on "look at this graph" Hahahaa

[@josearmas1511]

as someone who is changing careers from social sciences to software developer I can't express on how many levels this video made me feel better

[@KarlDag]

How has career changed gone? I’m in healthcare but studying for computer science right now… scary stuff

[@arsnakehert]

I started streaming myself coding on Twitch, and I think that helps me program while I feel like I'm being judged, even when there's nobody watching lol It also helps me talk about what I'm doing, it's like I'm rubber duck debugging without a duck, but with real random people...who may not even be there, but I like to pretend that the "1 viewer" that shows up in my phone isn't really myself

[@stan_de]

really great ending. You earned this like honestly :) Thank you!

[@user-cd6vy2jg6f]

What you can ALSO do is - become an interviewer. No one wants to do them because they’re tedious, not coding, and come with a lot of paperwork afterwards, but that’s why it stays broken. There aren’t many good interviewers with a desire to fix the system. I’ve made it a point to do as many as I can at my company and ask better questions. I.e. (develop a program that can update a file on N different hosts) instead of (literally any leetcode question)

[@vibovitold]

I can confirm that some experience on the other side of the table is very eye-opening. I've noticed so many things I used to do wrong in such interviews. I did like conducting those interviews too, so "noone wants to do them" is a bit of an exaggeration.

[@TH3BADRO]

Your videos are the best. I love how you mix fun and memes all while helping us learn new things.👏🏽

[@WolfPhoenix0]

I didn't think you'd include the hiring freeze part at the end. Fireship always makes the funniest tech videos! The lesson here is to practice your tech interview skills only AFTER you've confirmed that the company isn't in a hiring freeze. 😂

[@the_crypter]

Yea, I gave and cleared the Amazon Assessment a few months ago, only to wait 3 months for an interview, only to find out they might have froze hiring's for this year. 🤡 Always Check people.

[@_ash64]

This is hilarious! And the production value is next level!

[@pesterenan]

Wow, I legit thought about the modulo operator first instead of the type conversion trick! That means I would be just a LITTLE less anxious in the interview. Nice!

[@creamy6680]

same here!! feeling a little less like an impostor lol !

[@dadqqader]

If you get clever right away. They might think you're smart enough for the bigger step. And eventually will put you in a corner.

[@VinnyBarone]

I wish I watched this before my interview today. Welp..now i'm prepped for the next one ;) Great video!

[@bob_mikhail]

Thinking on the fly, not using Google or chatgpt, jumping straight to solution/implementation, just what are those live code interviews checking in my skills? This is exactly the opposite of how I work daily

[@MEZOMEZO2011]

Tbf, you can ask the interviewer. If he doesn't answer nor give hints, just relax as that is a place you probably don't want to be in.

[@kamil8263]

As mentioned in the video, sometimes you just have to play the game

[@casualrich-lifeiseasy4921]

Fireship, you are literally my coding Dad!

[@chriskapoutselis7281]

Totally accurate. I will never forget my first interview where I was asked If I know how a keyboard works and If I can add 2 numbers in C. Beautiful video.

[@pemifo260]

How many years it was ago?

[@chriskapoutselis7281]

@@pemifo260 3 years ago

[@danyalimran2591]

I got a technical tomorrow. Watching this eased my nerves. 10/10 video

[@GbpsGbps-vn3jy]

I'm always thrilled to say that all natural numbers between 1 and 100 are divisible by 3 and 5 because no-one at the interview said that we must exclude fractional and decimal numbers :D

[@NeptuneFan12]

Natural numbers do not include fractions or decimals. Rational or real numbers do.

[@GbpsGbps-vn3jy]

@@NeptuneFan12 Whole numbers. If we're going to call numbers 'natural' then always remember that the nature has fractions in it

[@vibovitold]

​​@@GbpsGbps-vn3jythey've been called "natural" in mathematics for a long time now. they're not called "natural" because they describe quantities that occur in nature, but because they are used for "naturally" counting (or ordering) discrete objects. whole numbers can be negative, natural numbers - no (because -1 is not a number that would come up in simple counting)

[@theena]

This is the crossover we all needed.

[@raymond-andrade]

Now if I ever feel nervous during an interview, I will just remember Nickelback's wise words @ 7:15 to "Look at this GRAPH", and never forget Big-O

[@lazyman2451]

They gives me 30 minutes on a coding interview at meta where I had to solve the question and then optimize it to get the fastest response time. About 4 questions while actually explaining each step I’ve taken.

[@DavidM_]

6:48 i am not sure if this is correct solution. Based on the question and logic used in previous solutions for 21 it should print out 'Bazz' but we get 'FizzBazz' here.

[@LaynaStambaugh]

The stop caring part is actually how I got my driver's license. I thought I failed the maneuvering bit, so I just didn't care anymore when we went through the normal driving part. Turns out I did just well enough to pass the test!!

[@gldplatinium]

I have a question, is it me, or when you do the condition, both being correct (number divisible by 3 and 5) shouldn't be console.log('Fizzbuzz');?

[@RuiSilva450]

Yep, that is wrong and it's odd that he kept it like this

[@nikfp]

"Look at this Graaaph" - Literally almost choked on my lunch. Much laughter at the same time. Thanks for that!

[@samyogdhital]

5:30 C developer with 50 years of experience 😄😄😂😂

[@Nieosoba]

oh man, this is the best programming channel, I have a job in IT but I also have an interview for 2x better job next week. I am sure they going to ask me about some SQL optimization shit, I know it.... :D

[@geekwithabs]

The thumbnail is brilliant 😂

[@VANSHPOONIAJEE]

🤖