Bonded by Love for Product
Doppler is a product built for engineers, by engineers.
As developers ourselves, we know firsthand what a pain it is managing environment variables. It’s something we’ve encountered as individual engineers working on side projects and also as devs on larger teams at larger companies. In fact, we faced the issue once more when we first started Doppler, which began as a crypto machine learning marketplace (we know, all the buzzwords in one). Whether it was a silent outage due to using our Stripe staging API key in production (we couldn’t make any transactions) or figuring out how to securely share our API keys with short-term contractors (we didn’t want to give them access to all of our customers’ bank accounts), we realized this was a universal problem for developers without a universal solution.
We love being able to build a product that not only solves problems we face, but also makes development easier for all engineers. In the same way that Figma abstracts away all of the complexities of Photoshop while still maintaining its power, we want to do the same with Doppler for the dev community and their secrets. As we grow from a 5-person company, we hope all of our early engineering hires are as passionate as we are about solving such an omnipresent headache!
Creative + Innovative
We place an extreme focus on the developer.
Most companies who’ve attempted to solve secrets management before built it for the devops and security teams. These tools tend to be overly cumbersome to use and require constant maintenance. We decided to take a different path by building Doppler for developers and placing an emphasis on the user experience. Typically the more secure you build something, the worse the experience is. Working at the intersection of developer productivity and security means you have to get creative. For example, our command line tool login flow begins with a simple command that takes you to the browser so you can authenticate like you would any other website. From a user experience perspective, the user just logged into a site but behind the scenes we created a new token for that user scoped to their machine and placed it securely in the keyring on their computer. This is just one example of how getting creative can lead to a better experience that is also more secure.
Another big advantage is being able to constantly dog food our own product, too! As developers ourselves, we are our own users and get immediate feedback as we build.
Customer Comes First
Our customer is always the individual developer.
We will always prioritize features that individual developers will love over what large enterprises request, even if it leads to less revenue. We are so developer-focused that one might describe it as an obsession! At the end of the day, whether someone is building for a side projector as a part of a team at a 1,000-person company, the day-to-day problems are the same: devs want to be able to put secrets in and get secrets out, and have it be simple and enjoyable to use.
In one of many examples, we prioritized building out custom environments ahead of a long roadmap of enterprise features. We heard time and time again that developers wanted to be able to create custom environments outside of the standard development, staging, and production environments whether it be for CI/CD or sandbox. We know how much flexibility it would bring our users so we built it! We will always put our developers first!
EQ > IQ
It’s incredibly important that everyone we work with feels comfortable saying, “I don’t know.”
We care so much about our team and who we work with that we dedicate nearly 85% of our interview to culture. Our first two phone screens involve zero coding (or silly brain teasers) and focus purely on how you approach problem solving interpersonally. We want to work with folks who will fight for the company to be right rather than being right themselves, and want to invest in high-EQ individuals who will make for great leaders in the long-term. We find that as engineers grow more senior in tech, egos can get in the way, and we actively want to fight against that here at Doppler.
Clear and transparent communication is important to us beyond our company walls, too. Customers also want transparency. People who value and covet IQ tend to be less open to sharing mistakes they make, and we’re the opposite. If we have an outage of some kind, we want to be transparent about how it happened and why it won’t again.
Lastly, we consider EQ as a collective to come from a team with diverse backgrounds. By having people from different walks of life, we will be a more well-rounded, thoughtful, and empathic company. Our team started male-centric, but that is rapidly changing moving forward. Alongside striving for gender balance, we want to work with people who have something unique to share with us. Some of the best people we have worked with in past companies started their careers in unexpected ways with unique twists and turns. Those experiences helped shape who they are and thus what the company became. Join us in shaping Doppler!
Engineers are responsible for breaking down complex ideas into achievable tasks and then rigorously executing.
We are currently a small 5-person company, which means everyone has a tremendous amount of ownership. As we grow, we want engineers to continue weighing in at every stage, from ideation to design. We get feedback from customers often and if we hear the same thing from multiple users in a short period of time, someone typically takes it on and runs with it. One to two weeks later, that feature will be live! Ownership will always be a core part of Doppler’s culture, with a deep affinity towards prioritizing features users deeply need.
High Employee Retention
We hire artists, not assassins.
While it’s true, we’ve had zero churn from the company so far, high employee retention is more about value alignment than anything else. Our goal from day one is to work with people who share our values and understand why we’re building what we’re building on a deeply personal level. We sometimes joke that we’re a home for crazies because security people tend to be disliked at companies for always saying, “No.” However, at Doppler, you are the champion! We have all been that super niche person who pushes back before, but now that we’re a part of a security company, we’re amongst similarly-minded peers.
We should let you know that we’re extremely passionate people. Our first hire, Tom, has a deep seeded passion for security and privacy. (He reads privacy policies the way most people watch Netflix, no joke.) For Tom, it is not a task, but a way of life, and we appreciate how he brings that passion to our team. Ruud joins us from Instagram, where he led their API backend infrastructure. He has built out all of our integrations and focuses on growth at Doppler. His interest and enthusiasm is contagious. As a last example, Ryan owns developer advocacy at Doppler. His excitement for building communities helps us stay connected to and inspired by our users, and we love his talent for distilling information.
We hire artists, not assassins. Assassins will only pull the trigger if they are paid, but artists will happily work for free until the day they die because they love what they do. Thankfully everyone at Doppler is very well compensated but the passion being our main driver remains the same.
High Quality Code Base
We turn OR operations into AND operations.
First and foremost, having a high quality code base enables us to write new code faster. With a lot of the complexities abstracted, we leverage our code in order to develop more quickly. We utilize controllers in our codebase, which allow us to do operations in Doppler, and each controller has baked in permissioning, security, analytics, bug reporting, and other features so we are secure by default.
While there are many advantages to having quality code, it also isn’t a choice for us. We store incredibly sensitive data for customers, so having high quality code is really a necessity for our business. We’ve gone through two penetration tests, conduct rigorous code reviews, ensure all core flows have end to end tests, and use a dedicated staging environment for QA.
Perhaps this is somewhat unique to Doppler, but we don’t have to compromise between speed and quality. We’re a productivity tool that makes you more secure, and generally speaking, if you’re more secure, you’re more productive. By prioritizing reusability, we’re able to turn OR operations into AND operations.
We’re creating a whole new layer (secrets), which opens up endless opportunities.
If you think about GitHub owning the code layer or AWS owning the infrastructure layer, we’re creating an entirely new layer by centralizing all your secrets in one place. Our long-term vision is to own that space between our customers’ code and infrastructure, and we make sure every feature we build today has that perspective in mind.
To give you a sense of what the current landscape looks like, we’ve noticed three big trends that have created a real need for Doppler:
- Growing list of deployments. There are more places where people deploy code than ever before. This is in part due to the adoption of microservices and dedicated hosting environments per use case (ex: Vercel for frontend, Lambda for background jobs, etc).
- Adoption of 3rd-party services. Before you’d built your payments stack inhouse, but now you use Stripe. Same goes for SendGrid and Twilio. The more services used, the more secrets there are to store and manage.
- Microservices. Companies and projects are using microservice architectures more than they ever did before. This leads to more groups of secrets that need to be managed. Your billing service likely won’t use the same variables as your React frontend app.
These three trends are creating a whole slew of new problems for developers. What GitHub did for code, we are doing for secrets. One central place to manage all your secrets across projects and deployment locations.
If any of the above interests you, we’d love to tell you more and encourage you to reach out!