UserTesting is a large panel of people who test website and mobile applications. Let's say you own SomeTravelSite.com, and you'd like UserTesting to test how Donna, a fictional woman earning $X per year, would use your site to plan a vacation 6 weeks from now. You ask UserTesting to have 10 people like Donna run this test. UserTesting finds 10 Donnas, and within minutes you've received 10 videos. In each video, you are watching a screen recording of a Donna booking a vacation on SomeTravelSite.com, including an audio narration of what she's thinking at each step in the process.
As a company, we're doing well! Since 2010, revenue has doubled every year, we've grown from less than 15 to over 100 people. Sales have been strong enough to fund UserTesting's growth, and we've got plenty of cash in the bank. Investors who see how well we're doing are asking to invest in us.
We, the Engineering Team, would like to hire an experienced back end developer with strengths in Ruby on Rails. As UserTesting grows, our team is starting to feel the need to build services, remove performance bottle necks, build distributed systems, etc. We're bumping into challenges that would benefit from an experienced back end developer with the wisdom that comes from having "been there, done that".
Technologies we currently use
Ruby 1.9.3, Rails 3.2.X, MySQL, Redis, Sidekiq, RSpec, Git, Capistrano, Haml
Proficiency w/ Ruby, Ruby on Rails, and relational databases
Passion for scaling web application
Experience w/ Agile methods, such as Scrum & Kanban
Ability to work onsite at our office.
Areas in which we need your help
Building web services. For example, within the bowels of our Rails app a distribution system routes user tests to testers. The distribution system is tightly coupled to many things in a way that is hard to maintain. We'd love to break the system off from the main app, build an isolated service, and give it an API. The distribution system is so important, we may even build a team just for it.
Instilling the knowledge of application security in others. Our most junior developer isn't the one we want leading an effort to make sure private stuff stays private. Could you teach Most Junior Developer to write secure code?
Building a REST API that's actually using RESTful. Maybe we write RESTful APIs. Maybe we're just sending JSON over HTTP. We'd love to have a REST guru who can tell the difference. Could you write a REST API that makes Roy Fielding say "That's totally what I had in mind!"?
What we offer
Competitive compensation and company equity
IRA plan with matching contributions
Paid vacation and company holidays
Gym membership reimbursement
Paid time off to work at a charity or non-profit of your choice
A fun place to work with a great team of people!