Ruby but not Rails on my Resume

Question

I have listed Ruby as a skill on my resume becuase I've been programming in Ruby for 5 years while I work on my Ph.D. thesis. I've mostly been using it to implement natural language processing algorithms.

I'm starting to look for a job, and I posted my resume to a few sites (as an extra bonus when applying to certain on-target jobs). Now I get recruiters calling me to offer me Ruby on Rails jobs. The problem is that I've never learned Rails. It was never relevant to what I'm doing for my Ph.D.

How do you recommend handling this situation to avoid wasting my time and theirs? (And learning Rails probably isn't an option until I finish my thesis.) Can my resume be adjusted to make this clearer? Should it be adjusted? Should I just politely tell them on the phone that I don't know Rails?

By the way, the relevant part of my resume simply says:

Skills:

Programming Languages: C, C++, Java, Scala, Ruby, LaTeX

Databases: MySQL, XML, XPath

and lists a few other skill areas that couldn't possibly be confused with a Rails developer.

Answer 1

You could tell them you're very good with Ruby (assuming you ARE good with Ruby) and that you'd be willing to learn Rails as a part of a new job (assuming you ARE willing and interested to learn the Rails framework). On-the-job training is not that uncommon. I had to pick up JavaEE, Spring, Hibernate on the job. I had Java and web apps (not in Java) so they figured I could adapt.

In general, don't put negatives on a resume such as "Ruby but NOT Ruby on Rails", it just doesn't look good.

Answer 2

This is a good question.

I would leave your resume alone. It's good to filter out languages you are not comfortable working with, but do not filter out frameworks. You don't know what version of your resume will be sitting on someone's desk when they become interested in you. By the time they see it, you might be a well-versed Rails developer.

With that, I would much rather have a dozen calls about Rails opportunities just to have one turn out to be plain Ruby. Recruiters tend to think ruby == rails so don't confuse them.

Answer 3

To a recruiter ruby = rails. It's not right, and it's a very narrow view of the Ruby world, but that's how a recruiter processes buzzwords. It would be like equating Django with Python, but the majority of the demand for Ruby jobs is for Rails applications. It will take time and another killer app to make that distinction.

Answer 4

Nothing that you do on your resume will stop 90% of recruiters from contacting you about Rails jobs. Just develop a thick skin and cultivate patience.

Answer 5

I would leave it as is and just list Ruby.

I would also spend 1 hour boning up and if you know Ruby well, there's not that much to know.

• It's Model-View-Controller.

• The models represent database tables through the rails ORM, mapping models and attributes to tables.

• Functionality such as authentication can be done through 'gems'.

• html is created through 'ERB' templates.

• Low cost hosting solutions exist, e.g. Heroku.

Answer 6

Ruby with no rails? -10 to being fashionable :)

Put "willing to learn rails", better than 'no rails' :)

Answer 7

Recruiters who are calling are tytpically first level screeners. They make calls on a daily basis. Think of them as salesmen. Telling them no means you might be interested. In addition if they are not at a technical scale Ruby and Rails may be synonymous to them.

Tell them politely when they call that you are not familiar with Rails and would prefer to focus in a Ruby only environment; the portion of your resume you listed looks adequate and I would not suggest changing it based on the current issue.

Answer 8

Clarify

You could clarify that you don't have Rails experience by putting "not Rails" at the end. That is if you really don't want any Rails jobs. This has the downside of automatically limiting your options as it indicated you don't know, and have no interest in learning Rails.

Learn

Why not learn Rails? If you really know Ruby well, Rails should be easy. Then you can say Ruby / Rails and open yourself up to more opportunities.