We pair-program 100% of the time.
While most pairing takes place in-person in our Seattle office, we do have a few remote employees. You won’t be getting a personal computer, but rather using pairing stations to do your work. This ensures that you’ll always be working in an easy-to-use environment that everyone is comfortable with.
Pair programming has a number of benefits, including:
- Higher-quality & less risky code. We trust you and your pair to determine when the work is done. No lengthy approval process needed!
- Mentoring & training built-in to the process.
- No single points of failure.
- More talking. You will more quickly identify blockers and dependencies, and you will likely write clearer, more understandable code for the rest of the team.
There are also social aspects to pairing we like:
- Reinforce healthy work-life balance. If your pair goes home… you should too!
- You will get better at communicating and sharing your ideas
- Bias toward hiring a team with high EQ
EQ > IQ
We aren’t looking for /rockstars/, but team players.
We want folks who can collaborate and listen, just as well as they can deliver. We are building products for Humans, not machines, and being able to work with and listen to each other and our customers is a job requirement. Voom’s problems are about workflows, funnels, and commerce more than they are about algorithms, optimizations, and scale. We believe that not every great engineer went to MIT or Stanford (but that’s great if you did).
We always phrase our stories in ways that make the user-value clear. We want team members who can put themselves in the shoes of the person using our product, and think about what might be best for them… and update our stories as we build.
We work using a GitFlow-like process.
Stories are worked on in branches, and then merged to master when they are ready. Our test suite then runs, including mobile tests. If everything is green, we deploy both the server and mobile apps so we can accept and test our work. This all happens automatically.
We use tools like Heroku, CircleCI, and CodePush to manage our operations. We write our tests with tools like rspec, jasmine, and selenium. Being an international company, we’ve also integrated a translation process (both automated and with human review) into our deployment process.
We deploy to production about twice a week, but that’s a choice by our PMs as to when a feature is ready. Just because we work at Airbus, that doesn’t mean that we can’t use modern software practices and tools!
Our mission is to build something that works for everyone around the world, not just us in North America.
We’re building products for folks around the world. Our challenges are human-centered and operational, rather than purely technical. How can we help you find your helipad in an airport where you don’t speak the language? How can we help you book travel for your whole family in another currency or timezone? We have an empathetic and product-minded team who enjoys focusing on work that can be expressed through interfaces, workflows, and data.
Today, Voom’s product is helping people in some of the world’s most crowded cities fly over ever-increasing traffic via helicopters. It’s a premium product, but it’s the perfect way to learn how people want to fly within an urban environment. We are working with the rest of the Airbus Urban Mobility division to bring new vehicles & ways of flying to our cities. We’ve got a decade-long plan to make flying cars a reality. We’ve got the support of a big company over many years to deliver on our plans.
If you do a job more than 3 times, automate it.
We are a small team who owns a large global product. We all share responsibility for the site’s uptime, and we don’t point fingers. We favor a rigorous test suite over a QA team. We favor self-healing infrastructure over an operations team. We are happy to choose (and pay for) the right tool for the job to be as successful as we can be. If you find yourself repeating the same job, we encourage you to automate it.
We make space for technical tasks in our backlog, and we never let our dependencies get more than a few months out of date. The engineering team always has the responsibility to add technical stories to improve their own efficiency and happiness.
We are not a startup racing the clock.
We are part of a multi-decade plan to change the way we travel through our cities. Unless there’s an operational emergency, working a few extra hours this weekend isn’t worth it. This is a marathon, not a sprint.
We have generous, long term benefits like 401K contributions, continuing education stipends, and parental leave.
We generally work 9:30 to 5:30. Go home when your pair goes home, and stay well rested and healthy.
Committed to Personal Growth
For a small team, we have a generous continuing education budget ($5000/year).
Some members of our team use their stipend to attend conferences, some of us spend it on learning Spanish, while others of us are getting our Pilot’s Licenses. We have a true full-stack attitude that lets folks level up on new topics, all the time, regardless if its related to tech or not.
Everyone at Voom also has the support of Airbus to build their personal brand. We make space for you to spend time at work working on conference presentations and blog posts. We will also pay for travel to conferences you are speaking at.