There are hundreds or thousands of things you might use a couple times a year. Why should 75% of the interview be devoted to this one?
Does the justification for a Google-style interview (need to whiteboard O(N) because it matters for large N) even hold up at Google?pic.twitter.com/67s81AV6MG
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
even if your job did require O(N) solutions, would it require *whiteboarding* them? Or could you take a few hours, or even days?
-
Yeah, I actually do this stuff fairly often, but I never have to whiteboard up a solution within 45m of hearing about an algorithms problem.
- 1 more reply
New conversation -
-
-
FWIW I think these skills I needed to pass my Google interview correlate with what my job required, so the process isn't useless.
-
I got these kinds of questions for a hardware design position. I've heard of people getting them for front-end positions. YMMV, of course.
- 1 more reply
New conversation -
-
-
Is this still the common "Google-interview?" I've been asking questions focused on code comprehension, testing, and design for 5 years.
-
It must vary depending on who you draw, but I mostly got those questions < 5 years ago and I hear similar stories from other folks.
End of conversation
New conversation -
-
-
One possibility, it's not about DSA being important, it's about being able to quickly (re)learn them and perform in an interview
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.