Chris, I did an interview recently. I liked this:
https://srikantmahapatra.wordpress.com/2013/11/07/ruby-on-rails-interview-questions-and-answers/ which is mostly a series of "What is...?" questions. And this is similar, but with some code: http://anilpunjabi.tumblr.com/post/25948339235/ruby-and-rails-interview-questions-and-answers I was asked what the major changes introduced in Rails 3 and Rails 4 were, what my favorite gems are (just try to think of gems on the spot! I mentioned that there are 6,400 gems), what sources I liked for keeping up (I lamented the loss of new Railscasts, mentioned Toptal and an ebook I liked, and admitted I still look at the Guides=guides.rubyonrails.org), and what the worst code I've seen was like ("Big Ball of Mud" anti-pattern). I was also asked about a couple computer science topics, one of which I had never heard of. I thought I had at least heard of just about all of them. Hard to prepare for that. If those lists don't have testing in there, that would likely be important. Know whether you like TDD and if you don't, then ask if they do it religiously (you might hate working there). Good luck! Scott On Monday, August 10, 2015 at 12:00:12 PM UTC-4, Chris McCann wrote: > > SD Ruby, > > Though I've been building apps in Rails for over 8 years I've never > actually interviewed specifically for a Ruby on Rails senior developer > position. I'm suddenly left wondering how much stuff I don't know! > > Of course I Googled the topic, and here are a few decent results: > > http://www.toptal.com/ruby-on-rails/interview-questions > > https://gist.github.com/ryansobol/5252653 > > https://github.com/afeld/rails_interview_questions > > > I also asked someone who's well-known in the Ruby community, and his > answers were: > > - Knows how the metaprogramming works that makes Rails work > - Knows a bit of Rails internals > - Fully understands how Bundler etc. work > - Gets how concurrency works in the various web servers and what the > tradeoffs would be > - Has opinions and good ideas about good OO design and architecture in > the context of a Rails application (as opposed to letting the framework > rule) > - Fully versed in all the REST stuff > - Good knowledge of troubleshooting production issues > > > Anyone else have suggestions? If you've been through a senior Rails > developer interview, what else were you asked? What did they stump you on? > > Cheers, > > Chris > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
