Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> There is an entire industry built around tech interview prep now (books, websites, practice/mock interviews). Many would defend this practice because their paycheck directly depends on it.

Or you know... an algorithm and data structures class that's part of a serious Engineering/CS curriculum.



That's enough for passing familiarity with what the algorithms are / pointers to reference material when appropriate. Not nearly enough to perform on command from memory in 20-40 minutes.


I mean,

If someone knows he's interviewing at a place where there will be a coding interview, he would be crazy not to take a look at his algorithm textbook.

And maybe if the course only only gave the candidate a passing familiarity it wasn't thorough enough?


At the end of Princeton's Algorithms I-II on Coursera you've done fewer than 20 implementations, and those were open-book assignments with week-long deadlines.

A reasonable interview prep cycle would be closer to 200 practice problems, under time pressure.


>he would be crazy not to take a look at his algorithm textbook.

Why? what's wrong with going "purely" into interview?


an algorithm and data structures class that's part of a serious Engineering/CS curriculum

Good luck remembering the kind of details a typical interview asks for 10 years into the business.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: