In @CalmEngineering we've been experimenting with ways to make our interview process more transparent (without having to rely on, ya know, asking someone you know inside), and now we've extended that to our engineering manager process eng.calm.com/engineering-man…

Writeup from @markthom_as of how we're using engineering working groups to evolve our process and approach eng.calm.com/posts/working-g…

A writeup of our experience using Locust for load testing at Calm from Sai Yerraguntla! (tl;dr - Locust is great.) eng.calm.com/posts/zero-to-l…

Making the world happier and healthier @calm and having fun with #DevOps Checkout out our blog at eng.calm.com/

Great post from @ronakdotpatel on our recent zero-downtime postgres migration medium.com/@ronakdotpatel/rd…

Some background on our experimentation and data culture from @ansonwhitmer ansonwhitmer.com/using-the-s…

If you're looking for an approach to prioritizing work on a data science team, great post from our Dir of Data @ansonwhitmer about the M.I.C.E. prioritization framework ansonwhitmer.com/m-i-c-e-add…

I love how @CalmEngineering have a page describing their interviewing process in detail. What each interview involves, and most importantly what rubric a candidate is being assessed against. eng.calm.com/engineer-interv…