I'll add another tip from my experience as a hiring manager at Google. Talk to the hiring manager and provide them real world examples of your coding skills. Especially useful if you've contributed to open source projects. The hiring manager can write a Statement of Support to include in your packet that can help address a weak coding interview at Staff+ level.
In a perfect world, we would have a magical device that connects to the brain, gathers everything the candidate knows, and determines if they are suitable for the position.
Leetcode is not the solution, and distracts the industry from finding better alternatives.
I'll add another tip from my experience as a hiring manager at Google. Talk to the hiring manager and provide them real world examples of your coding skills. Especially useful if you've contributed to open source projects. The hiring manager can write a Statement of Support to include in your packet that can help address a weak coding interview at Staff+ level.
That is a great advice!
Wow I need to actually try negotiating leetcode out of interviews. Any tips?
Just ask.
Mindblown by the tip of negotiating out of doing leetcode interviews.
Thanks for sharing your process, Gourav and these tips!
In a perfect world, we would have a magical device that connects to the brain, gathers everything the candidate knows, and determines if they are suitable for the position.
Leetcode is not the solution, and distracts the industry from finding better alternatives.
Great article, Gourav!
Thanks Michal!
Exactly. Leetcode sucks. But they made it as a trend but unnecessary.