Skip to content

Instantly share code, notes, and snippets.

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

@tamalw
tamalw / gist:6514880
Last active December 22, 2015 18:39 — forked from blockjon/gist:6430015
-- Setup some tables.
CREATE TABLE `users` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=1;
CREATE TABLE `internal_messages` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`owner_user_id` int(11) DEFAULT NULL,
#!/usr/bin/ruby
require 'rubygems'
require 'net/http'
require 'hpricot'
class Twitter
def initialize(username, password)
# aldershot.rb
=begin
main file for aldershot mountain.
aldershot mountain is/will be a (currently)
simple chutes and ladders/snakes and
ladder/adders and ladders/moksha patamu/
gyanbazi/leela ripoff.
=end