Whiteboard Coding Interviews: A 6 Step Process to Solve Any Problem Check out the full transcript here: www.fullstackacademy.com/blog...
Пікірлер: 205
@jardondiego3 жыл бұрын
1. Repeat: make sure you do understand the problem. 2. Example: get insights by doing examples 3. Approach: come up with your approach(es) to the problem (brute force first) 4. Code: write the code for your chosen approach 5. Testing: pass the testcases 6. Optimize: optimize the complexities (time and space) of your algorithm
@emmanueltorty44023 жыл бұрын
Nice one! You can make it better by adding timestamps to each step.
@luisady89903 жыл бұрын
Thank you, saved me a lot of time!
@jgaurav62 жыл бұрын
One of the things that I found helpful that you missed here is breaking down the problem into multiple parts (possibly smaller functions). This helps to avoid being stuck in trivial implementation details just because your code feels super complex and also helps focusing on one small problem at a time.
@MichaelStephenLau2 жыл бұрын
You really don't have time to brute force and optimize in 20min. Many FAANG companies will tell you to explain your most efficient approach, why, then do it.
@wtfdidijustwatch50532 жыл бұрын
This is exactly what he said in the video. What’s your point?
@samanthagomez1858 Жыл бұрын
I had an interview today and it was my FIRST TIME whiteboarding! I was so nervous and had no clue what to expect so I just wanted to say thank you for making this video because it really helped me get through the interview and I was lucky enough to get an email back to move on to the next stages.
@Terryochristopher Жыл бұрын
Hi, what was your whiteboard question?
@Jeemmai8 ай бұрын
hello, I hope you got the job and was it for an entry level web developer job.I have one soon and i dont have an idea what the question is going to look like
@anikamukherjee70272 жыл бұрын
This deserves more views. I have been working as a manager for some time and was feeling very nervous for a technical interview since it's been a while since I've had to do coding. This gave me very practical advice that I will certainly be using and will take with me forward to any future technical interviews.
@XClaudia303 Жыл бұрын
Great video, these are some of the ideas I had when prepping for interviews. It would be nice if Fullstack Academy would post a mock interview that follows these steps.
@BehPoker3 жыл бұрын
This is probably the best valued programming content I've seen on youtube.
@meowchka3 жыл бұрын
I really appreciate this video! Thank you for taking your time to explain this. I've been in this field for over a decade, and I realize now that when I was an entry level developer I naturally performed at interviews using similar set of steps. Now as I am at a senior level, I am more nervous about white boarding than ever before. I realize that it is because I adopted the classic thought -- "As a senior I need to be able to solve all of these problems easily." I appreciate this video so much as it reminded me that "No I don't have to know all of it. The goal is to show how I think." Thanks!
@yohsahrdcrpirate2 жыл бұрын
Thank you sooooo so much. Made a huge difference in my prep and approach to the interview
@ians474 Жыл бұрын
Very insightful. I can apply this not only to my future interviews, but also to my future coding problems. Thanks man!
@shubha07m11 ай бұрын
WoW! THIS. I needed exactly, If and when I pass a whiteboard interview someday , I will come back here and thank you!
@AlbertoRodriguez-oe6jo2 жыл бұрын
Thanks, you saved me from directly rushing towards the keyboard and start typing code as soon as problem is displayed.
@pablogandhi3744Ай бұрын
This is a great video! Picks up in very simple concepts overlooked often like understanding the questions right and writing down the input/outputs!
@jjrauch44663 жыл бұрын
This is the best video I have watched on this subject. Thank you.
@CabVideoz3 жыл бұрын
This helped me calm down a lot, thanks!
@LorandPalfalvi2 жыл бұрын
I feel like this helped me reduce my technical interview anxiety a bit. Thank you so much! 🙏
@KaneTheWrestler4 жыл бұрын
Very helpful. Please make a sample video with the whiteboard.
@batlin2 жыл бұрын
I've heard that "breadth-first coding" idea described before as "top-down" rather than bottom-up, but breadth-first describes it better. There's an old diagram format from the 1980s called Warnier diagrams which is basically all about this. The conventions of the diagram aren't very important, other than that it makes you describe what happens at the top level in one or two words per action, before moving down to the second level and so on.
@none0n Жыл бұрын
After watching a thousand videos about this topic. This is the best of them all. No disrespect to other creators.
@keemkorn Жыл бұрын
I think their should be ONE more little step in here. That being simplify and break down the problem into smaller parts, then once you have your bearings on that small control size, scale it up to the whole problem at hand. It's not always gonna work, but it's helped me notice patterns I was missing when trying to tackle the problem as a whole.
@harrybellenie95583 жыл бұрын
Great video! Thank you this is incredibly helpful!
@whatscookinginla-foodblog97982 жыл бұрын
Great video, I could relate to a lot of situations mentioned in the talk , I guess I picked up some pointers , Thanks .
@boliang2523 жыл бұрын
Best code interview tips ever!!
@jessicasmith19532 жыл бұрын
This is fantastic advice, thanks for making this!
@chuka231d8 Жыл бұрын
Fantastic! I love that REACTO structure!
@rogerdeutsch58834 жыл бұрын
Fantastic talk. Great points created around a memorable acronym. Especially great points were: 1. Talk your approach out, talk about what your thinking 2. Decompose your solution into high-level functions (don’t start writing imperative code) 3. Break down your approach into high level ideas -- you can often become caught-up on trivial details but this helps you think of the over all solution. Thanks for the great advice.
@Madinko12 Жыл бұрын
I have to say this has been the most helpful video I have watched to prepare myself, and it helped me way more than I thought it would through my past interview. Background: I am a very pathologically anxious person. Trick interview questions with stangers looking over my shoulder and judging me is definitely one of the most terrific situation possible for me to be in. I was still very unbearably freaked out with the interview, almost brain-frozen by anxiety and dark thoughts. But this video really gave me those few steps I could hold to, and it was comforting. I was able to get started, clear-up my thoughts, and tackle the problem with a clear methodology, in a constructed way. I was still very anxious, and it felt like I solved their problem in a "secondary thread", while my main thread was focused on being anxious and frozen. But that secondary thread was definitely following the framework, and I think it was key. Apprently, my secondary thread solved their problem successfully. I'm still a bit bitter that they ask this kind of trick questions during interviews. It's only good at evaluating the level of stress of the interviewee, and how much they have prepared for this very specific kind of interview question, which is pointless and unrelated to the actual job. But regardless, thank you so much, this video was of great help.
@onaspnet4 жыл бұрын
R -> also stands for RELAX
@jolinzhang5605 Жыл бұрын
I am applying for job recently. Thanks for this video. It will be helpful for me!
@DanDascalescu-dandv Жыл бұрын
Great idea to start by writing pseudocode. To expand on that, you can start breaking down the problem by writing out comments for the code sections.
@meetthereqs2 ай бұрын
This is awesome insight! Thank you so much!
@ChristopherCricketWallace2 жыл бұрын
it's a test to see if you're just like them--a test to see if you know the same things they do (and therefore are on their level). Personally, I think that's not always the best way to full a team. It may be good to have people that know different things so your team can do more together.
@JustinSchieck3 жыл бұрын
I have an interview today. Out of everything I've watched to prepare in the last 2 days, this has been the best help yet. I came from computer programming college courses and not computer science and have 4 years of web dev under my belt. I've never done a coding interview as I've worked for a large corp since I left school. I've needed this example.
@davidleal7143 жыл бұрын
how was it?
@elmahfoudmajidi53442 жыл бұрын
well, bro?
@vcalesco2 жыл бұрын
@@davidleal714 i really hate when they don´t respond, what is the problem?
@chilly21712 жыл бұрын
@@vcalesco Those that aced coding interviews like myself (Google intern) knows that this video is useless.
@diffuusio48522 жыл бұрын
@@chilly2171 Useless for you* Also, I have never been asked these questions in tech interview. The last tech interview I did for web dev I had to create a game. It was way easier than memorizing these useless algorithms that you never actually use after graduating. A lot of the education in US seem to be memory based. You know the questions they are going to ask and can therefore be ridiculously well prepared.
@j.y.9 ай бұрын
Wow. Very helpful guide. Thank you very much. It is so hard to find a high quality info in the internet now.
@user-cc8kb2 жыл бұрын
Very helpful advice! Thanks! :)
@hash5102 жыл бұрын
nice, this video values more more than "I'm former FAANG Google Uber super coder .and now " .. Good job, man
@ndz73722 жыл бұрын
Thanks a lot..i feel more comfortable going in now
@ryank.60332 жыл бұрын
This is very calming. I have a job interview in 2 days I worry that I may completely butcher the coding assessment.
@sanshubhkukutla4043Күн бұрын
Beautiful video very helpful advice!
@jamesbertel8793 жыл бұрын
this made me feel a LOT better thank you!
@thetruthsayer83472 жыл бұрын
Are you better at solving coding problems or did it just make you feel better?
@wc3815 Жыл бұрын
That is such a good point, help the interviewer to be comfortable in the interview. That probably helps them to remember you better after the interview. 13:12
@vusalahasanli42003 ай бұрын
Great explanation. Thank you a lot!
@fireinthehole22724 ай бұрын
Amazing video, thank you!
@jaimemedina3351 Жыл бұрын
absolutely great stuff!!
@hertzvador22202 жыл бұрын
Great tips. Thank you
@omercohen93522 жыл бұрын
thanks so much, great insight!
@suneilgoel31448 ай бұрын
damn this is some good advice, thank you dude. appreciate it!
@LiliLala1991 Жыл бұрын
That so easy yet useful! thank you :)
@Woeden Жыл бұрын
Great valuable tips, thank you very much.
@RyanHemlock3 жыл бұрын
Super helpful! Thank you!
@lstellway2 жыл бұрын
This is super helpful - thank you for sharing! One thought: I wonder if it could be helpful for others to remember the acronym as “React To”. How one should react to the interview question.
@jvjacq Жыл бұрын
This was incredibly useful thanks homie
@Basta112 жыл бұрын
In the C Step, I learned to do CT - Test as you Code. You can do a little sanity checks after every few lines. For example, after writing out a loop, or helper function, any conditional statement, math, look for syntax errors, logic errors. It helps a lot instead of doing it in the end in one fell swoop.
@NomadCodemist3 жыл бұрын
this vídeo made me MUCH calmer about my upcoming interview at Amazon. I have some live coding experience that I hope will help me to not freeze and stay a little bit more chill
@amandalaurcind21453 жыл бұрын
good luck with your interview! :)
@tnikoli403 жыл бұрын
How did it go?
@NomadCodemist3 жыл бұрын
@@tnikoli40 didn't even get to the one with actual people hahaha. But I'm cool, I have much to learn
@tnikoli403 жыл бұрын
@@NomadCodemist so only over the phone type interview?
@NomadCodemist3 жыл бұрын
@@tnikoli40 not even that hahaha. I was too slow on the online assessment
@Entropy6710 ай бұрын
Great advice
@abhilashpatel30364 жыл бұрын
impressive. Can we have a demo where u pretend to solve a real coding question with implementation of these steps. Thanks in advance
@AadidevSooknananNXS2 жыл бұрын
Agreed!
@benstheweatherdog Жыл бұрын
Thanks man, you're making me feel way more comfortable for my interview today! In the interview is it ok to tell them/ask them about thinking out loud? Or should I just start doing it without telling them. Obviously won't say I'm using reacto method but asking to just verbalize my thoughts.
@AnonYmous-yu6hv8 ай бұрын
I had many interviewers that sit there completely silent, even though I was trying to talk to them they barely talked and they expected 100% working code without any hints or anything. Obviously these places had bad reviews on glassdoor and those managers or interviewers are most likely incompetent.
@aodiogo2 жыл бұрын
This is great, thanks!
@richlira2 жыл бұрын
Thank you for this great video
@progtom75853 жыл бұрын
Very helpful video, thanks
@ogookafor21372 жыл бұрын
Awesome.Thank you.
@prajuchannel8709 Жыл бұрын
Nice video mate - thanks for this and very useful. :)
@KeyesAnthony2 жыл бұрын
great advice.
@JoeWong814 жыл бұрын
Thanks a lot bro
@shuvenduoffline2 жыл бұрын
Nice....I really appreciate this video!!!!!!!!
@scottnidell62593 жыл бұрын
Nice explanation 👍
@mayleanpatrickamanyire71312 жыл бұрын
This is great I love the content
@jsiddiqui2 жыл бұрын
good example.. everyone should learn and practice foe algorithms to improve your approach and yes alwayz be confidient and dont ahow your interview er you are stuck
@bkywong2 жыл бұрын
Breadth-first coding worked like a charm! I had a coding problem on paper, and the interviewer got the idea of my code very quickly. Got the job in the end.
@Putra-zy7vf Жыл бұрын
Do you have resource breadth first coding i can learn?
@namratavishwaskelkar68532 жыл бұрын
Thanks so much!
@Timjstewart3 жыл бұрын
The breadth-first coding video (linked to the time where Gayle starts talking about it) here: kzbin.info/www/bejne/e5iYXqeadtyWotE
@DiegoOliveiraProf4 жыл бұрын
totally faild my interview with Amazon. My codes didn't pass all the tests, felt horrible at the time. Then realized it is a huge company and many people told me it is very hard to pass!
@sneezygibz64033 жыл бұрын
I'm nervous for my interview tomorrow. Hopefully it goes well
@DiegoOliveiraProf3 жыл бұрын
@@sneezygibz6403 don't worry, I managed to pass in November in the same company. Be calm, practice today so you will be more confident tomorrow. If it is your first time, they usuarlly use sites like testdome.com or hackerank.com; Review search, sort and optimization algorithms. Matrix are common as well. Good luck!
@ericalopez5142 жыл бұрын
They can’t know how you now with a technical interview, the companies are very wrong, the experience is enough
@ramisru12 жыл бұрын
Very helpfull. Thank you!
@cicero86002 жыл бұрын
Thank you for it is very useful for me. ❤️❤️❤️❤️
@bahmannejati52493 жыл бұрын
Very nice explanation
@suzannevogt2018 Жыл бұрын
Great video.
@greyreynyn3 жыл бұрын
add "review" to the end and call it reactor
@investinglearningmachine3951 Жыл бұрын
Wow! You have the book
@sunwado3 жыл бұрын
Excellent
@manhaabdellah347411 ай бұрын
Very helpful
@ohmegatech666 Жыл бұрын
4:58 if anyone else is confused, it's "breadth-first" coding, not "breath-first". Breadth meaning the full width of the problem
@abdouseck48942 жыл бұрын
thank you very much
@valenciawalker6498 Жыл бұрын
Thank you
@mollydeangelis-jimenez32203 жыл бұрын
I have an interview tomorrow and part of it is peer coding of JavaScript. I’m so nervous but this was helpful!
@josueem143 жыл бұрын
how did it go?
@valencefootball97403 жыл бұрын
any update???
@31redorange082 жыл бұрын
Here's the update: She butchered it and is homeless now. Hope she gets back on the right path.
@mollydeangelis-jimenez32202 жыл бұрын
@@31redorange08 I got the job and make 6 figures now 😏
@31redorange082 жыл бұрын
@@mollydeangelis-jimenez3220 Not sure if sarcasm. 🤔
@javierrodriguez4218 Жыл бұрын
This is literally the design recipe from my favourite book "how to design programs".
@donydou1956 Жыл бұрын
very useful tips
@doniaelfouly4142 Жыл бұрын
Thanks
@RyszardRudy Жыл бұрын
Recently I've been doing for the first time a Whiteboard interview. They warned me about it, but I didn't think they ware serious, so I didn't did my research and failed obviously. Honestly, it's bit frustrating, when a person who's haven't looked for a new job for a while has to learn why such interviews exists, how they should behave. Even I consider myself a good programmer/coder, I felt like I was standing naked thinking how bullshit coding is this: I have to waste time writing by hand, I can't edit, I can't move, I can't look up, I can't test... next thing they gonna ask me to build a computer out of rocks like xkcd comics... I had the idea in my head, but I couldn't write in in code just straight off directly, so the most part I was repeating, trying approaches realizing, that this won't work, and start over, more stress... Total nonsense if you don't know to do this interviews....
@brawlgammer4424 Жыл бұрын
Same here, totally bombed it lol HackerRank or LeetCode questions suck the joy out of programming for me. I've solved a few of them since i bombed that interview, and I come to liking them less each time. Completely irrelevant problems, out of touch with reality, playing on an abstract field of BS. This gamification of Software Development makes me sick.
@kamilbircak10273 жыл бұрын
Very interesting
@KeinNiemand Жыл бұрын
these question about algoriims are more about memorisation then about actual problem solving, like how many people could actually solve a lot of these question if they never heard of the algorithm before.
@avi72782 жыл бұрын
Alternative title: Framework for Getting a Job at Which You'll Be Miserable
@gilong13112 жыл бұрын
Wish you guys did an Android developer track, enjoyed the content nonetheless!
@saddamhussain38603 жыл бұрын
Amazing
@Tesmond2562 жыл бұрын
The coding interview should be what would you Google to find out the answer… I joke slightly, but if I encounter a problem I will often Google it to see if anyone has pointed out any solutions. I can then add value to their solution or build my own knowing that it will work better than an alternative.
@kenjimiwa3739 Жыл бұрын
While this is good high-level advice, my problem is not that I don't go through these steps. Rather, it's the "Describe your approaches" step, which is easier said than done for some problems.
@Cty1011 Жыл бұрын
I have a similar view on this. Been developing for a while now, with many languages, over various size projects, and more than a few frameworks... I always find it hard to articulate how I would unravel a problem with all the various solutions I might initially touch upon... some are even intuition or foresight from past lessons learned.... but you don't have time in an interview to even begin to touch upon ... and still they want to see your best within 30 mins... I do better with 4 engineers grilling me for 4 hours in a free for all session... Talking shop really tells you how someone is to work with... not these 45 minute interviews, where you memorize every algorithm under the sun and hope they ask you the easy ones and fake it until you make it... such a forced and fake process, I am getting tired of these interview games...
@gameplayer19802 жыл бұрын
"hazing process" is a good way to put it...
@mohamedfouad64922 жыл бұрын
knuth books in the background ?
@ERICROJO1563 жыл бұрын
pray they give you enough time for all these steps
@eldavimost Жыл бұрын
You mention Christopher's approach at 10:30 in the video, what's that? I tried googling it but seems to be too vague to get anything useful!
@tayyabrehman24082 жыл бұрын
I have two interviews tomorrow and I'm soooooo nervous.