Customer Comes First
We are so user centric that we’re currently on a first name basis with our users/customers.
We’re passionate about talking to our users and constantly synthesizing what we learn from them. Every week, one engineer rotates into a support shift (during normal business hours) so they can help debug support issues and learn where our customers are getting stuck. This means you’ll put down your normal project for the week and (very likely) dive into different parts of the codebase that you probably have never seen before. At the end of the week, you’ll know exactly what our users think of our product and will be armed with incredible context about what we should work on next.
We are uncomfortable with those who feel comfortable building things without customer feedback. We rarely take our customers requests literally, but when they tell us that something makes them happy, sad, excited, or frustrated, we listen closely and ask the right questions to inform our product roadmap.
We like to work with folks who are excited about making and carrying out their decisions, and who enjoy working outside of their role.
Engineers at Vanta are full stack; they code and architect both the front- and backend of Vanta. Some engineers get on the phone with customers who have agreed to alpha test a new feature and give feedback, others are drawn to dev-ops and build out our infrastructure and monitoring, while others work closely with support and product to define the requirements of a new feature.
Being multifaceted is incredibly important to us because we work on the highest-priority issues, and the highest-priority thing isn’t restricted to a single part of the tech stack. Having exposure across technologies and departments suits folks who enjoy going broad rather than deep, as well as anyone interested in founding a company someday.
If you’re an engineer curious about sales, you’ll be shadowing sales calls and helping us understand our customers; if you’re an engineer who loves design, we’ve got loads of product surface for you. If you’re interested in building a company, you’ll be on the interview loop (with training!) for a role you’ve never interviewed for before. Everyone contributes to the product and the business, and our goal is to empower everyone at the company to work outside of their job title.
Bonded by Love for Product
We value our craft, but we focus on impact.
Today, consumers rely on software for everything from banking to hailing a taxi, and with that reliance comes a trusting relationship. As internet services store increasingly sensitive data about their customers, it’s even more important than ever that companies store and use that data properly.
We all love playing with the latest technology, but we recognize that it’s in service of our greater mission. Focusing on impact allows us to zoom out, decide what we truly value, and have a common language to discuss our roadmap and product.
We’ve built some really cool technology and we put intentional time toward developer tooling and battling tech debt, but it’s with an eye toward making us more productive. This isn’t the sort of company where an engineer will insist that we rewrite our entire codebase in Scala – we look to our product goals and work backwards.
Team is Diverse
Our backgrounds are varied, our values are shared.
We believe that the strongest teams are diverse in their backgrounds, interests, and perspectives. This belief has guided our hiring philosophy, and will continue to be a pillar as we grow. We also know hiring is only one piece of the puzzle, and have prioritized creating an inclusive workplace to continue to foster diversity – both in our physical workspace and with how we empower, enable, and encourage our team.
To us, diversity includes traditionally underrepresented groups in tech, as well as professional and academic backgrounds. One of our engineers has a PhD in Japanese literature (TripleByte even did a story on him), and among the computer scientists you may bump into actual scientists and near-film-majors (it’s a sore subject, but we’re glad he ended up focusing on CS!)
We have all arrived at the same place because of the mission of this company. We love working together, and diversity is our strength.
We believe if we give everyone the information needed to make important decisions, everyone will be empowered to make important decisions.
We send out notes from every Vanta meeting, including co-founder Erik Goldman and CEO Christina Cacioppo’s weekly syncs, and encourage others to drop in or follow up with questions. This isn’t just out of convenience: we believe that every member of Vanta should feel like they can contribute to what they’re passionate about, and that starts with shared context.
Success for us means giving everyone a common language, an understanding of our company’s challenges and opportunities, and information about each others’ roles. We believe transparency is the most powerful way to equip our team members and scale decision making.
Upfront work to validate a hypothesis is always the right investment, and we’re rigorous about what we know and what we’re less certain about.
It’s easy to change a spec, it’s a bit tougher to change a design mock, even harder to change code, and a major project to modify a feature that our customers are already using. We ship quickly, but we’re always doing user research so when we start a new project it’s with a strong hypothesis about what’s wrong and how we can fix it.
We spent almost a year learning about security and validating the product, market, business, and product need upfront, all without code. Now we’re net profitable with incredible revenue growth and a strong mission to work toward, so we’re glad we didn’t rush things.
We’re very Richard Hamming about things: “A random walk of random decisions will not get you anywhere near as far as those taken with your own vision of what your future should be.” If this resonates with you, we’d love to meet you.