3 ms·
Wait what? You’re saying for people who already went through the leetcode hazing to join the company, they have to do it all over again for internal promotions?
by ornornor 4y ago
Wait what? You’re saying for people who already went through the leetcode hazing to join the company, they have to do it all over again for internal promotions? That’s absurd, I had no idea.
Isn’t the “rationale” for leetcode that they dont know you and as far as they can tell, you copy pasted all your open source code from SO, so there is no other way to prove that you can actually write code than to take a leetcode? But if you’re already working there, couldn’t you (bear with me because this is a little crazy) just point in the general direction of the code you’ve worked on at said org and ask your colleagues or manager for their opinion on how much of that was copy pasted from the internet?
- novok 4y agoNo when you change jobs externally lol. Internal moves are pretty easy.
- ornornor 4y agoThat’s a little less absurd even though leetcode is a waste of time. FWIW, I typically decline code challenges. I have ample open source code that’s commented, publicly visible, and tested. I’ll sometimes humor them if I like the team and it really takes an hour or less to complete (note that when they say an hour it really means 4–8h, so I assess it myself). But otherwise, I point at my open source code, offer to pair on a feature/bug on these OSS projects, or drop out of the pipeline if it’s not acceptable to them. Same with quoting a salary number or salary history: if they ask I decline to answer and if “the software won’t let me continue without” I offer to fix their software and drop out of the pipeline if “tbd” or “1” won’t work.