Some practical tips:
Make your Github profile look as good as possible.
Get your LinkedIn profile organized and well written. Be sure you mention Ruby, Rails in your linkedin skills.
Get a Stack Overflow careers profile.
Start contributing to open source (even if at a very, very small level.) For example, for a gem I use frequently, I fixed just a small thing ( I thought it was important, though it only took less than one line of code.) It didn’t take much skill, but still, it was a contribution.
If you’re doing a side project (which you should always be doing,) commit it to github, but be sure you’re acting “as-if” it’s a professional project – meaning, use well formed commit messages, Tim Pope has a great, short commit message style guide you should read.
I guarantee you that you’ll start getting slammed with recruiters trying to get you hired. That of course, doesn’t get you the job, nor are all the jobs from companies that would necessarily work to develop your skills, but if you can confidently move around the rails environment and are grounded in the fundamentals (such as Array manipulation) then you’ll be good enough to get started.
I recommend that you work on your front-end skills as well. The “calling card” app that you build needs to look good – even if the function is awesome, first impressions mean a ton, unfortunately.
I would get your Vim skills up to speed. In my experience some of the best shops for new talent also happen to be Vim shops, which means, if you get to do the pair programming interview, you don’t want to be flustered with the Vim (the programming itself is hard enough!)
I would be TDDing everything you build. If that seems “hard,” Good! You’re going to be learning testing right alongside learning the “code.” If you get an interview and get to do a coding test… Remember to approach it test-first. I would learn Cucumber. First, it’s awesome, secondly, it makes you better at communicating the purpose of something you’re trying to build which helps develop your critical communication skills. I would even Cuke stuff you build for yourself.
Also, I would listen to the Ruby5 podcast – just getting used to the Ruby and Rails community jargon, lingo, argot, will make you yourself more fluent. Remember, fake it til you make it, and you will!
Learn Haml, Sass, Coffeescript. You don’t necessarily have to use them (I think you should!) but many places are looking for those skills and by adding that to your arsenal, you’ll be able to jump into any project and know what you’re looking at. Think of yourself as a Diplomat from the country of NewDeveloperstan – like any diplomat, the better you can relate to the host country (your prospective employer) the more they’ll be willing to hire you, help you and the more they’ll be willing to overlook a relative lack of experience.
This is obviously a highly opinionated response, but hopefully you find some useful bits! Good luck!