Disclosure: This post includes affiliate links; I may receive compensation if you purchase products or services from the different links provided i...
For further actions, you may consider blocking this person and/or reporting abuse
How is bubble sort implemented?
Don't implement it, use insertion sort instead for quick and dirty implementations.
Its hard to believe that people still try to hire this way. It rarely achieves the purpose you're aiming for.
I have interviewed about a hundred people.
Yes, I'm one of those scoundrels that presents a coding interview.
I look for two things in a coding interview: technical competence, and character assessment.
The number one thing that a candidate can do to immediately ruin their chances: try to lie or attempt to baffle me with bulldoodoo. I've got a very good BS detector.
So if you are interviewing, and you don't know something, say "I don't know." It's hard to do, especially in an interview. But an "I don't know" is not necessarily a strike against you. Whereas BS is a disqualifier.
Pretty cool article :D
I made a course a couple of months ago that received decent feedback, might be worth taking a look at the structure and let me know what you think ;) :
udemy.com/course/leetcode-in-pytho...
When I was interviewing, I didn't look for the candidate who knew everything, I looked for the people who could think about new concepts, come up with new solutions to problems they haven't encountered before. Anyone can memorize and spit out some lines of code. If you want top talent, you have to see how they fail. So I go the extra mile... I ask increasingly difficult and obscure questions until I reach the interviewee's limit of knowledge. At that point the pass or fail can be determined by looking at how they respond to their own failure:
A. they don't know but they try to hide their lack of knowledge.
B. they don't know and just admit they don't know.
C. they admit not knowing and continue with "here's how I think it might work" and are genuinely curious as to what the solution is. This one is the winner.
Don't just memorize bunch of code. Learn how to approach problems you never encountered before. Granted, most interviewers aren't like me. Most interviewers usually just ask if you're good at regurgitating an algorithm and that's all that matters to them. You pass the interview if one of the algorithms you memorized is the one that they asked. That's why the software industry is full of copy & paste engineers who can do a fine job of applying existing solutions to problems but can't think themselves out of a paper bag when they encounter novel problems.
Usually I never comment on blogs but your article is so convincing that I never stop myself to say something about it. Just have a look at this Air hostess Training
Thanks for sharing this post...!
Check this site as well: interviewbit.com/courses/programmi...
This site is very up-to-date with the latest interview question and for that matter there are alot of top tech companies interview questions covered.
Thank you for all these tips and for the great article 😊😊
This is such a resourceful article. 😇
So this article is about let us know that you are able to collect some links on internet and promote yourself ? What if you focus more on the reader and less on you ?
Thanks a lot for taking your time in this investigation labour. A great resource.