Preparing for Ruby on Rails job interviews

There are lots of excellent books and websites that provide general help with preparing for coding interviews, but few discuss the expectations of Ruby on Rails employers.

Here are a few links to fill in that gap:

• Sandeep prepared a comprehensive list of Ruby on Rails Interview Questions, covering everything from Ruby language basics (What is a Symbol?) to Rails-specific questions (What is RESTful routing?) and Test Frameworks (What is an alternative to using test fixtures?)
• Toby Hede provided an excellent list of skills Rails developers should have at entry, mid and senior levels
• Suggestions for creating a project for your resume - I particularly liked George McDowd's suggestion: write a custom app, email the source to a prospective employer, then offer to walk them through the code to prove you'd written it
• Attend a Ruby on Rails Meetup group - I've done this a couple of times, and it's a great way to get a feel for the local Rails job scene.
• A peek behind the curtain! Actual Rails employer John Philip Green posted his 11 tips on hiring a Rails Developer, and Tim Goh shared his Practical Tips for Hiring Ruby Web Developers. While you might disagree with some of their criteria for an ideal employee, e.g., a personal blog on Rails, etc., keep in mind that this is what real live hiring managers are looking for in a Rails developer. These posts let you look inside the heads of people very like the ones who will interview you. Any insight you can gain into an employer's POV will only help you prepare to meet their expectations and needs.
• OK, not Rails-specific, but Sijin Joseph's Programmer Competency Matrix is a great 10,000 foot overview of the general skillz you should have, and Steve Hanov's massive list of five essential steps to prepare for your next programming interview will keep you busy for weeks.
• Edit (26 May 2013): An extensive and excellent list of Rails interview questions from Anil Punjabi's blog.

Many of the ideas for Ruby job interviews could of course be extrapolated to any software development interview. Happy hunting!