Rails Test is a productized service run by real human beings.

You want to hire the best candidates for the job, but it's time consuming to set up and conduct technical code challenges that properly test what a developer should know at a specific level (eg. junior, intermediate, or senior).

I created Rails Test to help companies scale their Ruby on Rails hiring process. As a Rails consultant, I've seen the inner workings of numerous companies and have met and worked with Ruby on Rails engineers of all different skillset levels.

We apply this knowledge and design coding challenges that integrate industry-based workflows, such as effectively using git, providing proper communication when appropriate, and writing effective code.

We answer the question: Is this candidate someone whose current level of process and technical efficiency reflective for the position you're hiring?

Rails Test is about solving real problems

Our coding challenges are practical-based and leans heavily into solving real world code with Ruby.

We believe that in order to be an efficient Ruby on Rails engineer, a candidate must be well versed in the conventions of how Ruby is used.

While the use of things like algorithms may be employed in the solution, it is not the focus of our tests. Instead, we ask candidates to build things like a simple API client, a web service endpoint using nothing but Ruby, refactor an existing code with a specific pattern, and other such challenges.

These challenges reflect real-world problems that are solved at businesses which employ Ruby on Rails engineers, and can provide insight into whether candidates can efficiently plan, implement, and document their solutions to such challenges.