Chris, That list is pretty good!
When we have interviewed in the last few years, we've made a point about asking about background processing. I think most Rails app now need some sort of background processing, for a variety of reasons. I have always found the conversation interesting, especially because Rails did not have any of this built until very recently (ActiveJob) and there are many choices with different data stores, etc. There are a lot of tradeoffs to talk about: Sidekiq is great, but if you don't already use Redis it may mean adding another database to your app, etc. I recently came across the chart in this post: https://www.codefellows.org/blog/this-is-why-learning-rails-is-hard I think that mind-map is fantastic, and if anything, it's easy to expand on that. If I was interviewing, I would read up on the parts where I feel weakest. Good luck, — Ylan Segal [email protected] > On Aug 10, 2015, at 9:00 AM, Chris McCann <[email protected]> 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. -- -- 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.
