Why Good Programmers FAIL Coding Interviews
Vložit
- čas přidán 28. 10. 2022
- 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/dp/1982137274
► 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: powercouplejourney@gmail.com
#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. - Věda a technologie
For me coding is an art and very creative... Coding under pressure during an interview is nonsense
Exactly.
I just finished my coding test and felt unrespected for the given questions to the point I just left
Just realized that today 🤥. Successfully messed up 50% of the interview.
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.
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.
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.
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.
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"
@@EskoLuontola can you link the proof of the algorithm?
Programming is always about trials and errors, there is no way when the first time you write the code is completely fine and perfect.
You’re missing the point.
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.
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.
Tell this to Donald Knuth, famous for "“Beware of bugs in the above code; I have only proved it correct, not tried it.”
@@sahilandsarra yeah he may not understand what you are saying properly
Thank you for the advices! Very thoughtful and inspiring!
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.
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.
I happy you are finding the videos useful. Thanks!
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
This is a very good confirmation. Thanks for sharing from your point too.
Awesome video. As a new grad, this video eases my anxiety during this hard time.
Happy to help. 😀
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.
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
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.
@@BW022 to prove candidate's competence, they could just give them simple project or provide personal portofolio
@@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"
@@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.
Best intro off all times!
Very good advices by the way.
Thanks Serge!
@Power Couple that is great advice about solving the medium problems. Thanks~
Thanks Bek 🙏
To hear that you were turned down in over 100 interviews is exactly what I needed to hear right now. Thank you.
Great and most vital tips 🙏 always helping us. Thanks Sahil 😊
Simple , straightforward and effective.👍
Thanks 🙏
Honestly very lucky to have a person like you guiding us in very good way
I like your calm tone and logical follow 🙏
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.
Thanks for summarizing, Ajinkya!
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.
Just found out about your channel. Thank you for the valuable advice.
Thanks 🙏
Thank you… I really need to hear this
Happy to help 😀
Nice details to know .. Thanks for your valuable time
Great, unusual tips! Thanks ♥
Thanks 🙏
Thank you, your contents are very inspiring and helpful💙💙💙
Thanks so much Rafiul for your continuous support 🥰
You are rocking Buddy! Now Im fan of Power couple❤
Short and simple vdos with great useful information as always
Thanks Dev.
😍🥰🥳 AMAZING! On point explanation.
Thanks Saify
Great Video.Thank You! ❤❤❤
Thanks Athul ❤️❤️❤️
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.
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.
@@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!
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
@@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.
@@ayoubdouch6975 thank you for your advice!
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.
Thanks 🙏
Yep. These are great pieces of advice.
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.
I’m glad you liked the video. Thanks 🙏
The interviews don't even reflect what people will be doing for the actual job
The problem is that job interviews don't reflect real life situations (and are often done by not so competent people themself).
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
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 😊
It will come with time but I’ll cover how to think with an example in my next video.
@@sahilandsarra I’ll be waiting till then stay blessed
best coding mentor I have seen so far in youtube!
I started leetcode for SQL from few days sahil. It gives me some type of confidence. Thanks again :)
Good luck 👍
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.
I learned a lot from this video. Hence subscribed ✌️
Great content! Everything is To the point
Thanks Dhanraj!
@@sahilandsarra Do bring more such content, would love to see. Subscribed! and made my friends to subscribe.
Will do. Thanks Dhanraj!
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
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
I’m sorry to hear that. Hoping you will get what you want very soon 👍
Very interesting informative effective and helpful to preparing for coding interview Thanks for sharing this video
Thanks ❤️❤️❤️
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.
Thank you sir.since being from non it background i had completed Python Web Development and your videos are usefull.
Bhaiya your video is so much informative. Keep uploading such types of vdo 🔥
I’m glad you liked the video 😀
Great video, thank you
Thanks 🙏
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
I understand your point but unfortunately, we don’t get to change the rules of the game.
@@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.
@@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
Thank You so much for this video. Now I got to know where I am laging. Thank you.
You’re welcome Shubham!
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.
Hello Sir, Your all videos are informative & helpful 🙏🙏🙏
Happy to help 🙏
Great video 👍👍👍
Thanks ❤️
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.
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.
This channel is a gold mine
Thanks Krish!
❤️❤️❤️❤️Thanks lot Big Like
Thanks 🙏 ❤️
😅 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.
Oh plase
Hello sahil, first of all your videos are amazing. So thank you for putting so much efforts for us.
Secondly I am so confused in what to do and what not to do. I have completed my MSc but in different stream I had done my graduation in CS. I want a job in this CS field so I have started DSA but I am confused whether I'm having a right start because there are so many paid course bragging confirmed placement projects but how can I find projects without buying those courses and how can I build up my skills. I mean is it the right thing to start learning DSA first. What is your suggestion on this.
Hi Shreya! I have already made multiple videos on roadmaps on the channel.
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
Hii... How is ur studies now ?
Got placed in a company ?
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🙌🏻
what course is it?
That’s a great news Ajmal, I’m so happy for you.
Congrats Ajmal, that's awesome
What course?
The negha code
This Man is Another Level...
Thanks 🙏
Thanks for your great words
I’m glad you liked it. Thanks 🙏
Your really good bro
You titled your CZcams 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.
I enjoyed reading your comment, John. Thanks for sharing your valuable insights.
As a former manager, I don't want you to code. I want you to solve problems. Coding tests are useless.
these interviews are just so unrealistic compared to what you actually do in practice.
Hey bro You're the one to Improve my self-confidence I'm not a cs degree student I'm worried about that...I started to learn DSA please would you give us the perfect roadmap to learn DSA in Python 😉
Hey! I have already covered DSA in another video.
Thanks 👍
I’m glad you liked it 🙏
"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
Thanks a lot
Thanks Asibul.
Thank you ❤️
Dunith 🙌
Seriously I feel samething why I reject it many interview thanks for give me clear view.
Happy to help Nikhil
Which are the best IT roles acc. to you which maximize this fraction? -> (income x growth) ÷ (actual work hours x tech friction)
I just enjoy the hard problems because, they are fun.
Me too 👍
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
THIS!
Awesome
Thanks Tara!
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 CZcams is also frightening me. I don't know in what step I am doing wrong.
I have another video on Leetcode coming soon.
@@sahilandsarra Sure brother, waiting and have the same excitement to learn😊
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.
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.
Let's go
🤘
Thank you for your videos♥️♥️.
Sir how to i improve my English . Please give some tips for me.
In comments are adequate for me.
Hey sahil Can you make a video on web development
And Thank you for your wonderful video🔥
Hey! I have already made this video.
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.
Thanks for sharing your experience 👍
Sahil, can you please make a Timetable for me to practice coding and how can I balance school life. (Class9)
Omg you are reading all comments lots of love from harsh brother ❤
Of course Harsh ❤️
Best intro😂😂❤
Thanks ❤️
I've never prepared for my coding interviews.
Interestingly, I always pass those with flying colors.
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.
I am really big fan of u
Thanks Durgaprasad!
Thanks bro
Thanks 🙏
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.
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?
In my interview of career you are my helper function
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.
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
I’m sorry to hear that but some companies do play these sneaky games
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.
I am in 1st year college right now. Please can you suggest me where to start🥲 and also make a video
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)
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
Option 2 if you can
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!
Can you share source of this information?
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.
2:58 You can also apply this tip to other areas of your life to excellent effect.
You should add to your circle of control:
Get a good night's sleep. Get several.
Get a good meal.
Thanks sir.
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.
I understand the frustration but unfortunately, we don’t get to make the rules.
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.
Make a videos on CTC vs base salary for top companies..
Will cover it in upcoming videos.
Please make an video of Linkedin Profile i am waiting fot it
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.
enterprise level programmer for 17 years. Built lots of large applications and what not....I still hate coding interview BS and usually fail them.