Sign In

Mitchell Hashimoto

Software company with a freemium business model

Mitchell Hashimoto is a prominent figure in the tech industry, best known as the co-founder of HashiCorp, a company he established in 2012 alongside Armon Dadgar. HashiCorp specializes in tools for cloud infrastructure management, including popular products like Vagrant, Terraform, and Vault, which are widely used for automation and deployment in cloud environments.14

Early Life and Education

Hashimoto graduated from the University of Washington, where he met Dadgar while working on a research project. Their collaboration laid the groundwork for HashiCorp's founding.3

Career at HashiCorp

  • Roles: Hashimoto served as CEO from 2012 to 2016 and later took on the role of co-CTO until stepping away from leadership positions in 2021. He transitioned to an individual contributor role before leaving the company entirely in December 2023.245
  • Contributions: He played a crucial role in developing many of HashiCorp's key products, significantly impacting cloud infrastructure practices. Under his leadership, HashiCorp grew rapidly, reaching over 1,500 employees and numerous enterprise customers.45

Departure from HashiCorp

In December 2023, Hashimoto announced his departure from HashiCorp after more than 11 years with the company. His decision was influenced by personal reflections and a desire to spend more time with family. He expressed pride in what he had accomplished and emphasized the importance of building a self-sustaining company that could thrive without his day-to-day involvement.26

Personal Interests

Outside of his professional endeavors, Mitchell Hashimoto is also an FAA-licensed private pilot and enjoys flying various aircraft, including a Cirrus SF50 Vision Jet.5

Overall, Mitchell Hashimoto's legacy at HashiCorp is marked by innovation in cloud technology and a commitment to fostering a vibrant user community around open-source software.

Highlights

Nov 10 · twitter

We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work.

First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs.

Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue).

Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main.

Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown.

The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in.

Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way.").

This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours.

All of this works on mutual trust. It ONLY works with mutual trust.

Everyone at all times has to trust that they've got each others back:

  1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts).

  2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer.

  3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly).

We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago.

In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.

Nov 10 · twitter

This is a good filter for people who I don’t want to work with. Please understand how computers work. This isn’t even about understanding Docker. Any software person should know how the layers work at a high level and this is a VERYYYYY high level.

Related Questions

What inspired Mitchell Hashimoto to start HashiCorp?
What was Mitchell Hashimoto's role at HashiCorp before he left?
How did Mitchell Hashimoto's work on Vagrant influence HashiCorp's products?
What are some of Mitchell Hashimoto's notable achievements at HashiCorp?
What is Mitchell Hashimoto's current project, Ghostty?
Mitchell Hashimoto
Mitchell Hashimoto, photo 1
Mitchell Hashimoto, photo 2
Add to my network

Location

Manhattan Beach, California, United States