Well, we have a pretty high bar and a great team. The job descriptions on-line are broad on purpose. I have been doing allot interviews and code screenings lately and (with Troy’s help) have decided to explicitly publish five specific minimum bars that we apply during the screening process. If you want to work at Kashless.org as a Ruby Dev, here is what you will need to have done/do to make the cut.
The whole Rails stack (2.2/2.3+) – unless you can point to a Rails app you have been responsible for building from top to bottom chances are you don’t have enough experience
GitHub and git - you have an account, you've forked and sent pull requests, hopefully they've been accepted.
You test. A lot. Preferably with shoulda.
Stuff that evolves from operating a large Web app -- full-text search (Sphinx, Solr), async job queues (ActiveMQ, delayed_job), DB sanity (foreign key enforcement, migration)
Consumed enough APIs to explain the ones you've liked and the ones that were just endless frustration
Pluses: Happily spent an entire day ‘building a slice’. Don't need to ask what EBS means or how AWS probably implemented it. Done role-based capistrano deployment. Geocoded a million rows.
Go ahead, apply, it is fun http://kashless.org/home/jobs
or direct to the Ruby job http://kashless.catchthebest.com/apply/6398/
Recent Comments