63

What should someone know as an Entry Level, Mid-level, and Senior Developer working with Rails? Across the board: theoretical knowledge, development tools, gems and more. What issues usually are at the interview?

temporary_user_name
  • 35,956
  • 47
  • 141
  • 220
akrisanov
  • 3,212
  • 6
  • 33
  • 56

5 Answers5

140

Senior

  • Analyse and profile an application for performance and memory issues
  • Analyses and profile an application for security issues
  • Understand database modeling and query analysis
  • Tune a production deployment (Passenger, Thin, Apache etc)
  • Understand and use Ruby metaprogramming
  • Mentoring skills
  • Communication skills
  • Planning and Estimation

Mid-level

  • Setup and deploy a Rails App for production
  • Understand the Rails stack - callbacks, filters, plugins, engines, gems, rack
  • Understand and use Active Record associations
  • Understand and use scopes to define model abstractions
  • Define tests using Cucumber and rSpec
  • Understand and use Object Orientation
  • Understand and use Design Patterns (explain what they are, know some basic patterns)

Entry Level

  • Create and setup a Rails environment
  • Use generators to create models, controllers and migrations
  • Create and use a migration to manage the database
  • Create a unit test using rspec/etc
  • Create a model and basic validations
  • Handle a GET request using a Controller, Model, and View
  • Handle a POST request using a Controller, Model, and View
  • Basic HTML, CSS and JavaScript
  • Basic GIT - clone, commit, push
Toby Hede
  • 36,755
  • 28
  • 133
  • 162
  • 1
    This is a very good list, I would add model validation to the Entry Level or Mid-Level sections. I've found that writing validations first when creating a resource helps you think critically about your application and its data early in the development process. – Patrick Klingemann Apr 03 '10 at 02:24
  • 3
    Thats a pretty damn good list for anyone regardless of language. Understand your application stack. Understand the build system. Understand your test tools. Understand profiling tools. Etc. However I would recommend scrapping CSS and going straight for SASS. The power of sass is so great that while its still CSS, its like assembly vs c really. – Dmitriy Likhten May 12 '11 at 04:28
12

I wrote down some questions and answers that I have experienced from my interviews and some additional logic questions that you might find useful.

Here it is: http://anilpunjabi.tumblr.com/post/25948339235/ruby-and-rails-interview-questions-and-answers

Enjoy !!!

Anil
  • 49
  • 2
  • 6
1

I think for the seniority level you should be able to answer most of the following questions:

Here is my blog link.

AnkitG
  • 6,438
  • 7
  • 44
  • 72
0

How to setup and deploy Rails apps to production environment

Joshua Partogi
  • 16,167
  • 14
  • 53
  • 75
0

Understand ruby blocks and iterators for traversing and manipulating datasets.

scaney
  • 1,746
  • 13
  • 16