At Calm, as I assume is similar with many consumer tech companies,
experimentation is a way of life. At the time of writing, I’m in the process
of moving Calm away from not only our first in-house experimentation system,
but our first external system. I don’t claim to be a SME in many things, but
when it comes to deprecating old A/B test systems, I’m somewhat of a pro.

In November of 2021 I received a life changing offer to join Calm as a
software engineer. It was a dream come true and immensely exciting, but it
also brought an uneasiness. I was a finance major in undergrad. I went to
business school. I was primarily self taught and worried that people would
find out that I scammed my way in, or I wouldn’t be taken seriously.

Calm’s Search feature is an integral part of our app experience. In 2021, we refreshed our app to accommodate the scale of our ever-expanding content library. With a larger content library, it became more important than ever to provide a world-class Search.

Many of Calm’s most compelling products and ideas come from organic collaboration. We see success when we collaborate across orgs, across experience levels, and across backgrounds. This commitment to openness is where we started talking about working groups.

How exactly do you prepare for a huge spike of new users from a partnership launch?

There’s a lot to keep in mind when it comes to internationalization of a project, but most companies don’t want to think about supporting multiple languages right from the start. In fact, most companies shouldn’t localize right from the start. It’s faster to develop when not thinking about translations.

How do you give your server fine-grained control over your mobile content layout, without losing the benefits of a native experience?