3 ms·
> I'd put "ability to work in a team" above "raw academic/reasoning ability" for the vast majority of engineering roles, any day. In this hypothetical, why do
by lucianbr 1y ago
> I'd put "ability to work in a team" above "raw academic/reasoning ability" for the vast majority of engineering roles, any day.
In this hypothetical, why do you do leetcode hard interviews?
- Too 1y agoOne can be gifted while still producing code that the rest of the team can read.
- SkiFire13 1y agoMaybe because they are simplier to practice than working in a team?
- bluGill 1y ago> why do you do leetcode hard interviews? I don't. I do easy code interviews because there are people who work great on a team and know enough buzzwords to sound like they know how to write code, but cannot. Something that isn't hard to solve in about 20 minutes (I can solve in 5 - but I've seen a solution several times and so don't have to think about the solution), but is different enough that you haven't memorized the solution. If you can't solve an easy problem then you can't code.
- xenocratus 1y ago> In this hypothetical, why do you do leetcode hard interviews? I thought I already answered that: >> Not that the latter doesn't matter, of course, but it's by no means the one and only measure.
- nothrabannosir 1y agoIt is the only thing you measure when you do leetcode.