I spent some time this fall interviewing at various places across the industry. As pretty much anyone who's planning to do this knows, all companies ask, basically, the same flavor of questions. However, they do tend to vary in difficulty and scope. At the core of the interview experience lie algorithms and data structures, i.e. standard, first-year, undergrad stuff. Although we can spend all day determining whether this is a good measure of programmer ability (it almost certainly isn't, especially for companies whose primary business is building pretty simple iPhone apps), the deal is that learning to play the game is better (and certainly more lucrative) than avoiding it.
Most interview prep material seems to be either in Java or C++, primarily due to their ubiquity, as well as the fact that they don't "do too much," i.e. most abstractions are pretty thin. But, there's no reason why a Rubyist can't work his/her way through interviews with our tool of choice. In this article, we'll go through some reasonably easy to average difficulty interview problems using Ruby. Most of the time, harder interview questions aren't hard because they involve really complicated code; instead, they just require more thought and some insight. So, by figuring out how to do the easy stuff in Ruby, you should be set to tackle the hard problems, too.
Continue reading %Ruby Interview Questions: Linked Lists and Hash Tables%
by Dhaivat Pandya via SitePoint
No comments:
Post a Comment