Here's my list as a computer science geek always attempting to look top down at the industry:
- Cloudflare
- Datadog
- GitLab
- DistroKid
- Spotify
- TransferWise
- Typeform
- Okta (maybe)
This being my short list off the top of my head. Hopefully I can edit with some more later.
---
Also, a note that I'm currently hiring:
I lead an international role for AB InBev called Z-Tech which is modernizing the last-mile supply chain for all of AB InBev's massive network of subsidiary suppliers.
That said, I'm attempting to model our engineering practices based on some learnings from the above list of companies.
Feel free to reach out at:
christian.battaglia at ab-inbev dot com
I was impressed, however, to see that your corporate website cookie settings default to maximum privacy!
For those unaware, we're talking about the lack of an SSL cert on our new company website.
Edit: Or did I completely misjudge that as sarcasm?
They have a C++ layer for each client that binds into Android/iOS/macOS/Windows, etc.
And as for audio and their upcoming video hand in hand with Joe Rogan podcast being an exlusive now, the way they operate in guilds/pods is one of the first examples of this democratized workflow.
Great tooling. Great SW development culture. Strict requirements on code quality. Mandatory testing. Mentorship and continuous reviews for writing good code.
1 - you're looking for great software engineering practices to model based on other companies, which is good.
2 - you're looking for a company to work at, and you really value software engineering practices, which is also good.
I feel like these are two different answers though. Many companies that have great practices do them because they are large, and have resources to implement them, think FAANG. It is financially worth it to have great software engineering practices to reduce friction and increase quality. These can be really interesting and have great papers written about their sometimes open sourced technology. The Google SRE program comes to mind.
If you're looking for a company with great software engineering practices to work at, I think that's a lot trickier. It honestly depends on team and culture, and I've found it varies widely, even between different leads. Even at big companies where I've worked, some teams just have bad engineering practices, either due to bad team culture or practical problems like lack of time or resources. Also be careful because a lot of software engineering practices aren't about writing code, committing code, or writing papers about tools and frameworks - they're about personal interactions and problem solving together. Even great software engineering practices can be perverted in a toxic culture.
After the VMWare acquisition, we'll have to wait and see how much of the culture remains.
Usually it's very great but in certain cases people feel like they spin their wheels on projects.
