Why Good Programmers FAIL Coding Interviews

1. How to crack coding interviews?
2. How to prepare for coding interviews?
3. How to learn Data Structures and Algorithms?
4. How to use Leetcode effectively?
5. How to ace Software Engineer interviews?
I will answer all these questions in this video.
► Credits:
1. Seven habits of highly effective people (Circle of Control): www.amazon.com...
► For more content like this, subscribe to our channel: / powercouple26
► Follow us on Linkedin:
/ gabag26
/ sarrabounouh
► Let's be FRIENDS! / power_couple26
► For business inquiries, reach us on: [e-mail]
#codinginterview #datastructures #datastructuresandalgorithms #leetcode #dsa
DISCLAIMER: All opinions shared on this channel are our own and don't express views or opinions of our employers. We only use our experiences and public knowledge to make our content. NO CONFIDENTIAL INFORMATION of our employers is used or shared on this channel. This is not a Professional Coaching channel, it only highlights the public resources that have worked for our careers.

[@SimonZimmermann82]

For me coding is an art and very creative... Coding under pressure during an interview is nonsense

[@fancyAlex1993]

Exactly.

[@HeroicKhalid]

I just finished my coding test and felt unrespected for the given questions to the point I just left

[@sahanlakshitha8453]

Just realized that today 🤥. Successfully messed up 50% of the interview.

[@jedi4049]

Bombed the USAA one it was 30 min and 3 questions. If I had time to work as I normally do I could have done it. The stipulation of not being able to switch off the window (theyd give 2 warnings and 3rd time exit you from the exam) and having a webcam (which they didnt actually use during the test) didnt seem like a real world situation. I get it they need to test my expertise but it was for an entry level role. I know how to code but never did it under those circumstances. At what point in a job will there be a 30 min timer?

[@kritimandal2285]

I can't figure logic at the pressure

[@Afterlord2]

This is really good advice. It's a shame that companies still do coding interviews like this though. For some jobs that are very technical it can make sense, but for most jobs you're primarily thinking at a high level. Solving these kinds of puzzles is less than useless and something I've never done, even while working on extremely technical finance modeling code. Asking them in an interview is doubly useless since it really just wastes everyone's time and tells you very little about a person's ability to program other than that they've spent a lot of time practicing for a coding interview.

[@Pvizzy]

Couldn’t agree more. I’ve been coding for 13 years. Technical interviewing and the day to day job of programming are disjointed skill sets.

[@EskoLuontola]

I consider such an interview (i.e. it requires knowing an algorithm that took someone years to invent) to be a red flag and that the company should be avoided. I would just say that I haven't encountered the need to solve such a problem in my 20+ years of career, but I could quickly find the problem and known solutions to it with google and code it up based on some research paper. The job interview reflects that what kind of people are at the company (i.e. they've passed the interview), so an interview requiring highly specific knowledge will pass only people who are very similar to the people who already work there, producing a diversity deficiency. In one coding interview related youtube video, they mentioned Floyd's Tortoise and Hare algorithm. Once you know the algorithm, coding it is the easy part. I was more interested in *why* the algorithm works. Most internet pages only described the algorithm, and it took me quite some time to find a proof of the algorithm.

[@ProLeopardx1]

So true. I'm a junior engineer but I had a unique opportunity to interview potential interns. I gave them a lot of conceptual questions, and gave them a design question to see how their brains worked and how they thought about problems. They all really liked that format, and I loved it since it was an actual problem they would have to solve if they were hired. I could so quickly tell their competency, far more than if they solved some random puzzle that I wouldn't care about.

[@dra6o0n]

They would do interviews like this, then want to hire a skilled programmer who doesn't mind the wage of a basic programmer, so they can cut down on the cost. "Seeking professional, uses Junior paygrade"

[@gingeral253]

@@EskoLuontola can you link the proof of the algorithm?

[@Gazer-x5s]

Programming is always about trials and errors, there is no way when the first time you write the code is completely fine and perfect.

[@sahilandsarra]

You’re missing the point.

[@archirnobenz]

He did mention that it is perfectly fine to take longer time and attempts when you are a beginner. But when preparing for an interview, clearly you want to be as strict as possible.

[@AlFasGD]

It has happened to me, and it happens rarely to very few people, but it's not impossible. That being said, the focus is that you should be able to intuitively approach the problem at very high success rate, with very few bugs and issues at the first trial.

[@vitalyl1327]

Tell this to Donald Knuth, famous for "“Beware of bugs in the above code; I have only proved it correct, not tried it.”

[@mixshots1801]

@@sahilandsarra yeah he may not understand what you are saying properly

[@siddharthchauhan1129]

I am an interview engineer and i can say each and every point stated in this video is absolutely valid. Few things I would also like to see is communication while coding from the candidates side. It can happen sometimes that the language chosen by the candidate is not known by the interviewer. This could create some issues if the candidate couldn't complete the solution on time .. because the interviewer know how good or bad the code is in general. But communicating that what the candidate is doing and what they want to achieve is always a good plan

[@IgweEmmanuel-bd5rn]

This is a very good confirmation. Thanks for sharing from your point too.

[@emilyau8023]

The interviews don't even reflect what people will be doing for the actual job

[@sharkysharkerson]

I've been doing software development for a while now, right at the cutting edge for most of it. I'm not a fan of coding interviews to this day. Its really not reflective of the actual work. I have to understand and implement and create algorithms all the time. When there is something I don't know, I can easily learn it. When there is something nobody knows, I can leverage previous experience to synthesize something new. In most cases, coding interviews remind me of college exams. Which in a way is actually good for newbies trying to break into the industry because it builds on experiences you already have. After one has spent so many years actually working, this style of interview doesn't make as much sense. Developing software isn't like taking a test at all, so that part of your brain that you once honed to dominate the exams starts to get rusty as you're spending all your time doing things that matter. Sure, you have to know algorithms, and what to use when ... you have to know how to read code and understand what its trying to do, look for optimizations, refine, debug, simplify, etc ... but that doesn't happen in one shot and it doesn't happen under duress. It only tests one's ability to make the right choices regarding what they want to keep in their brain cache, and does nothing to assess one's ability to learn or create or understand ... all tasks that happen when relaxed. So take heart that its generally kinda difficult for anyone, regardless of level. Because I'm not a fan of interviews like this, I try to avoid giving others interviews like this. But am still refining the right approach.

[@janisir4529]

Coding interview: Spit out algorithms that data scientists spent months or years on to demonstrate your "way of thinking" Actual job: Move a button 4 pixels to the left on a website

[@BW022]

The purpose of coding interviews is not to determine if the person can do the kind of work you do, but to test that they haven't been lying on their resume. Someone says the know HTML and JavaScript, you ask them to write a webpage with some JavaScript which say moves and item from one list to the next. Most times coding interviews aren't designed for real world, but as tests with solutions which are easy to test. You'd be amazed how many people lie or exaggerate their knowledge.

[@ilyasofficial1617]

@@BW022 to prove candidate's competence, they could just give them simple project or provide personal portofolio

[@vstev3472]

@@BW022 yea but there's still many companies that go "Oh so you know HTML and Javascript? Okay then write me a binary search tree algorithm to prove that you can make a simple CRUD website"

[@BW022]

@@vstev3472 Yes. So? People make bad coding interviews (not to mention interview questions, job ads, etc.) all the time. It actually isn't easy to come up with a good coding interview. You have to test enough knowledge that someone can't fake their way past it, yet it needs to be easily evaluated. You have lots of issues with setup, instructions, conveying the purpose of the task, monitoring, whether to make it 'open book' (which is far more realistic in the real world) vs. ensuring the solution isn't cut-paste, etc. Then you have the grading issue -- especially if there are multiple solutions (which there should be), time constraints, etc. However, it's still better than the alternative, which I've seen happen. Hiring people just really need to know the limits of a coding test and only use it as a pass-fail to determine whether folks not the technology or not.

[@HeroicKhalid]

10 years experince developer and I just lost my dream job 3 hours ago due to the stupid coding test and its puzzles. I was so honest to the interviewer that In real projects we are checking for solutions in github and stack overflow to have best ones and build our own version. Anyhow, these type of interviews need to be stopped

[@sahilandsarra]

I’m sorry to hear that. Hoping you will get what you want very soon 👍

[@OBGynKenobi]

In general, passing an interview only signals that you're a good interviewer or that you've studied for a specific type of questions, which have nothing to do with real world programming.

[@bzhmaddog]

The problem is that job interviews don't reflect real life situations (and are often done by not so competent people themself).

[@thejoblesscoder]

Did an interview today and totally bombed. One of the questions was pertaining to field of view of a character. I didn't know that the answer was a single math equation the dot product. Because how tf could I possibly know that I've never had a practical need once to use the dot product. But in the real world if I didn't know bing bang boom 1 Google search 2 minutes problem solved. Coding tests need to allow the use of Google so they can see how you'd act in real life when confronted with that problem

[@sabjohn9266]

Awesome video. As a new grad, this video eases my anxiety during this hard time.

[@sahilandsarra]

Happy to help. 😀

[@ajinxRGB]

amazing tips !! very simplified and to the point tips...thanks !!! Key take always for me : 1) Solve more Medium level questions 2) User helper functions while writing code 3) take help of interviewer and pay attention to his questions 4) Pay attention to the details of the questions 5) Complete focus on interview and not to worry about other stuff like your degree, college etc.

[@sahilandsarra]

Thanks for summarizing, Ajinkya!

[@SuprousOxide]

3 is most important. That is the biggest thing that will get a thumbs down from me. If I suggest something to you, or ask you a question, I'm trying to help you, and ignoring that help tells me you'll be more trouble than you're worth as a coworker.

[@CodingAbroad]

The stupid thing about test interviews are that the interviewer has had several hours to ask *any* question they want whereas the interviewee is expected to take the question, think and give an immediate answer which is stupid and unfair

[@sahilandsarra]

I understand your point but unfortunately, we don’t get to change the rules of the game.

[@1220MrCool]

@@sahilandsarra this is basically standardized testing studying. If you do not study, then you did not play the game correctly. This does not measure overall coding skills unless your job requires you to code like this daily.

[@mediocrestu8238]

@@sahilandsarra we do get to change the rules of the game by educating and organizing the working class against the capitalist/ruling class that forces it upon us

[@chrisoffersen]

To hear that you were turned down in over 100 interviews is exactly what I needed to hear right now. Thank you.

[@flyeagle320]

I started leetcode for SQL from few days sahil. It gives me some type of confidence. Thanks again :)

[@sahilandsarra]

Good luck 👍

[@faizanahmed9304]

Thank you, Sahil! Your tips are much helpful in preparing for our coding interviews. I know in previous videos you've mentioned that you've also learned web development like (React, Redux, etc.). My question is, how did you manage your time to learn DSA and also learning development? because I'm totally confused and I'm unable to manage both DSA and development, at the end of the day I want to say that I'm confused a lot. If possible, I would request you to make a dedicated video on it.

[@sahilandsarra]

Focus on Webdev for now and build projects to make a strong resume. Once your resume is looking good, start on DSA. Remember that with Web dev, many companies (usually smaller companies)can hire you without DSA if you’re really good.

[@faizanahmed9304]

@@sahilandsarra first of all thank you for acknowledging my comment. This piece of advice I will surely follow along. Keep making such good content. Have a nice day!

[@ccgames8189]

Programming Languages Pattern Throw Pillow... This pillow is a very beautiful pillow for computer language lovers. Buy now. $29.94 www.redbubble.com/i/throw-pillow/Programming-Languages-Pattern-by-Lanka-Shop/129569867.OHB9S

[@ayoubdouch6975]

@@faizanahmed9304 once you get the job, you are expected to make stuff as a web dev , so your knowledge of algorithms and data Structures might not shine depending if you are working as a front end dev. Build that strong portfolio and then move on. Also it is a huge bonus, if you have an IT background education.

[@faizanahmed9304]

@@ayoubdouch6975 thank you for your advice!

[@mixshots1801]

Honestly very lucky to have a person like you guiding us in very good way

[@MrHaggyy]

😅 biggest problem why people fail the interview is because they are obsessed with solving coding problems and knowing the solution to each of the coding problems. What they don't really focus, or at least don't show or communicate in the interview is their problem solving skills. Which is why the company gives you questions in the first place. They want to hear from you if you know what it means to have sorted or unsorted data. Do you want to sort it? What time complexity / memory spacing does your algorithm have? Is the complexity a problem or not? What math would you use to lower the complexity? In an ideal scenario you know a more complex solution and can solve the question. The interviewer hints a better solution, or adds more constraints. So you two together improve your code in the interview. This is quite common in practice. Finding a solution that does work. Ask one person to help you implement it in an architecture. Some helper functions might be in place already or you get limited resources. If your solution does not fit you might need to ask someone who is good in math/info to help you with a better solution. This new solution might use different functions so you need to implement it again etc. The communication what you did and why is at least as important as your solution. In a company you almoat always have people that could do what you are asked to better but you should only occupy them if needed. Also a lot of people maybe yourself years down the line need to work with your work. So it better has a clean structure thats easy to work with. Also clean work can be used much cheaper all over your company than dirty work. And if you are good you will get a problem with no known solution to date. And developing something new is a much harder but more fullfiling job. But jet again you need to be precise about what you are doing and why so the right mathematicion, physicist, engineer or programmer can give you the right pieces and tools for your problem. Nothing is more frustrating than thinking you found a genius just to realise that he fooled himself into a burnout because you thought he solve stuff on his own.

[@ohgin12345]

Oh plase

[@pedrolopez8057]

As a former manager, I don't want you to code. I want you to solve problems. Coding tests are useless.

[@creo_one]

If company offers solving some puzzle in live-coding form, it tells me that they don't know what they are doing. In daily job you rarely have some kind of algorithmic oriented issues while someone else is looking at your screen while typing and when You do have this issue then ability to learn the best approaches quickly is how You solve it. Live-coding don't show anything like that. Don't want to work there.

[@troybaxter]

Live coding is incredibly stupid. If anything, it eliminates the vast majority of good/great programmers that take their time, work through the problem, and come with a solution that is optimized and bug free. There will likely be no point in your life where you have to code on the fly, and if you are in said situation, you either a.) didn’t properly prepare, or b.) are in a more experienced position to know the ins and outs of the code you are working on. On top of that, you are very rarely in a position where you are the only programmer on a project and are always working with a team. Even at a senior level engineering position, someone is always checking your code. As such, if you have questions, you can always ask someone else in the company or on Google. The true skillset of a damn good software engineer, is one that knows how to write 95%+ of the code, and knows how to Google and/or ask his fellow engineers how to get that last 5% to be done correctly. And this is coming from someone that has nearly 10 years of experience in programming. I’ve had a experience with over half a dozen different languages and for the most part, I know how to properly navigate them and ask the right questions.

[@Laszer271]

I have another spin on why good programmers fail coding interviews. It's because coding interviews don't check whether someone is a good programmer or not. Coding interviews check if someone solved a lot of similiar problems on sites like Leetcode. There are many good programmers that have a lot of knowledge, both practical and theoretical, but haven't practiced interview questions. It's similiar to how we were in school. To have good Maths grade it's more important to cram exam questions than to actually be good at Maths. This sysytem is just flawed but it works for most because it's catered towards average programmers, not the best ones.

[@sahilandsarra]

Thanks for sharing your experience 👍

[@johnadriaan8561]

You titled your KZbin video "Why Good Programmers FAIL Coding Interviews". I get it: you want people excited about their skills to watch your video. However, I hate to burst their bubble: the coders that you describe are NOT Good Programmers. I have been on both sides of the coin: the interviewee and the interviewer. When I had to do a coding test, it was a four hour test to write a program to do something: if it didn't work, I failed. They didn't assess the code to see why it didn't work, I just flat-out failed. I completed the task in three and a half hours - but I failed anyway. When I asked why, they said "Because you didn't write all of the code. You used the C++ Standard Template Library (STL) to do half of the work." I asked if they had looked at all of the source code - all of the source code was part of the submission. They hadn't. They didn't realise that I had (re)implemented those parts of the STL that I used - in other words, during the test I re-wrote those parts of the STL that I needed. When they realised that, they hired me. That's important. I didn't need to experiment with that code: I knew what it did, and I reproduced it. Sure, while I was busy with it there were typos and bugs and whatever - but I fixed those quickly. I didn't do the "Maybe this will work?" guesswork that you describe. If THAT's the kind of programmer you are? Sorry, you are NOT a good programmer. On the other side, I have interviewed people who thought that they were "gung ho" programmers who could ace any problem. They couldn't. They couldn't even answer simple practical theory questions like "Why should you use a mutex?" let alone write code that would last in a production environment. I'm sorry, but a good programmer is more than someone just writing "medium difficulty" code. It's someone who understands the concepts to the point where they can explain it; it's someone who understands the intricacies of local versus file versus global variables; it's someone who can identify which variables need to be persistent, and which can be sacrificed. In other words, it's someone who not only knows how to write code, but what that code actually means.

[@sahilandsarra]

I enjoyed reading your comment, John. Thanks for sharing your valuable insights.

[@sergemasson7150]

Best intro off all times! Very good advices by the way.

[@sahilandsarra]

Thanks Serge!

[@FumeiYuusha]

Thanks for the great advice. I've been especially stuck worrying about things that are outside of my circle of control, where I should have been dedicating that time to improve myself where I can instead.

[@andychen5443]

Thank you for the advices! Very thoughtful and inspiring!

[@moestaxx286]

thanks for the video sahil. u are really helping me with the DSA part of my studying curriculm. it would be nice of you to make a video about which algorithms and data structures we will have to learn to be efficient in the interview. because theres a lot of them! thanks again for the insightful video.

[@sahilandsarra]

I happy you are finding the videos useful. Thanks!

[@beksaylor]

@Power Couple that is great advice about solving the medium problems. Thanks~

[@sahilandsarra]

Thanks Bek 🙏

[@AhmadAsifArifeen]

best coding mentor I have seen so far in youtube!

[@nikolatesla399]

Simple , straightforward and effective.👍

[@sahilandsarra]

Thanks 🙏

[@ishaaq5506]

You are rocking Buddy! Now Im fan of Power couple❤

[@nikolozlatsabidze2196]

the most annoying fact is that, you actually do not need any of them at work, but because there are too many people who wants to work there they developed this algorithmic interviews... meanwhile people at work write bad unreadable, procedure code without OOP SOLID, Unit tests which actually are needed.. they do not even ask questions about them. SAD

[@shimadabr]

THIS!

[@changtailiu2018]

The most important thing that many people don't understand is that your interviewer is not your oponent, instead he is your partner trying to help you solve the question.

[@ricon0suave]

You should add to your circle of control: Get a good night's sleep. Get several. Get a good meal.

[@sahilandsarra]

Thanks sir.

[@741ibrahim2]

Well as always quality content man but as a learner in Dsa I still lack in approaching but sometimes even I solve medium problem in quick time but I want to Maintain this type of consistency so that I can crack any company of my interest 😊

[@sahilandsarra]

It will come with time but I’ll cover how to think with an example in my next video.

[@741ibrahim2]

@@sahilandsarra I’ll be waiting till then stay blessed

[@archirnobenz]

Brother, I’m almost done with the popular Blind 75 and I may start your 150 questions next. Anyways, I appreciate this video a lot. Especially the area of concerns section, it may seem obvious but some of us like me tend to overthink

[@KRiSH-ei6fy]

This channel is a gold mine

[@sahilandsarra]

Thanks Krish!

[@Kkubey]

Something that is requested by teams around here is that they can participate in the interviews themself. To see if the person is a good fit for their team and has what they need. More importantly, getting along and having someone on the other side of the table who is pleasant to deal with sure helps for the future. They also ask better questions than people who are just given some terms they are supposed to search for they have no idea about. Job offers that are posted by hunters are usually including something like "needs to know how to deal with microsoft office" which makes people nope out of a lot of offers, while they wonder why no one is applying. It sounds like they are not actually looking for developers.

[@MikeBoardley]

I can tell you why I fail at them. When people are watching me I freeze mentally and I cannot think. All I want to do is run away.

[@tennisfreak312]

Just found out about your channel. Thank you for the valuable advice.

[@sahilandsarra]

Thanks 🙏

[@gamerk316]

These are the types of things as a Software Engineer I abhor. Too many companies are hiring what I call "language experts" who, frankly, have no idea how to write good code that solves actual problems. I work mainly on embedded systems where I have to work with HW that is mechanical in nature; I've seen so many "language experts" who write beautiful abstracted code...that runs like a slug and fails because they don't take into account mechanical systems are not instantaneous. They simply don't know how to develop for real hardware. I'll never pass one of these coding interviews, and frankly, I don't want to.

[@sahilandsarra]

That’s fair. Thanks for sharing your thoughts.

[@gamerk316]

@@sahilandsarra I've been quite open that if I ever leave my current job I'll never get another one; I've worked so many different languages over the years (15 and counting) I simply am not an expert in any of them. But to me: It's all the same stuff, wrapped around a different syntax. Granted, working on embedded mechanical systems is niche, but it gives you a totally different way of looking at how you develop software.

[@artstrutzenberg7197]

"asking clarification questions to the interviewer".....This is honestly one of my top criteria when I determine hire vs no hire during interviews? Secondly, how well/much does the candidate verbalize their thought process during the question? I want to know your thought process for a solution. Finally be up front and honest when you are not sure about something--"I believe that this function is going to do X Y Z." Also I do somethings pull out "left field" questions--purely to gauge how the candidate handles themselves. Will they step up and analyze things, or not. Further if this turns into a learning moment for them, how do they react--in this case the level of enthusiasm plays a part. Long and short of it, I'd rather have a candidate that * May have an error or two on a coding question, but they have decent analysis skills to get them to the solution * Is willing to seek help when needed---AND they use that assistance to help them boost their own knowledge/understanding vs using this as a crutch? Granted things WILL differ when interviewing for say an intern vs say a level 5 SDE

[@gracefry9637]

I like your calm tone and logical follow 🙏

[@curesnow6493]

Thank you… I really need to hear this

[@sahilandsarra]

Happy to help 😀

[@vedparkashgaba5478]

Very interesting informative effective and helpful to preparing for coding interview Thanks for sharing this video

[@sahilandsarra]

Thanks ❤️❤️❤️

[@ajmalali7050]

I'm a final year Electrical Engineering Student. Recently (few weeks back) I've seen this channel. I was only having a basic coding knowledge. I've learned Data structures and Alogorithms from a free course mentioned by you in a video. Really helped me to crack the technical test🙌🏻 And I've ended up getting the placement offer after the interview. Thank you so much sir🙌🏻

[@dabstar2845]

what course is it?

[@sahilandsarra]

That’s a great news Ajmal, I’m so happy for you.

[@darnzh]

Congrats Ajmal, that's awesome

[@mister-ace]

What course?

[@93hothead]

The negha code

[@shyamagrawal6006]

Nice details to know .. Thanks for your valuable time

[@JustAGuy93-G]

Because the questions are often BS that someone would never realistically have to do in their day to day job. That's my opinion and experience from 99% of the programming interviews i've done. Using intelisense as well is extremely helpful and no one can write perfect code the first time. Yet recruiters will almost always take the person with a 100% score despite saying "We just want to see how you think". Which is bs. You can memorize solutions and still be a terrible programmer, or you could have great problem solving skills and fail the test.

[@rick2591]

I just enjoy the hard problems because, they are fun.

[@sahilandsarra]

Me too 👍

[@jejejeje4491]

Hey sahil, does google allow you to work remotely?

[@a.k.k05]

Nope. Google Managers aren't that happy with remote work🤷

[@cristianfigueredo566]

@@a.k.k05 thanks Sahil

[@DC-yw5yg]

@@cristianfigueredo566 welcome sahil

[@sahilandsarra]

Yes, some people did opt for remote work.

[@HarisHussain]

@@a.k.k05 damn you were wrong lmao

[@migmit]

I've never prepared for my coding interviews. Interestingly, I always pass those with flying colors.

[@troybaxter]

Same. Either I know what I am doing or I don’t. And if I need to look up some syntax, I will. That’s how it is in the real world.

[@subhamsaini1]

Thank You so much for this video. Now I got to know where I am laging. Thank you.

[@sahilandsarra]

You’re welcome Shubham!

[@saifyabidbhuiyan]

😍🥰🥳 AMAZING! On point explanation.

[@sahilandsarra]

Thanks Saify

[@george527]

If the coding interview is easy, I will not be able to choose correctly between 100 people. Give them medium and hard problems to distinguish between good "programmers" and bad ones. Yes, you will not need 95% of the things, but if you nail the interview there are high chances you will do amazing at the job too.

[@asifshah1582]

Thank you sir.since being from non it background i had completed Python Web Development and your videos are usefull.

[@jonathanwallace7662]

You may want to consider how the company that uses these really think about their engineers though. A company asking you to do this, should be a big red flag. There is a very big difference between an engineer giving you a few logic problems to work out, and them sending you a link to a test. They will not use the results of your test, that's not while they're doing it. It's a job market survey, and nothing more. They're using it to know how many applicants of each caliber there are out there and how low they can offer you a salary. I've been in this field a long time, both applicant and hiring. If a company sends me a link to a coding test, I politely end our correspondence. Find a place that respects you.

[@stIncMale]

> How to crack coding interviews? Just keep in mind that there are companies beyond FAANG. Spending a ton of time preparing for insane interviews, solving algorithmic problems that look nothing like anything you'll ever work on, and learning how to come up with bloated system designs just to please interviewers by fitting in as many buzzwords as possible - is not only not the only way to become a software engineer, but also 100% is not the right way.

[@edu.x4325]

Bhaiya your video is so much informative. Keep uploading such types of vdo 🔥

[@sahilandsarra]

I’m glad you liked the video 😀

[@anonymous_0954]

This Man is Another Level...

[@sahilandsarra]

Thanks 🙏

[@dhanrajbhosale9313]

Great content! Everything is To the point

[@sahilandsarra]

Thanks Dhanraj!

[@dhanrajbhosale9313]

@@sahilandsarra Do bring more such content, would love to see. Subscribed! and made my friends to subscribe.

[@sahilandsarra]

Will do. Thanks Dhanraj!

[@TON-vz3pe]

Guy failed 100 interviews before getting into Google. How is that possible? Clear someone from those hundred would have hired him if he had the potential to be hired by Google.

[@_pro_grammer_]

Thank you, your contents are very inspiring and helpful💙💙💙

[@sahilandsarra]

Thanks so much Rafiul for your continuous support 🥰

[@alespecka6410]

The complexity of the algorithm for an unsorted array is not O(n), it actually is O(n log(n)), since adding and retrieving elements from a map takes O(log(n)) time. Map operations are definitely not O(1) operations!

[@sahilandsarra]

Can you share source of this information?

[@alespecka6410]

Turns out that I was wrong. It depends on the mapping that is used. Searching an element in a red-black tree takes log(n) time en.wikipedia.org/wiki/Red%E2%80%93black_tree, however, search in a hashtable takes on average only O(1), although it takes O(n) in the worst case, see en.wikipedia.org/wiki/Hash_table.

[@devkailay3046]

Short and simple vdos with great useful information as always

[@sahilandsarra]

Thanks Dev.

[@test-rj2vl]

It's kinda frustrating that the only reason you need to learn algorithms is to pass university course and then coding interview, only to use it never again. I mean in real life, thinking with you own head = bad, using framework to tell if number is even or odd = good. And then math. You study calculus and algebra and what not. And then your final job is to generate PDF invoice where each invoice row = consumed amount * unit price and total sum of all invoice rows. And even that math is told to you by customer in Jira ticket. And now in my new project I basically just write rest api that expose database to frontend and write frontend to database. And then integrations with third parties which is basically picking fields from their json and saving them to correct fields in our db - zero math, zero algorithms. And the real complexity comes from how how to get camel routs to do what I want them to do - of course I never studied that, and I was never asked this on interview.

[@sahilandsarra]

I understand the frustration but unfortunately, we don’t get to make the rules.

[@WhosShamouz]

Great, unusual tips! Thanks ♥

[@sahilandsarra]

Thanks 🙏

[@KeinNiemand]

these interviews are just so unrealistic compared to what you actually do in practice.

[@Bigbacon]

enterprise level programmer for 17 years. Built lots of large applications and what not....I still hate coding interview BS and usually fail them.

[@layer4down]

Yep. These are great pieces of advice.

[@SamOnTehsea]

The only time i practiced a coding test , i was surprised that my answer was wrong because my code was working with the test data they gave me. The problem what’s that the question itself was not specific enough i was missing part of the problem that i did not new existed

[@sahilandsarra]

I’m sorry to hear that but some companies do play these sneaky games

[@SuprousOxide]

In a real interview, if the interviewer was any good, they would step in to clarify the question when it was obvious you had misunderstood it. Or let you finish, and present the clarified example as a second question. When working, you'll always have the opportunity to ask for clarification on the requirements, an interviewer is going to provide the same option to you.

[@athulstalwart2715]

Great Video.Thank You! ❤❤❤

[@sahilandsarra]

Thanks Athul ❤️❤️❤️

[@carbonnephoenix]

I learned a lot from this video. Hence subscribed ✌️

[@MrHanditar]

Great video, thank you

[@sahilandsarra]

Thanks 🙏

[@dapcook]

Problem may be these coding interviews are most likely given by people who themselves are not "leet". just cause it's amazon or google, doesn't mean quality coders at all.

[@bhargavpratimsharma2024]

Hi Sir ! Your videos are awesome. Currently I'm in BCA 5th sem. Till now I have learnt C programming, Data Structures through C, DBMS, C++, a little bit of web development(the backend in php though I'm not interested in web, i h've to learn it as part of syllabus), Computer Organisation and Architecture, Digital Logic fundamentals, Operating system, Java programming and python programming. As final year projects , in 5th sem, I'm using Python and Kivy md to build my project. How can I sit for off campus interview??, as I am pursuing BCA from a govt. College and no company visits here.

[@mattweger437]

"I did it I made it into a fang company" as they realized they'll be stuck fixing CSS errors for the next decade because there's literally nothing to do

[@newbieguy2509]

Hello Sahil, your videos are totally to the point and not with some bs. Also , i think most people can relate themselves to your experience. Thanks for these helpful videos.

[@sahilandsarra]

I’m glad you liked the video. Thanks 🙏

[@sarav-Frontend_Engineer]

Great and most vital tips 🙏 always helping us. Thanks Sahil 😊

[@group8183]

Omg you are reading all comments lots of love from harsh brother ❤

[@sahilandsarra]

Of course Harsh ❤️

[@noshitsherlock6908]

once you become comfortable 3:33 with interview style questions, take a stopwatch and start timeboxing your practice sessions. Give 3:38 yourself 45 minutes to solve medium problems at first and try to get to 30 minutes if you can.First way you can use your interviewer is by clearly explaining Another reason why people fail coding interviews is because they violate the asic design principles of programming in the interview. This is how most people’s interview solution looks like. 5:22 Everything that comes in the mind just gets dumped in this one place and that is the final solution. 5:27 In reality, if you want to make your life easier, you should break your code into helper functions if possible. This is especially 5:33 important if you are using the same code again and again. There are 3 major advantages of doing this. 5:38 One, you don’t look like a newbie who doesn’t really know how to write code at an actual job. 5:42 Two, If the interviewer wants you to run the code and you need to debug the solution, having well 5:46 defined helper functions makes it very easy to debug. That’s because you can test your helper functions 5:51 separately if needed. Lastly, when you don’t have enough time to code the full solution, you can 5:55 just tell the interviewer that you will write this helper function that has this particular behavior 5:59 at the end. If you have some time left in the end, you can obviously write the helper function. But if you don’t, 6:04 the interviewer might be able to see that writing the helper function is actually easier than the actual 6:09 code you wrote during the interview. That way, they will be willing to let it go if you 6:13 complete the rest of the solution. This only works if helper function is not really the core part of the solution. 6:18 So, make your life easier by using helper functions First way you can use your interviewer is by clearly explaining your solution to them. That’s because most humans can not resist the urge to correct you if you are saying something wrong. And when they correct you, listen to them carefully because they will drop some very useful hints. By doing this, you can avoid the situation where you end up coding the wrong algorithm and it’s already too late to correct your mistake. Second way you can use your interviewer is by paying attention to clarifying questions they ask you when you are coding your solution. Most of the time, interviewers do this when they have spotted something wrong in your code. So, always pay attention to your interviewer.

[@julithomas8792]

I was in an interview which I got a ridiculous request: "Can you type a working code now of the solution you mentioned?" I answered: it is complex approach and cannot be done in just 10 minutes with your eyes wachting my hands. And I was rejected by the voice president (who has little software knowledge) of the company in the final round. (I was already approved by multiple senior engineers before that, also Coding Test was passed)

[@basicguy5785]

I refuse to take coding interviews, especially if they want me to do algorithms. I have noticed that the problems I'm asked to solve, are nothing I would do in the actually job 95% of the times. Also you ability to solve those algorithms doesn't prove how good of an employee you can be, unless you do actual work where they are applicable.

[@sahilandsarra]

Ok sir.

[@pradhansebak9920]

Hi Sir, I'm From India and I'm currently practicing DSA questions on leetcode but i didn't Have Any Project For My resume Can You Suggest Me 1 option from below. option 1 : buy a Full stack course And learn from basis to advance Step by step option 2 : Building a project with learn at the same time. option 3: your opinion

[@sahilandsarra]

Option 2 if you can

[@achiver]

Seriously I feel samething why I reject it many interview thanks for give me clear view.

[@sahilandsarra]

Happy to help Nikhil

[@5556665012008]

I'm a senior engineer with a decade of experience and have never done any leetcode

[@jerobyarts5654]

Bruh Iam not even a CS student and still learning this despite my stupid degree ....

[@sahilandsarra]

I was not a CS student either

[@AmanSingh-vv1td]

Hello Sir, Your all videos are informative & helpful 🙏🙏🙏

[@sahilandsarra]

Happy to help 🙏

[@almousafir4041]

Great video 👍👍👍

[@sahilandsarra]

Thanks ❤️

[@bicycleworld7049]

Thanks a lot for these fine videos . they are very inspiring and helpful /and up all/ your share of your experience is very valuable it gives confidence to go on continuously and never give up thanks.

[@sahilandsarra]

Thanks 🙏

[@Fuxy22]

Meah... if the coding interview is too difficult it wasn't meant to be. There is no point to worry about it and if you are required to get right from the start it's a shit interview. The scenario needs to match a normal coding situation as much as possible. Hell if the problem is too difficult then it's not worth my time especially since at the end of the day no matter how good I did on the interview its a numbers game. Especially when salary expectations etc factor into it as well...

[@chigicherlamounika9977]

Thanks for your great words

[@sahilandsarra]

I’m glad you liked it. Thanks 🙏

[@chigicherlamounika9977]

Your really good bro

[@Martialarts7700]

❤️❤️❤️❤️Thanks lot Big Like

[@sahilandsarra]

Thanks 🙏 ❤️

[@RodrigoTonin]

I was like "how do you code an interview?" then, 3 seconds into the video I went "Ohhhhhhh I see...."

[@bibliusz777]

I only have HR interviews every ~6 months. Fortunately ~every month I have some small commission on Upwork, but it is definitely too little

[@jawadkaiyal5008]

just an advice for your channel don't add music for the videos because it will become hard to understand the talk on the video

[@ifstatementifstatement2704]

Probably because they are too concerned with which design patterns to apply and designing classes rather than making the damn program work.

[@vivek-bh6od]

Which programing languange is best to learn now??

[@sahilandsarra]

I’ll make a video on this shortly

[@troybaxter]

Depends on what industry you are interested in going into.

[@tanmayyguptaa]

Sahil sir can you please tell that I am learning PHP and making project on it also. But there is a hype today that PHP is going to be dead is it true or not should I continue with PHP. Please tell.

[@sahilandsarra]

If I were in your place, I wouldn’t do PHP.

[@gokul7701]

iam beginner,just started to learn python by following the roadmap suggested by you.i dont understand anything about hashmap,time, space that you mentioned here.would I eventually be able to understand these topics?

[@_nimrod92]

This is what happens when the same people who administer the SAT/ACT end up in tech.

[@MrPicklecopter]

2:58 You can also apply this tip to other areas of your life to excellent effect.

[@the__saswat__nayak]

Hey brother, though I am learning DSA and am comfortable enough just to solve questions like prime number or binary search questions. For me the leetcode questions even if it's easy I am not able to analyse the questions and think the way coders think. Can you please make a video or Suggest me as I am a beginner in learning DSA using Java language, i always have this fear of doing projects and also the project videos consisting 12-13 java projects and all in KZbin is also frightening me. I don't know in what step I am doing wrong.

[@sahilandsarra]

I have another video on Leetcode coming soon.

[@the__saswat__nayak]

@@sahilandsarra Sure brother, waiting and have the same excitement to learn😊

[@shimadabr]

Did you start coding in less than 1 year? If so I think the feeling is perfectly normal. The more Algorithms you make the more confortable you get. I suggest always writing the key points of the problem you're solving and, if you can, type a solution in pseudo-code, so you don't have to think about syntax and implementation details. Done that you start coding your solution. About projects, you should focus on simple ones first, don't try to make a fully-featured application for example. Get a simple ideia and implement it without thinking too much about corner cases, design, UX, features and elegance (a "proof of concept"). After you feel it's "complete", you worry about these things and expand.