Shop Alto Essentials to add pharmacy products to any delivery!

Your partner in navigating the ins and outs of prescriptions — at no extra cost.

Alto Pharmacy Technician

Alto Pharmacist

It’s official: Alto Pharmacy is a great place to work! We’re honored to join the community of Great Place to Work-Certified™ companies based on team member feedback and a rigorous assessment of our company’s culture and benefits.

Join us in delivering our industry-leading pharmacy care to millions of people across the country. As a member of the team, you’ll play an integral role in improving our customers’ quality of life and redefining what’s possible in pharmacy. 

Be Part of a Great Place to Work — Join Our Team

Hear first-hand from members of the Alto technology teams.

Read the latest Alto blog posts covering healthcare, family health, managing diseases, and other Alto highlights.

Blog | Alto Pharmacy

We are building a pharmacy where every patient matters and is included. To do that, we need to foster a culture and company that is committed to challenging existing racism, injustice and prejudice, in order to create a culture and service that is inclusive. 

Diversity At Alto: Building an Inclusive Healthcare Company and Culture

At Alto, we are redefining the pharmacy experience which has been part of a very old, broken way that has fueled systemic racism. We are building a pharmacy where every patient matters and is included. To do that, we need to foster a culture and company that is committed to challenging existing racism, injustice and prejudice, in order to create a culture and service that is inclusive.  Our team consists of committed and passionate individuals who champion to effect positive change on issues related to race, injustice and prejudice.

This passion for equality is what we strived for when we first set out to build a team with a broad representation of diversity. Our goal was to create a community that reflects an inclusive culture regardless of age, education, gender, race, ethnicity, religion, sexual orientation, socio-economic status, or other dimensions of diversity. Yet even with the best of intentions we recognize that there is more work to be done to dismantle the systems and structures that fuel racism and inequity.

2020 has been a year like none other for so many.  HR professionals around the globe have stepped center stage to support our organizations, teams and communities in ways many of us could not imagine.  I wanted to write this post to share my personal journey on this topic while supporting others in capturing this moment.  I am a white gay cis man.  Many of my identities provide much privilege.  I am committed to educating myself. I am building an environment where our teams can push past their fears to learn and grow.

Read more about Why We Prioritize Diversity at Alto.  

In 2019 we initiated our focused DEI (Diversity Equity Inclusion) work with the goal of ensuring employees felt safe, and included, and ensuring that candidates and employees have equal access to opportunity for advancement in the organization. We learned a few things during the early days of this work including balancing listening while creating the right structure to move to action.  Fast forward to early 2020, in the midst of the global COVID-19 pandemic and the murder of Ahmaud Arbery, Breonna Taylor, Tony McDade, George Floyd, and Jacob Blake, we like many other organizations did not want another moment for action to pass by.

Read more about Alto’s Mission and Values. 

The week after George Floyd’s murder we hosted a series of listening sessions for Altoids.  We began them with a simple statement:  “We are holding this space for you.  Tell us how you are feeling.  Share your experiences.” The results were powerful moments of revelation, pain and heartbreak.  Black, Asian, Native and Latinx Altoids shared experiences of racism, sexism, and prejudice in their lives.  As a leadership team, we started to wake up to the enormity and urgency of the work we had ahead of us.

In reflecting on these tragic murders and Altoid voices, we realized we needed to expand the building blocks of our 2020/2021 DEI strategy. We recognized that we didn’t want to rely on the members of our underrepresented communities to lead us on this journey.  We do not expect underrepresented professionals to teach us, especially cis white men, about the history and experiences that led us to this moment. 

We made the decision to find a partner to help.  What struck me about Pathfinder and Trier Bryant, is their ability to push our thinking on this critical work while meeting us where we are (each one of us). Trier is a strategic leader with distinctive Tech, Wall Street, and military experience spanning across 15 years. Pathfinder has an unwavering commitment to advise leaders on how to create a more equitable, inclusive, and thriving culture to produce prosperous companies. I appreciate many aspects of Trier’s support including that she too is a Chief People Officer, she wears these shoes.  Given that experience plus Pathfinder’s work with clients like Equinox, Compass, SoundCloud, Gusto, and eBay, we gain perspective and lessons learned.

Our first half-day session with Trier focused on educating the group about the language of diversity (e.g. Is it okay to say Black? What makes up the LGBTQIA+ community?).  Next we spent time learning about key historical events starting from 1619 that have shaped our current society with respect to race, oppression, and white supremacy in America.  We watched videos displaying more covert forms of white supremacy [see Ellen Tuzzelo’s Pyramid of White Supremacy]. 

These are actions I could recognize in myself (i.e. not challenging racist jokes when told by my family members, not always believing the stories of Black victims).  I felt sadness and shame. Sharing these feelings and our part in the current state of our nation is an important step. We took time to process and walked away with an epiphany.  

Over the past decades, America and specifically Corporate America lulled itself into thinking that we’ve been fighting bias.  Our aim up until this moment was to reduce or eliminate bias.  We were wrong.   Our fight, our work is to eliminate racism and white supremacy in America. This work is neither a marathon nor a sprint; we’re committed to doing this work all our lives.   

With that realization in mind we got more specific about what diversity meant to us and where we wanted to focus our teams at Alto. Diversity by nature is very broad and inclusive. We used individual characteristics, experiences, and abilities consistent with our values and mission that includes but is not limited to:

*Sexual Orientation and language abilities will begin to be captured with Workday, our new HR system.

As a part of the above education, we learned that while we all have various identities and intersections that represent our Altoids, intersectionality is a term that must be clearly understood to comprehend unique modes of discrimination and privilege that occur in the workplace.  

Identity - the fact of being who or what a person is; affinity (i.e. Hispanic/Latinx, Black, Male, Female, Nonbinary) 

Intersections - a point at which two or more identities  intersect (i.e. Hispanic/Latinx Gay Male, Black Heterosexual Female)

Intersectionality -  the cumulative way in which the effects of multiple forms of self-identifications intersect, overlap, or combine to create unique modes of discrimination and privilege; intersectionality identifies advantages and disadvantages that are felt by people due to a combination of factors

While Alto recognizes a broad and inclusive definition for diversity of various identities, there are strategic priorities for underrepresented groups at the company. After benchmarking current tech and health care demographics, we decided to focus our DEI work for Altoids including our leadership, managers and independent contractors on the following underrepresented groups at Alto: 

Women in STEM (Science Technology Engineering Math)

The following month we read So You Want to Talk about Race by Ijeoma Oluo. What an incredible read! This engaged us in thinking about and naming our privilege.  In the next half-day session with Trier, we discussed the book to name our privilege and explored how it influenced our personal and professional development.  

We learned several lessons from Ijeoma and Trier including that we’re going to make mistakes and say the wrong thing; that is part of the journey yet we still must do the work.  Also that microaggressions are as damaging as overt racism and we must do better at calling these detrimental behaviors out everyday. 

Lastly, non-white people fear retaliation most when the topic of racism and prejudice comes up; we must create a space for everyone’s voices and perspectives to not only be heard but respected.

As I reflected on our second half-day session together, I saw the journey for our leadership team through four stages.

Stage 1: Self-Awareness-doing the personal work regarding racism and privilege

Stage 2: Awakening-acknowledgement of role of racism, privilege, and gressions,; doing the work in our professional life

Stage 3: Empowering-identifying the work to be done with our team, team members and building more inclusion on our teams

Stage 4: Advocating-taking our roles as a senior leaders at Alto to change behaviors and lead change at the company and our communities 

For the last round of workshops we split up our senior leaders into smaller groups so that we could focus on the work needed to be done with each of their teams.  In these sessions, we learned more about identities.  How do we identify?  What do we learn and acknowledge about our team members identities?  We discussed specific examples of how intersectionality shows up in the workplace and the role it places in each other’s experiences.  This pivot allowed us to move into Stage 3.

As we embarked on taking this work to our team, we felt more prepared and comfortable because of the time spent educating, processing and doing our own work ahead of time. This allowed each of us to live one of our core values “start with empathy.” Being empathetic is hard when you haven’t done your own work.

As a result of all the foundational work we’d done as individuals, as a team and as a company, in July, our leadership team committed to a bolder, crisper DEI plan that includes four strategies with clear goals:

Hire - ensure we have diverse teams and insure all are valued

Include - increase inclusion and community 

Develop - educate our leadership team and all Altoids

Invest - support initiatives with money and time  

This new DEI plan rallied the team and catalyzed us to make some significant changes with clear alignment, commitment and clarity around the problem we’re trying to solve. For example, one immediate change we made was to focus our executive search process on underrepresented talent. I’m excited to share that only a few months later (most searches take 6 months), we were able to hire several outstanding candidates from underrepresented backgrounds. 

Before, we had just been “hoping” for diversity and thus looking in all the wrong places.  Once hiring diverse talent  at the executive level became a critical mandate, that forced us to really seek the right kind of strategy. I’m excited to share some more of the significant changes we’ve made, over a series of posts over the next few months.

We are far from perfect.  We have work to do to meet our goals.  These are our first steps.

In January, we will share our first DEI Report including workforce demographics, success stories, lessons learned from 2020, and aspirational goals for 2021 and beyond.

We condemn the violence and systemic racism that has harmed marginalized communities, specifically Black communities, for far too long. At the same time, we commit to look inward and educate ourselves to continue to create safe spaces for Altoids and to act on what we learn. 

This will be a lifelong journey and we will continue to share updates on our progress. Our actions must be sustained and focused on keeping the momentum of enabling change now and for future generations. 

Last, personally this work is the most fulfilling of my career. There are days I am exhausted.  There are days I need help.  Yet there are many days I overflow with pride in our team.  I am most hopeful about the work ahead and seeing the early fruits of this work while challenging us each day to do more.

Mike McClay has spent the better part of two decades working in Silicon Valley. Here, he chats with software engineer Akash Gupta about the road from Software Engineer to VP, what it’s like to work in digital health, and his best advice to both independent contributors (ICs) and managers. 

Get to Know Alto’s VP of Engineering, Mike McClay

I'd love to first understand a bit about you personally. What do you like to do in your off time? What’s something most people don't know about you?

I grew up in Orange County, which is pretty suburban, so that afforded us a lot of time outdoors as a family. A life goal of mine is to do a solo hike of the John Muir Trail. The route starts in Yosemite Valley and heads south to Mt. Whitney. It’s about 225 miles and typically takes a few weeks to complete.

Currently though, I have a two-year-old and a four-year-old, and we have another baby on the way, so my outdoor activities tend to be much shorter and closer to home. I got into road biking about 10 years ago and transitioned to mountain biking a few years back when my family moved to Marin. Being able to get out onto the local trails a couple times per week is an amazing opportunity to get a great workout in, and unplugging does wonders.

Finally, a ton of family time with my partner and kids. A big reason I decided to join Alto is because it provides a great balance of simultaneously being a high growth startup but it’s also a company that has an eye on culture and achieving work-life balance. At Alto, we're playing to win, and we’ve got a lot of things to get done, but there's a lot of support and representation for people with families with kids. It's nice to be able to work hard towards an incredible mission but also not have to sacrifice too much on the family front; so outside of work, I’m mostly focused on spending quality time with my family getting outdoors, getting to the beach, and things like that.

That's very exciting, having another child on the way. How has COVID-19 impacted your responsibilities of being a VP Engineering and a father?

Life is a lot harder during COVID, though I say that with a fair amount of awareness of the privilege my family and I have. On the home front, we are constantly trying to find that balance of keeping the kids entertained and learning but also doing it in a safe way that protects everyone. My wife and I are pretty fastidious about keeping the house organized and clean but that’s relaxed quite a bit during this time; there’s a lot of resetting of expectations, and I try to do as much as I can to support my wife.

Professionally, probably about half of our engineering team has interviewed and onboarded since the shift to remote work in March, and I’d say we are still iterating and adapting each month to work better in a fully remote environment. It’s been incredible to see our teams adapt to this new style of work, and while it’s not quite the same as our in-person environment was, it’s been really cool to see the team grow and have our organization make a bigger and bigger impact for our patients each month.

I'd love to talk about some of your past experiences. You went to the University of California, Berkeley (Go Bears!), then Expedia, then Uber, and now you're at Alto. What prompted each of those transitions?

Yeah, I’m kind of an outlier in the tech world in that I’ve only worked at 3 companies since graduating undergrad in 2004. I think I’ve been fortunate to find myself at companies that have had no shortage of growth opportunities and that led me to stay for considerable amounts of time at both Expedia and Uber. 

Towards the tail end of my tenure at Expedia, I was managing the engineering team of a start-up that Expedia had acquired, and I knew in my heart that I wanted to move to a much smaller company. I spent a few months talking to a bunch of early stage start-ups but hadn’t found anything that felt right yet.

At the urging of my recruiter, I took a call with a company called Uber, which had seemed way too “big” for what I was looking for in that the engineering team was about forty people. Despite the role feeling different from what I was expecting, I was excited by the mission and the team, so I made the leap. Fast forward six years or so and it was an amazing ride, full of a lot of ups and definitely some learnings, but it was a truly formative experience for me.

Uber ultimately got to a point where I struggled a bit to pinpoint the impact I was making, and things overall at the company just felt slow. I wanted to work on something that was even more mission-driven, and one of my colleagues insisted that I chat with Alto. I was introduced to Jamie (Alto’s CTO). We talked over a number of months and found Alto’s needs and the challenges I was looking to solve aligned in a great way. So that's why I ended up joining.

Each of the companies that you’ve worked at have had large operational components. What are some of the key pieces to creating a strong partnership in a tech-enabled company?

What I would definitely say is that the tooling and the product that we built for ops at Uber was, at the time, world-class; it was just beautiful. Design was a first class citizen in our operational tooling because the workflow of our ops team was so critical to our company’s success. 

This is something that Jamie and I bonded over about Alto; our internal platform (called Wunderbar) powers the functionality that allows us to process our patient’s prescriptions in an efficient and effective way. Getting this right is critical for our patients, and the fact that we put so much time and energy into getting the technology platform right goes a long way to build a great working relationship with our operations team. 

Additionally, I’m passionate in general about operations since it’s often an area of the business that creates strategic advantages over competitors. And what I love about building software with operations is that it can’t be copied easily by competitors since there is no public surface area to observe. I view our task as an engineering team as getting to where we're crushing it as a business because we have nailed supporting operations with our product engineering work.

On that note, would you say Alto is an operations company, a pharmacy, or a tech company?

We aspire to a model of cross-functional leadership, whether it's between Engineering, Product, Ops, Growth, Marketing—whatever it is, the leads of areas and even the team members of each area need to be empowered to achieve the mission that they're setting out to do. If that's to enable, say, the flow of prescriptions coming through our system, maybe you could call that Ops-led, but at the end of the day, multiple functions have to come together to solve the problem. I almost want to call it vision-led.

There’s a time and a place where we need to be creating a faster horse, and there's a time and a place where we need to be thinking one to two years out about what the step up is from the faster horse: bringing the car into the situation, so to speak. Ultimately we need to be thinking on multiple time horizons at the company, and depending on the time and place and the strategy, you might see one function spiking up in terms of what we're rallying around versus another.

The engineering team at Alto has grown from eleven engineers and four managers when you started a year ago to more than fifty-five engineers with nine managers, directors, senior managers, and managers. What would you say has enabled that dramatic growth, and how do you plan on ensuring that that growth is well-managed?

For engineers, there are a lot of choices out there, and a big part of our hiring process is spent not only assessing technical skills, but also looking for signals that candidates align well with our patient-focused mission. From the beginning, we created an interview process that is fair and equitable, and that resonates strongly with our candidates. From there, we set out some really big goals that energized the team to push to make it happen.

I'm really proud that we've grown while maintaining a solid level-mix in terms of junior, mid-level, and senior engineers. Our engineering team is ~25% female, and while we only have single digit percentage points of representation of other underrepresented groups, representation is improving every quarter. Our goal over the next several years is for the team to achieve 50% gender representation and 30% from other underrepresented groups, so that our engineering team is representative of those we ultimately serve: our patients.

In order to make sure this growth is well managed, my philosophy is to hire or grow Engineering Managers well in advance of the acute need. On the manager side—and this was a big learning for everyone at Uber—we’d grow a team of fifteen to twenty engineers under a manager and not really have a great plan in place for how to bring in additional leadership and get the teams down to a right size of ten. When we approached that number, we'd battlefield promote someone and everything just felt strained. So I'm really proud of the fact that even at nearly seventy people now, we have a management team of nine that could actually support one hundred people pretty well. As the team continues to grow we’ll be making sure to stay ahead of the growth on the management side.

On that note, Uber has been reported to have an unhealthy culture. What have you learned from it to engender a more positive, inclusive culture at Alto?

Yeah, I’ve had a lot of reflection on this and a lot of learnings from my time at Uber. First, it’s that as a leadership team, we need to be vigilant about creating a team environment where team members feel they can do their best work. We need to always have great managers leading teams that are right-sized, and we need to have people-focused cultural values that help guide our behaviors and how we interact with one another. 

At Alto, half of our cultural values are focused on skills that foster an environment where folks can do their best work. Yes, we're thinking constantly about impact, but we make sure to hold ourselves to a high interpersonal bar. This type of behavior has also been institutionalized at Alto in our engineering career ladder. Culture amplification is one of the five skills engineers are evaluated against, and I think it’s a very strong signal into what we hold dear and how we want to roll here.

Finally, I’ve put a strong emphasis on making sure that interviews at Alto assess behavioral skills in addition to technical ones. We didn’t do this well at Uber for too many years, and I believe it led to some of the cultural negatives that you’ve likely read about in the news. To me, it’s critical that we hire really talented folks who can work seamlessly with one another. Getting signal on this during our interview process is a big part of growing a healthy engineering organization.

You've gone from being a Software Engineer to Tech Lead, Engineering Manager, Director, and now, VP. What advice would you give someone at each of those stages? What advice do you wish you had back then?

The main piece of advice I’d relay is to make sure that you spend enough time in each role to get solid proficiency. I’ve come across a number of folks in my career who look to move through roles as quickly as possible, and I think that doesn't allow for solid bases of knowledge to be built up. The foundation I built up in my experience as an engineer I believe resonates with engineers; I’m not just a people manager that helps coordinate minutiae. Additionally, a lot of the skill-building in these roles happens as you encounter various real life situations; the only way to accumulate experience is over time. So my advice is to be patient.

I would definitely encourage everyone to work at a company where there are clear career paths for both ICs and managers. You should never feel like you need to move into management to “grow in your career.” One of the first things we put in place after I joined Alto was a career ladder so that folks could reason about how they wanted to grow over time and come up with a growth plan with their managers.

Finally, don’t go too long in a role or at a company where you don’t feel challenged and don’t feel like you are growing. To me, growth and challenge are proxies for job satisfaction. I would say I've achieved it about 80 to 90% of the time in my career. If you're not in a place where you're feeling like you're growing, you should go somewhere else.

What would you say to someone considering working in digital health? What are some challenges and benefits in this space?

It's not so fraught with red tape that you can’t get anything done. There is a process to work through with HIPAA (Health Insurance Portability and Accountability Act) to ensure patient privacy; there is a massive set of opportunities that support all of the activity in the space; and there are seams where startups can begin disrupting entrenched players.

There’s also a massive opportunity to solve hard technical problems while achieving these amazing, mission-driven ends. I think sometimes it seems that those can be separated to where it’s almost mutually exclusive. While we don't yet have the volume nor traffic that you might receive at companies like Uber or Google, there are still meaty technical challenges that haven’t been solved before.

What disruption is good in healthcare and what may not be?

The good disruption comes in places where companies can plug into an existing experience that patients go through to solve a problem and figure out new ways to address that problem. In the pharmacy space, we are disrupting the brick and mortar pharmacy experience that is effectively in the business of selling you Coca-Cola while you wait for your medication. 

Bad disruption would be anything that goes against protecting a patient or their privacy. At Alto the engineering and security teams are tightly coupled so that we can best solve for the needs and privacy of our patients.

You mentioned technical challenges. What would engineers and other technical people get excited about in this space?

We don't yet have our architecture mapped out for scaling 100x on our business over the next couple of years, and it’s been really exciting to start to discuss our technical plans to enable that. At Uber, we went from a monolith to a full micro SOA (Service-Oriented Architecture)—both extremes that had quite a few problems as implemented. At Alto, we aim to find a better middle ground. 

Additionally, we need to think about what the pharmacy experience will look like five to ten years from now and start building some of the pieces that will work us toward that future. Safety and accuracy are incredibly important to us now, but at one hundred times our scale, we’ll need to be constantly innovating our technology so that we can minimize / eliminate errors in our operational process. 

We’re also bringing data silos together that have never been joined before. For example, as many as 50% of prescriptions are not picked up for retail pharmacies. Doctors have no idea which of their patients pick up medications or not. Insurers don't know what happens to patients after they take their medication. We are the interconnect between all of these customers.

As we grow, that data is going to grow inside of our systems. The information and the insights that we can derive from it is going to be incredibly powerful. But we're going to need a ton of awesome data analysis, products that allow us to collect the data while respecting patient privacy, etc. I'm really excited about that.

What are you most proud of from your time at Alto so far, and what are you most excited about in the next year?

What I'm most proud of is the team that's been hired. They are just amazing. Last year, we had a team of eleven engineers with such a large surface area: fulfillment, operations, customer app, customer website, our provider portal, etc. With so much to do across a team of that size, we were constantly making really hard prioritization decisions and were not able to tap into what we saw as our full potential.

Fast forward to today, we're now in a world where we have dedicated teams for surface areas, and we’re solidly parallelizing efforts. Seeing the bandwidth, the throughput that's going to be rolling out each quarter, is really cool. We're going to have orders of magnitude more output each quarter than we did a year ago. That's what I'm most proud of now.

What am I most excited about? There's the business aspect, expansion. We've really only covered six markets and are now looking at covering many, many more lives. The next couple of years are going to be a lot of fun.

Last question. Someone's considering working at Alto: Why should or shouldn't they join?

Alto’s at a stage where things are changing constantly. Folks who like dynamic environments will thrive here, as the work is challenging, and we are trying to solve problems that have not been solved before. Given that Alto operates within a multi-sided network, we have a lot of opportunity to create value, but it also means there are multiple players to think about when building a product. There's a richness to our patient, provider, and insurer base that makes it both challenging and exciting to make sure that we're finding the opportunities that deliver value to broad strokes of folks without leaving others behind.

Finally, engineers should join if they want to be part of a mission-driven company, enjoy working in an inclusive environment and diverse team, and like to be at the intersection of technology and the physical world, whether that's operations, delivery of things to humans, etc. If we succeed,  the way society thinks about health, prescriptions, etc, ten to twenty years from now will look very different because of the work we’re doing here. If that's inspiring to you, and you want to be part of that, you should join.

Interested in joining the team? Reach out to us on LinkedIn.

In honor of National Coming Out day our Proud Employee Resource Group sat down with Altoid Nicholas Satow, Partnerships Manager HIV/PreP, to learn about his own personal experience and his advice for others on coming out.

Coming Out with Pride: Nicholas Satow Shares His Story

The month of June marks Pride, a time to recognize and support lesbian, gay, bisexual, queer, and transexual individuals. In honor of this awareness month, our PROUD Employee Resource Group* sat down with Nicholas Satow, Partnerships Manager HIV/PrEP, to learn about his own personal experience and his advice for others on coming out. 

Tell us a little about your coming out experience. When did it happen and who did you first tell? 

My coming out story starts with the story of my best friend. We met in third grade and were just 15-years-old when she came out to me. She was a star basketball player and met a girl from an opposing high school team 45 miles away. We quickly turned 16, and without our parents’ knowledge, we were driving 90 miles round trip every weekend to go see her girlfriend and hang out with a group of kids who didn’t know anyone from our school district. The 45 miles of distance made her feel safe from our friends and family finding out about her double life.

Leading a double life and constantly hiding our whereabouts started to wear on us. Especially for her after family and friends started becoming suspicious. Who is this girl you’re always on the phone with? Why are there so many miles on your car? Where are you going? Her fear of being outed or disowned started to build as rumors began to circulate between friends and family.

It was a Saturday night, and we were halfway through our 45 mile drive home. She broke down in tears and started to share terrifying thoughts she’d been having. She said she couldn’t take the pressure of the double life anymore and the rumors circulating at school. She felt extremely overwhelmed, isolated, and scared. Thoughts of teenage suicide and stories I had heard of queer teens taking their own lives started to consume my mind. 

Even though I wasn’t ready to come out of the closet yet, I knew in that moment my friend needed me more than ever. I felt responsible for her loneliness and selfish for making her go through this journey alone. She said, “I can’t take this anymore. I can’t live like this,” Staring at the road ahead, I said, “You need to stay strong. You make me strong.” I turned and looked at her and said, “I’m gay, too.” This was the first time I said those words out loud. It was terrifying and relieving at the same time. It was the first time I felt authentically me. 

It’s 15+ years later, and we’ve helped each other get through many scary thoughts and tough times, come out of the closet to friends and family (sometimes while sitting side-by-side) and navigate difficult romantic relationships as we learned what it was like to be a young gay person in Cleveland, Ohio.

How did you feel as a result of coming out? 

After coming out to my best friend, I felt a sense of relief and companionship. Our double lives became more of a shared experience and a lot easier to manage, knowing we had each other to rely on. I also started to feel more comfortable coming out to other friends. At 18, I came out to all my friends. At 22, I came out to my parents and family.

What resources, support groups, or communities did you rely on when coming out? 

At the time, I wasn’t aware of any resources or support groups, so this wasn’t something I utilized. Another best friend’s older brother was gay, so I learned a lot from him, and he took me out to introduce me to the community and become comfortable in my own skin.

The best advice I’d give to LGBTQIA+ youth is to find a support system of like-minded individuals and come out when you feel it’s safe to do so. If you’re in an environment where you feel your mental or physical safety could be jeopardized, don’t come out until those dangers are gone. If being disowned, financially cut-off, or assaulted is a possible reality, make sure you have somewhere safe to go where your basic needs can be met. There will always be people who won’t accept you for who you are, but there will be even more who will support you. You just need to find that community. 

Why is it important for you to work at a company that values diversity in all forms?

Companies that support diversity help us evolve into a more accepting society. When people are exposed to colleagues who are different from them, they get to know each other on a personal level and start to realize that we are all more similar than different. I believe these experiences translate into the way people treat others outside of work and how they raise their children.

At Alto, we believe in a world where every perspective matters and that diversity fosters creativity and creates innovation. We welcome candidates of all backgrounds, skill sets, and experiences. To learn more, read Why We Prioritize Diversity at Alto. 

For more information on how to make your workplace safe and equitable for all, read 11 Simple Ways You (Yes, You!) Can Make Your Workplace More LGBTQ Inclusive. 

If you or someone you know is considering coming out, we encourage you to review these resources: 

Parents, Families, and Friends of Lesbians and Gays (PFLAG) Recommended Reading: Coming Out

*ERG’s are voluntary, employee-led groups that foster a diverse, inclusive workplace aligned with organizational mission, values, goals, business practices, and objectives.

Coming Out with Pride: Nicholas Satow Shares His Story 

Nicholas Satow (center) with Camp Lightbulb leaders

Erik Gregorio Cruz, Micaela Moss, and Jordane Thomas joined Alto this summer as the company’s first engineering interns! Here they share their learnings, accomplishments, and their advice for future Alto interns.

How to Make the Most of Your Engineering Internship — Advice From Alto's First Interns

Erik Gregorio Cruz, Micaela Moss, and Jordane Thomas joined Alto this summer as the company’s first engineering interns! In their three months with us they blazed the trail for future Alto interns while adjusting to a new norm of fully remote work during the global pandemic. Here they share their learnings, accomplishments, and advice for future Alto interns.

Coming out of a bootcamp program rather than a traditional Computer Science degree program, Micaela hoped to find a company open to non-traditional educational paths. “I know that a company that is welcoming of bootcamp grads values diversity, inclusivity, and mentorship.” 

For Erik, it came down to his interview experience: “Everyone seemed to really enjoy their experience and really believed in the mission they were working on.” Micaela agreed, adding that it also ultimately came down to the people for her. “You can tell a lot about a company’s culture based on what the people who interview you are like,” she said. “From the recruiter to the engineers, everyone was incredibly friendly and a joy to interact with.”

What was the most fun moment of your internship? (That is, assuming you had fun!)

Virtual team lunches were a highlight for all 3 interns. However, one special moment during Micaela’s internship actually came from resolving a ticket that involved writing an end-to-end (E2E) test—something she was not looking forward to. “I was dreading it for two reasons: First, I do not particularly enjoy writing tests—I’d rather write the code that passes them—and second, I had never worked with Cypress before. Several hours later, after reading lots of documentation, studying previously written E2E tests, and getting stumped by a hidden selector, I managed to write the test. When I finally ran it and got to watch the video as it clicked on buttons and filled out inputs, I became instantly enchanted. I may have run it several more times just to watch it, smiling like a goofball, knowing that this test that I had created would be run every time code was pushed and merged.” 

In addition to their respective engineering managers, whom the interns had weekly 1:1s with, each intern was also assigned a dedicated mentor, who committed at least 5 hours a week of dedicated support to their interns over Slack and Zoom. Mentors were able to provide historical and business context, help interns get ramped up on Alto’s tech stack, codebase, and tools, and pair program as needed. “Working with my mentor definitely made me more productive,” said Jordane.

The mentors added that working with the interns actually helped them improve their ability to articulate technical concepts, as well as their ability to talk through technical challenges with others more effectively in their day to day work.

What was it like interning during the pandemic and being fully remote?

“I found myself setting up ‘Hey, there’s a pandemic, and this is crazy, so let’s get introduced virtually, maybe?’ meetings,” said Micaela. “Although, as someone who is horrible with names, it is worth noting that a silver lining to being entirely remote is having everyone’s name in the corner of their zoom video. That, and sweatpants everyday!” 

Erik and Jordane agreed that being remote required a little extra effort. Alto’s engineering office is based in SF, and since they weren’t required to be physically in-office this summer due to the pandemic, both Erik and Jordane were based in other time zones. “In the beginning I was starting my day at 9am EST/6am PST, but if I got stuck I would have to wait until West Coast working hours before I could reach out,” explained Jordane. With time, “I picked up a different working rhythm that worked better for everyone.”

While Jordane was surprised by just “how friendly and accessible everyone was,” Erik was surprised by how quickly he was able to actually deploy code. 

Acknowledging that her chosen career path has a history of gender imbalance, Micaela shared that she “was pleasantly surprised” to have both a female manager and a female mentor. “It was a great experience getting to have two strong female role models to learn from during my internship.”

Micaela and Jordane were both on the Pharmacy Platform team, which defines best practices and processes that promote a future-forward and scalable way of development. The platform team provides tools, libraries, and services that make development work at Alto and enable all of Alto's engineers to write performant code. Erik was on the Pharmacy Supply Chain team, which enables a better, faster experience for patients by ensuring the right medications get out the door, on time, and at the lowest cost possible.

Erik’s mentor, Eric Leite, helped us understand what Erik contributed to the Pharmacy Supply Chain team: “Sometimes our operations workflow requires manual intervention to resolve issues. We use an extendable admin interface to help us navigate the more complex issues. Erik created an add-on to this application that helped our on-call team work more efficiently. We can now resolve a specific kind of complex insurance claim issue by using his add-on to guide us through the multi-day resolution process. Erik learned about our supply chain operations workflow, how insurance claims are processed, how to model out a problem using Ruby on Rails, and how to write effective tests using RSpec.”

Micaela and Jordane, both on the Pharmacy Platform team, worked on optimizing performance and cleaning up legacy code. For instance, Jordane helped standardize Alto’s frontend by increasing adoption of our component library. “Although this was a relatively straight-forward task that didn’t require much problem solving, it did require a lot of endurance,” said Jordane. “I had to edit and test changes to over 300 files by hand. There were many times I could have broken [the platform], and changes needed to be made very carefully.”

What is the biggest learning you are taking away from this experience?

“The biggest learning I am taking away from this experience is nicely summed up by the grail knight in Indiana Jones and the Last Crusade: ‘You have chosen...wisely.’” said Micaela. “I knew I enjoyed software engineering when I was learning it, or when I was working on my personal projects, but that can change when it becomes a job. After spending the summer as a software engineering intern at Alto, I can say with confidence that I have chosen...wisely.”

Jordane discovered that “engineering isn’t just innovation,” as he came into the experience believing; “it’s also investigation.” When we asked the interns’ mentors and managers what they had learned from the interns, they all recognized the genuine curiosity the interns brought into their respective teams and projects, which helped them to see Alto’s codebase through new eyes. They also gushed about the excitement the interns had when pushing to production for the first time.

What words of wisdom would you give to future Alto interns?

All three agreed: ask as many questions as you need to! “Over communicate, and just relax & enjoy the process!” offered Jordane. Erik agreed sharing, “Do not be afraid to reach out when you get stuck. Reaching out for help is essential.” 

“An internship is all about learning and growing,” said Micaela, “so take advantage of the wisdom and experience of your peers. They have a lot to offer!”

Ashley Qian, the Senior Engineer who mentored Micaela, advised, “Know your limits! Take breaks! Find something else to enjoy other than software engineering because your work is not your life, and your life is not work. Surround yourself with people who are your advocates and go to bat for you, and if you find yourself in a system or an environment that does not support you, try to understand what your boundaries are, and leave if you can. You always have a shoulder to lean on if that's the case, here, with the friends you've made at Alto!

Interested in being an intern at Alto? Check out our careers page HERE.

We took the best parts of the software engineer interview process from the places we’ve previously worked and interviewed, eliminated stuff we thought wasn’t relevant, and added our own special Alto ingredients!

What to Expect When You Interview as a Software Engineer at Alto

Thank you so much for considering an interview at Alto! At Alto, we’ve devoted a considerable amount of time refining how we interview candidates for software engineering roles. As engineers, engineering managers, and recruiters at a rapidly growing company, this is a big part of our jobs and we want to get it right: for the candidate, for ourselves, and for the team. We took the best parts of the interview process from the places we’ve previously worked and interviewed, eliminated stuff we thought wasn’t relevant, and added our own special Alto ingredients. Let’s dive in!

What does a Software Engineer at Alto do?

First and foremost, Alto exists to serve our patients--whether that be via building products, or providing exemplary service. Engineers at Alto are empowered to go the extra mile to make an impact for our patients, medical providers, and amazing pharmacists and care professionals. We are organized into small mission-focused teams where you will be working closely with Product Managers, Designers, Data Analysts, Data Scientists, and our Care team. Alto Engineers enjoy this cross-functional, collaborative environment where everybody has a voice in the direction of the product and the team. Compared to other companies, we are more end-user focused in most of our teams, even those that work primarily on platform and infrastructure.

Our pragmatic focus on impact includes making sure that we fulfill our company value of Patients Come First. We have a strong culture of code reviews, testing, documentation, and knowledge sharing to ensure that the service consistently meets our patients’ and providers’ expectations for quality and reliability.

Developing a Predictive Interview Process to Reduce Unconscious Bias

We want our engineering team to look like our customers — and we strive to serve everybody. Our mission is to fulfill medicine’s true purpose — to improve the quality of life — for everyone who needs it. In order to effectively carry out our mission, we believe our engineering team should reflect the rich diversity of our customers. Our engineers come from all backgrounds and took many varied paths to arrive here: self-taught, coding bootcamps, and top-tier universities. Prior experience ranges from none to decades at large public tech companies with many joining from other startups and consulting/contracting backgrounds. Reflecting this, we’ve put together an interview process that focuses on predicting job success over testing for rarely-used computer science knowledge and encourages hiring diversity of all kinds rather than filtering for a certain type of engineer.

Throughout the interview, we work on problems that are facing Alto today or that we’ve dealt with recently. Our interview questions rarely have a “right” answer, and if you are writing code, any language works. (We spend our time mostly in Javascript, Ruby, and Go.) Occasionally, you will have more than one interviewer in the session. This is likely because one interviewer is shadowing the other to train, get calibrated, and learn how to deliver and interpret the questions while minimizing bias.

This is a quick chat with a recruiter or a hiring manager to further expand on your experience, capabilities, and interests. Based on this, we’ll have a good idea for which team(s) you would be the best match.

This screen aims to validate your technical skills. You’ll be working in a networked IDE (like CoderPad) with an Altoid (what we call ourselves) to write and run code that addresses a typical problem that you might face at Alto. We’re looking for fluency in the language of your choice and some fundamental object-oriented programming design skills. 

This is based on a typical task that you might face at Alto - something like designing or interfacing with an API. You're welcome to use StackOverflow, Google, or any other resources at your disposal—including your interviewer! We’ll be observing how you understand the problem, communicate with your interviewer to develop requirements, and get to working and well-tested code. 

In this section, you’ll spend some time getting to know a problem we have faced. You’ll spend 10-30 minutes working on how to approach and optimize a challenge that impacts our business everyday, then show that you can translate that into working code.

This module varies depending on your experience and interests. For some folks, we dive deeper into software design and learn how you would break up a hypothetical application into core modules. For senior frontend developers, this might be an app architecture challenge. And for senior backend developers, we’ll address systems architecture with an eye toward scalability, observability, and technology choices. In every case, we’re looking closely at how you approached the problem, gathered requirements, and justified your decisions.

The Engineering Manager is trying to deeply understand who you are as an engineer and a person. What do you get excited about? What type of roles do you like taking on within a team or project? What is your career arc and how can you best advance that at Alto? The questions often asked are behavioral or hypothetical in nature, and we love to hear stories about your proudest accomplishments and challenges you’ve overcome.

“I had an amazing interview experience with Alto - although the recruiters were super busy, they made sure to accommodate my timeline," shares Jacinda Zhong, Software Engineer, Core Services at Alto.  "I was really pleased to find out that Alto asks questions based on the type of work I’d be doing - no obscure CS concepts, and questions centered around complex business logic that you’d encounter working at Alto. Before my onsite, my recruiter gave me a call to provide context on what they’d be asking. No gotchas and no surprises, plus lots of detail so that I could be prepared to do my best. So excited to be working here and contributing to a great mission!”

The interviewers get together promptly—we try to do it no later than the next day—to discuss next steps. Prior to our discussion, we individually assess your performance against a rubric that takes into account your level of experience and the requirements for the role.

There is rarely unanimity in the panel. Almost everybody at Alto was discussed in a panel where there were some mix of Yeses and Nos. Often, we ask ourselves questions like, “What is the candidate’s superpower?”, “What will they add to the team?”, and “For which open role are they the best match?” Our hardest decisions are the ones where we all agree that the candidate is somebody we want to work with but we don’t have exactly the right role.

Don’t be surprised if your interview is slightly different from what is described here. We’re constantly refining our process to get to better hiring decisions more quickly and with less bias with regular feedback from candidates, interviewers and recruiters. 

Have you had an interview experience that you thought was exceptional? Let us know at feedback@alto.com.

In this interview, Alto's third engineer shares how her background and experiences, from her nomadic upbringing to serving as student body president in college, led her to where she is today at Alto.

Building an Engineering Career at Alto 

This interview has been edited for length and clarity.

Elnaz joined as Alto’s third software engineer in 2016, coming from Lob. She has since gone on to shape Alto’s culture and recruiting efforts and rose to become an Engineering Manager. In this interview, she shares how her background and experiences, from her nomadic upbringing to serving as student body president in college, led her to where she is today.

You’ve lived in 8 cities spanning 5 countries and 3 continents! Tell me more about that and how it shaped you?

My family started moving around from a really early age. My dad was a chemical engineering professor in Iran for around 25 years. When my siblings started going to college in the United States, we started moving around to pay for their college tuition. He did a sabbatical in Australia (where I learned English!), a short stint at his alma mater Oklahoma State, time at a research institute in Kuwait, and a few other locations. 

As a result, I’ve been exposed to such extremes in my life in moving from the Middle East to Oklahoma, or between Chicago and San Francisco. I’ve just been exposed to such a variety of people that’s allowed me to both blend in with a lot of different folks, but also be able to be a bridge and a translator. Regardless of whether it's in work or my personal life, I think “passionate” is maybe the most consistent way I would describe myself. I'm either passionate about the work I'm doing or passionate about getting outside for camping and traveling. There's an intensity in all aspects of my life. 

From my past roles, I realized I loved working on cross-functional problems. I stumbled across Alto, eventually realizing that working cross-functionally was such a unique and fundamental opportunity with this company. We would not succeed if engineering sat in one corner and operations in another - we had to work together. The other piece was that I knew I wanted to work on something more meaningful. I felt like I was able to close the loop on what started off my career – working in civic tech and on public interest projects – and do that as a more effective person in the healthcare business. Finally, I wanted to learn more about the business side of things. What I learned in my first job out of school was that nonprofits and civic tech are great, but they don’t work unless you can fund them. I really wanted to find businesses that were viable and also added value.

You were Alto’s third engineer. What was that like?

In retrospect, it was fantastic. I was able to shape the culture, see the evolution of the company, and develop a lot of relationships. For example, I was really passionate about engineering being a partner to the rest of the organization and for us to go into the trenches to understand how the frontlines use our product to figure out how to make things better. I was given a lot of unique opportunities, including working on recruiting to make sure we were building a more equitable interview process, and also ensuring that folks are successful once they got here. I was able to influence Alto’s diversity and inclusion efforts and grow as a leader to pave the path for more people after me.

How was the transition from engineer to management like for you?

The first feeling was just sheer excitement. So much of what I’d been passionate about up until then had been done on the side: building an onboarding program for new hires, building out better interview questions, improving our on-call process. Becoming a manager was validation of how things that I'm good at are not just pure engineering skills, but also things that make engineering more effective. I'd been worried about being perceived as not technical enough, or that the soft skills didn’t matter, and it really validated that what I wanted to work on was valued. The second feeling was, “How do I actually know if I'm doing a good job?” I think that's one of the hardest things when you first become a manager. 

As an engineer, you have these tight feedback loops: you build something, the test runs, and you see the product and the impact. As a manager, you might have a conversation or make one comment to someone only to find out months later what the actual impact of that comment was on the person. I had to get accustomed to slower feedback loops and being more comfortable with less structure.

You were your college’s student government president. Tell me more about that and how it relates to what you do now?

What I quickly learned from that position was that defusing tense situations was my superpower. When there were disagreements between the students and the university, I felt like I could speak to both sides and bridge the gap. That was the first time I really began to appreciate my upbringing of having been exposed to a lot of different cultures and different people. This becomes relevant in basically every intersection at work: how engineering and operations relate to each other, how engineering and design relate to each other, or being able to see different perspectives within the same discipline. 

In particular, I think it was helpful for me to spend time with a design and development firm because I saw the anxiety that designers can have around not solving the problem at the core or being forced to make sacrifices about the fidelity of their solution. Now when I'm working with a designer I make sure they understand when I’m talking about velocity, but I can also put that hat aside and talk about what's possible given a longer timeframe. 

What’s the best piece of advice you’ve ever received?

I've always felt like I've seesawed between coming on too strong or being too shy. The advice I received was to not think about them as binary aspects, but rather celebrate that I have both of those attributes. So when I was weighing the idea of whether I’m really great at people management, does that make me less of a technical person? Or if I'm technical, does that mean I can't be good at the people side of things? I think this advice was really helpful for me to stop seeing it as an either-or choice and recognize I can be great at both. It makes me think of a clip of Dave Chappelle where he talks about advice that his mom gave him that really resonates with me. His mom told him, “Sometimes you gotta be a lion so you can be the lamb you really are.”	

What are you most excited about at Alto in the next year?

Personally, I’m most excited for my parents to be able to use Alto as we expand our service areas so they understand what I've been doing the past three years! Professionally, I'm excited about the big dent we can make in technical scalability, as well as making it easier for our operations team to provide a consistently excellent patient experience.

If you have any questions about Alto, or are interested in joining our team, please reach out via LinkedIn.

Senior Manager, Engineering at Alto Pharmacy

The first two members of our Advisory Board are Dr. James Hildreth and Jennifer Kent. Their years of experience as leaders in the healthcare industry will be invaluable to us as we continue to grow.

Alto Pharmacy's newly formed Advisory Board launches today with two anchor team members.

Since our launch in 2015, Alto has been committed to fulfilling medicine’s true purpose, and improving quality of life, for everyone who needs it. Today, we announce our newly formed Advisory Board and our first two anchor members, who will help guide Alto towards our mission, advise on key decisions, and support strategic initiatives. We’ve formed the Advisory Board to support our leadership as we navigate the regulatory landscape, launch new features to modernize the pharmacy experience, and adhere to the highest standards of operational excellence and patient care.

The first two members of our Advisory Board are Dr. James Hildreth and Jennifer Kent. Their years of experience as leaders in the healthcare industry will be invaluable to us as we continue to grow. 

Dr. Hildreth is the President and Chief Executive Officer of Meharry Medical College, one of the nation’s oldest and largest private historically Black academic health sciences centers. He received his Bachelor’s degree from Harvard University, his Ph.D. in immunology from Oxford University as a Rhodes Scholar, and his medical degree from Johns Hopkins School of Medicine. He was the first Black American in the 125-year history of Johns Hopkins School of Medicine to earn full professorship with tenure and is internationally known for his influential HIV research.


Today, we announce our newly formed Advisory Board and our first two anchor members, who will help guide Alto towards our mission, advise on key decisions, and support strategic initiatives.

Blog

Diversity At Alto: Building an Inclusive Healthcare Company and Culture

Get to Know Alto’s VP of Engineering, Mike McClay

Coming Out with Pride: Nicholas Satow Shares His Story

How to Make the Most of Your Engineering Internship — Advice From Alto's First Interns

What to Expect When You Interview as a Software Engineer at Alto

Building an Engineering Career at Alto

Announcing Alto’s Advisory Board

Bringing Alto to a Neighborhood Near You

Help Us Shape the Future of Healthcare

Women Leading the Way

Alto's Mission & Values

Why We Prioritize Diversity at Alto

Switch to a better pharmacy.