This year, Thyme Care rolled out our new company values, which act as a shared north star for everything that we do. These values, which include acting with our members in mind, moving with purpose, and seeking diverse perspectives, are consistent across departments and functions, including Engineering. As an engineering team we decided that we wanted to add an additional layer of values to:

• Codify behaviors that are more specific to our engineering functions

• Align on norms across teams and engineering functions

• Align on the types of behaviors that we would look for in interviews

After quite a few live discussions, a narrowing down process, and some wordsmithing, we narrowed our list to the most meaningful four, highlighted below

We’re excited to share these externally so that prospective engineers know what kind of team we’ve fostered here and what kind of team they’d be joining.

Our recruiter Sarah Ruth recently reached out to a few of the engineers saying “I love hearing from candidates about the culture of learning. So I understand it better, how do you describe it?” Rather than just replying in Slack, this seemed like a great place to share publicly what we do.

One of the things that we are proudest of within the Thyme Care engineering organization is how learning and mentorship are core parts of our culture. We believe that investing time and energy into upleveling our engineering skills enables us to best solve hard business problems and to build a platform that will grow alongside our business needs.

We sat down with one of our talented Data Scientists, Scott Worland, to talk about his background and what it’s like contributing to the data science and engineering team at Thyme Care.

In our previous post, we talked about why we chose Kubernetes at Thyme Care to deploy and scale our applications. We emphasized the importance of managing the complexity of Kubernetes. In this post, we hope to share just one aspect of how we’re doing that, through the automation of our deploy process.

Are you an engineer interested in working at Thyme Care? Or maybe you’ve already gone through the interview process and are wondering what the next few weeks will look like once you’re on the team. Allow us to introduce you to Laura Jeong, one of our talented Front-End Software Engineers.

Coming by way of Oracle Maxymiser and Warby Parker, Laura is no stranger to the world of startup engineering. Hear from her on how Thyme Care’s team is different and what that looks like during the day-to-day.

When launching Thyme Care, we deployed our MVP to AWS Elastic Beanstalk (EBS). While it helped us hit the ground running, we quickly outgrew this solution. Just three months in, we found ourselves facing slow deployments, jumping through hoops to debug errors, and lacking the ability to implement more advanced configurations. Our plans for the future required a more robust platform – one that was highly observable, general enough for any number of workloads, and able to support our scale well into the future.

Sometimes we want to add some custom data to a third-party library class in Python but obviously can’t change the library itself. Using a simple inheritance pattern along with Python’s *args and **kwargs symbols, we can insert our own metadata into a wrapper class without affecting the underlying implementation.

What does engineering look like at a company that’s connecting patients, caregivers, clinicians, and health plans to effectively coordinate cancer care?

With a background in both finance and healthcare technology, Head of Data Science Alphan Kirayoglu’s current project is building the foundation and technology that will better the cancer journey for patients, their caregivers, and providers. We sat down with him to learn why he joined the company, what’s so special about healthcare technology, and all of the cool things he’s currently working on.

Hello,

This is the engineering blog – welcome!