I see lots of people saying you NEED to grind leetcode to get a job. That they spent 100s of hours studying to ace interviews.
This sounds absurd. I've never done it and I also have yet to 'fail' an onsite. I think you just be affable, talk through your process and do some problem solving. When I interview people I actually kinda hate when the problem is easy/seems memorized.
Anyways what do you think? Is it needed? Maybe I'm just an asshole who got lucky?
- Doesn't matter. If you're not from the CORRECT part of the country or world, and don't have the most elite credentials, then it doesn't matter how fast or thorough your problem-solving and algorithmic skills are, nor your communication, nor your ability to lead a team to success.
It's like throwing yourself onto a wall that's painted as an entrance window with a small wall at the bottom. Then the people on the inside will upon up another wall on the other side of the building if you are one of Their people.
- The last interview I failed wasn’t the coding (which was easier than I expected from blind). It was not remembering the best stories for the “tell me about a time <oddly specific situation>”
I wish I had spent more time reflecting and practicing that part.
- HP ModulusI don't think popping a memorized solution should get anybody anywhere. When I have done that, they keep adjusting the problem until I get stuck and have to problem solve anyways.
Just do a ton of programming either at your current job or at home. Have good examples that aren't hypothetical, ideally ones from you current job. Understand popular algorithm techniques and data structures.
Get in that interview and let your intuition run wild and free. Communicate like with a coworker problem solving together.
- Micro Focus / Eng5’6” RuskiThe problem is that even unknown or shit tier companies are asking difficult problems and expecting flawless solutions.