Oddball: Senior Rails Engineer
Oddball believes that the best products are built when engineers understand and value the things they are working on. We value learning and growth and the ability to make a big impact at a small company. Work life balance is important to us, and not something we just pay lip service to. We believe that we can make big changes happen and improve the daily lives of millions of people by bringing quality software to the federal space.
We are looking for an experienced developer to help build improve and build out backend code that interfaces with external systems. As an early hire on a small team, you’ll have a huge stake in what we build and how we work.
Our engineering team is small, distributed, and largely asynchronous. We value a calm, collected environment where you can focus on doing great work. Aside from a couple of weekly check-ins or project updates, you’ll be able to work interruption-free.
You can expect top-of-the-market pay, flexible hours, and a balanced work week. We are a mixed remote and in office team, you’re welcome to work out of our sunny Los Angeles office as much as you’d like.
What you’ll be doing
Working hand in hand with other engineers in developing API endpoints and services that proxy requests to various other applications. Some of these rely on message queues, some are xml, some are json. Day to day work will involve discovery, writing code, developing tests, and debugging. As a senior engineer you will be expected to give input on high level architecture decisions, and communicate those decisions to other developers on the team.
We are looking for someone with the following skill set:
- 4+ years experience in working with Ruby on Rails
- The desire to mentor and improve junior and mid level developers
- Experience with a front end JS framework (like Angular, React, Backbone)
- The ability to write code that is a pleasure for other engineers to read and understand
- The ability to speak and write in terms that non-developers can understand clearly, whether it be in a conference call, blog post or support email