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

Last month, Alto celebrated the well-deserved promotions of many Altoids across the company. Among those promoted is Elnaz Moshfeghian, who is now Alto’s VP of Strategic Planning & Business Operations. Elnaz shares more about her new role, what she’s most excited about at Alto, and advice she has for those looking to make a career pivot.  

Catching up with Elnaz Moshfeghian, Alto’s new VP of Strategic Planning & Business Operations | Alto

Last month, Alto celebrated the well-deserved promotions of many Altoids across the company. Among those promoted is Elnaz Moshfeghian, who is now Alto’s VP of Strategic Planning & Business Operations.

Elnaz joined Alto in 2016 as a software engineer and when we last connected with her in 2020, she shared her thoughts on building a career in engineering. Since then, Elnaz has pivoted to a truly cross functional, strategy-focused role, where she applies learnings from her engineering experience with her ability to identify opportunities for growth. 

Below, Elnaz shares more about her new role, what she’s most excited about at Alto, and advice she has for those looking to make a career pivot.  

To start, congratulations on your new role! You joined Alto 6.5 years ago, and so much has changed both within the company and the industry at large. Can you tell me a little bit about your journey at Alto? 

I’ve always been attracted to problems that are cross functional and can be solved by bringing together different teams - pharmacists, technicians, logistics, dispatch, sales. I really enjoyed it as an engineer, given that when I joined there were no product managers. We all had to figure out what we were going to build and build it ourselves. I loved working with teams, which is why I pursued the manager track. I noticed pretty quickly that the most interesting and challenging problems rarely came down to technical decisions, but more-so to people and priorities. 

As I grew in my engineering career, and got to lead teams solving problems, I was always searching for how to expand my understanding and impact across the business. I had the opportunity to shift into a strategy and operations role, which allowed me to shadow the CEO and learn a great deal while also identifying the company’s key priorities, understanding how they're doing, and ensuring that they stay on track. The new role allows me to use everything I’ve learned over the last 6.5 years at the company while at the same time, learning a lot from a seasoned leader like Alicia on how to run a business. 

Your previous experience was in engineering, and you didn’t work in healthcare or pharma before joining Alto. What has been the biggest surprise to you since joining the company? 

There are a lot of different hands in healthcare; it's a really complex space and there’s a lot at stake. I’m always mystified by how hard it is to align different parties’ incentives to result in the right outcome for patients. It underscores the importance of Alto’s mission: to fulfill medicine’s true purpose — to improve quality of life — for everyone who needs it.

Tell me a little bit about your current role. What are you most excited by? 

I’ve loved seeing how the different pieces of the company connect, and being able to connect the dots when we’re missing something. It’s been really fun to see how a little bit of communication and collaboration can go a long way. I also love thinking about how what we’re doing today could set us up for bigger things in the future, and how we build today in a way that opens a lot of doors for us down the line. 

In your opinion, what are the biggest opportunities for the company? 

There’s always an opportunity to be excellent at the basics. Are we consistently providing the best patient experience? Are we getting patients the best price? Are we saving time for prescribers and their offices? Those are problems that we’ve been solving for a long time, but it just gets more interesting and challenging as we’ve gone into new markets and therapeutic areas, and worked with different kinds of patients and prescribers than we used to. 

Something that I’ve always been intrigued by is - how do you bring more transparency around pricing to prescribers and patients at the earliest possible time, so that they can make the best decisions? It’s something that’s really missing in the industry. It’s not easy to do, and that’s definitely something I think a lot about - ‘How can we be the one who makes it easy for prescribers to know what they’re about to send to the patient, and for the patient to know what their other options are?’ Because a lot of times, what your insurance may cover and what your doctor may prescribe may not always be the best option. There might be other options, and I think a lot of people don’t know to ask about that. 

What are the biggest challenges in the pharmaceutical industry today? 

I think there’s been a lot of great activity from different patient advocacy groups and state governments to regulate the worst of what’s happened in healthcare. It’s been cool to see that take shape over the last five years. The challenge is that it’s very hard to write legislation and force some of these things, and so I’ve honestly gotten more interested in how do you write the right laws and approach regulation in a way that allows innovation to still happen and thrive, and still protects the patient at the end of the day. 

Back to your engineering roots – what advice do you have for young engineers?

Given the state of venture capital and the industry, a lot of engineers are going to earlier-stage companies, because there’s a little bit more investment and activity happening. I had to figure that out along the way - how do you operate as the third engineer on the team? Being anyone in an early-stage, small company - and an engineer especially - comes with its own unique challenges and skills. It’s not something there’s a ton of resources around. There’s a lot of resources about how to start a company, but not a lot for how engineers can grow their career at a company at that stage. So, my advice would be to seek out mentorship and cross functional peers from whom you can learn and grow. 

You pivoted from engineering to operations and strategy. What advice do you have for someone looking to make a career change? 

As an engineer, I’ve really focused on making an impact, whether that’s through building a product or shaping the business with what I know, with tech being the backbone. And I think that’s something we don’t talk about as much in engineering - how do you take your skills and really channel them for maximum impact and better understanding of a business? And for people who want to start their own companies someday, taking the path I did could be really valuable. It allows you to be a better entrepreneur and a better contributor if you can see the connection between engineering choices and the systems you’re building, and how they impact your customer and other parties. 

The other piece is being comfortable with wearing a lot of different hats. It’s what really helped my growth, and it’s counter to a lot of advice you get. People will tell you to go deep, get specialized and go down one path. You need to, to some extent; I absolutely had to figure out how to be a better engineer and a better leader. But the most growth for me wasn’t necessarily to stay in engineering – it was to take a turn. Hopefully, I can give colleagues a little more confidence who want to take a turn and increase their impact, growth and learning. 

Catching up with Elnaz Moshfeghian, Alto’s new VP of Strategic Planning & Business Operations 

When Jake Moffatt says he loves building things, he means it — sometimes literally. A construction project manager turned engineer, Jake has spent the past decade building software at mission-driven organizations. Today, as Engineering Manager of Alto Assistant, he leads the team that’s bringing wizard-like support to Alto’s customer-facing app.

Get to know Jake Moffatt, Engineering Manager on the Alto Assistant Team

When Jake Moffatt says he loves building things, he means it — sometimes literally. A construction project manager turned engineer, Jake has spent the past decade building software at mission-driven organizations. Today, as Engineering Manager of Alto Assistant, he leads the team that’s bringing wizard-like support to Alto’s customer-facing app.
Below, Jake chats with fellow engineering manager Mike Riess and recruiter Braden Hanlon about the work ahead for Alto Assistant.

I’d love to learn more about your background to get us started. How did you end up in software engineering?

When I was twelve, I started learning to code in QBASIC because I wanted to make video games. Once I wrote my first program, I was hooked! I loved computers and the creative power they gave to anyone willing to invest the time and energy to learn. Since then, I’ve built games, personal tools and projects, desktop software, and a number of apps and services — I love building things. My career has gone back and forth between construction and software engineering, but it’s been firmly in the software industry for the last ten years or so.

My favorite place to be in a company is working on something new that has a big impact or addresses an important problem. In a previous role, I built an app that helped people find roommates in a city where housing is prohibitively expensive. At that same company, I led the team responsible for creating a new vertical that eventually split off into its own company.

The goal of Alto Assistant is to help customers help themselves before reaching out to support. Our first project is introducing a wizard-like support “assistant” (hence the team name!) that guides the customer through a series of questions to narrow down the area of support. We’ve already identified a few tasks the assistant can help customers complete on their own, including making changes to upcoming deliveries or scheduling new orders.

In cases where we can’t help them just yet, our new tool generates data to help us to learn exactly what customers need help with. It’s a top priority to bake analytics into every new feature we build; even though we have years of experience supporting our customers — and we know intuitively which problems they frequently experience — we don’t have conclusive data to draw upon just yet.

We plan to start with a couple of frequent use cases and measure how often customers reach out to us for support. Then, we’ll chip away at the problem until we’ve seen a substantial improvement in the user experience. From there, we’ll move on to the next biggest problem and repeat the cycle. There’s a reason “Chip away it” is an Alto value: It’s the playbook that we’ve used to automate other critical parts of the pharmacy value stream like intake, billing, and fulfillment.

What opportunities are you most excited about?

Support drives much of the cost of every shipment today, so this is a high-impact area for our business. A year from now, it would be a stellar outcome if the Assistant team could reduce the number of issues that customers need support on by half.

We’re also thinking about the user experience beyond the app. We plan to improve the tooling that our care specialists use to provide support as well. We’ve already discussed some promising ideas like creating the concept of a conversation in support communications rather than an infinite stream of messages and building out enriched communications. We also intend to develop a custom tool that can expedite a customer’s prescription when they need their medication ASAP.

The possibilities are many, and it will take a team of determined, passionate, empathetic people to solve these challenging problems. I’m super excited to see what the Assistant team will do together.

Any lessons learned from previous experience that you’re applying to your role at Alto?

There’s always the temptation to tackle everything at once with new business initiatives. My experience leading new verticals at Apartment List and Snapdocs taught me the importance of being laser-focused on one or two key metrics instead of trying to build out a fully-realized product from the beginning. That’s exactly what we’re doing on the Alto Assistant Team with our clear focus on reducing communications per shipment — how often customers reach out for help because they could not find what they needed in our app.

It’s also important to recognize that we won’t have all the answers right out of the gate! I like to think of product development as a three-step sequence: learning, growth, and maintenance. Alto Assistant is so young that we’re very much still in the learning phase. We maintain a tight iteration loop with everything we ship: launch, measure the impact, and use the results to iterate and refine our hypotheses about what our users want. Our final product could be anything from a customer support wizard to an AI chatbot to a ticketing system — we have to rely on our key metric of communications per shipment, experimentation, and user feedback to shape the direction.

What got you excited to join Alto? What would you pass on to an engineer thinking about applying to the company?

I was impressed by the Altoids I met during the interview process. I knew I would be working with people from whom I could learn a lot, like Elnaz, who started as an individual contributor and went on to become Director of Engineering and, now, Alto’s first Head of Strategy & Operations. I was also impressed by the quality of the interview process itself — a good sign that the company was well-organized internally. Finally, the pitch for the role was extremely clear, with already-established key metrics that would directly contribute to the company’s bottom line and help Alto become more profitable.

For engineers, I think Alto is a great place for both technical challenges and career growth. We’re still small enough that every individual gets exposure to a broad portfolio of high-impact projects. It’s also a great environment for learning about how a business works — the Product & Technology organization does a great job of sharing information and presenting problems in a way that gets to the root business problem we’re trying to solve. There’s a clear line between any project a team is working on and a foundational business metric. Most importantly, we’re a company that makes a truly positive impact on our users’ lives.

Interested in learning more about engineering at Alto? Follow us on LinkedIn.

October 11 marks National Coming Out Day, an opportunity to celebrate all those who have come out as LGBTQ+ and recognize the courage they’ve demonstrated by choosing to be their authentic selves.

Celebrating National Coming Out Day at Alto

October 11 marks National Coming Out Day, an opportunity to celebrate all those who have come out as LGBTQ+ and recognize the courage they’ve demonstrated by choosing to be their authentic selves. In honor of this annual celebration, we sat down with two Alto team members — Ben Romero (he/they), Business Operations Manager for Health Plans and Travis White (he/him), Senior Software Engineer — who generously shared their experiences of coming out as bisexual/queer. Here are their stories, in their own words.

Ben: Like a lot of folks, I avoided coming out for most of my life. I grew up knowing that I wasn’t exactly straight and later recognized that I’m bisexual. I remember my entire experience around my sexuality being wrapped in shame. I would reluctantly conform to heteronormativity just to avoid the fear of being outed or questioned. It wasn't until college that I first felt like I could open myself up to the experience and validation that I deserved. By the time I graduated from college, I had a refreshed sense of my place in the world, but I was still hiding my sexuality from my family.

Five years after college, I was finally ready to be open with my family about being bisexual, and it was the first time I felt as if I had to “come out.” At the time I was engaged to my non-binary/queer partner. My family knew my partner as a woman, but my partner was also beginning to validate their nonbinary gender experience. All I could think about was how much of a disservice it would be to our identities as a queer couple if we started our marriage having to assume more invalidating heteronormative assumptions. I first told my closest family members — my younger brother and parents — who supported me unconditionally and showed me so much love. Not every family member was as accepting of my sexuality, which was really disappointing, but I had more than enough support from my chosen family to finally overcome the fear that I had held on to for so long. 

Travis: I realized I wasn’t completely straight at some point in high school. Growing up Catholic, I was always taught that men are attracted to women and that being gay was a sin. So when I found myself attracted to both girls and guys during high school, I wondered what was wrong with me. I brushed it off and ignored that aspect of my sexuality for a long time, which I would later come to regret since it definitely fed into ongoing anxiety and depression in college.

I first came out to my closest friends during my junior year of college. By that point, I had fully accepted that I wasn’t straight, but I had never acted on my bisexuality. I had only dated girls, so my friends saw me as completely straight. I couldn’t quite figure out how to tell them, and it ended up happening organically while hanging out on a Friday night. We were playing a game around the table that required everyone to share something no one else knew about them. Something came over me and I decided to throw caution to the wind with a, “by the way… I’m bi.”  

I came out to my parents several years later when I was working my first engineering job out of college, living in Silicon Valley and loving life. I knew that if they chose not to accept me, it was going to be their loss. After a night out (and an amazing prime rib dinner) when they were in town, I told them that there was something I wanted to tell them about myself - that I am bisexual. My dad’s first response was, “What does that mean?” I informed them that it means I am attracted to both men and women, though more recently, I’ve come to think of myself as being attracted to interesting people regardless of the gender they identify as. My parents were very supportive, but truthfully I had reached a point where I could be accepting of the worst-case scenario. 

Ben: I was most grateful for the sense of relief I experienced. Despite facing criticism and homophobia from some of my siblings after coming out, I couldn’t shake the sense of pride I felt from allowing myself to be unapologetically queer and visible. I’m finally allowing this part of me to flourish and grow. It’s liberating to be radically honest with yourself and others, regardless of what anyone else may think. I’ve now come to identify with the term queer in addition to bisexual. Part of the growth I’ve experienced involves unlearning so much of what I’ve been socialized to believe about the gender binary, and I’m just now starting to understand where I exist outside of it.  

Travis: When I came out to my friends during college, we stayed up talking until very late into the night. I left feeling a huge weight lifted off of my shoulders — and so full of love and support from some of the people I was closest to.

And later when I came out to my parents, they accepted me with open loving arms, for which I’m grateful, but I was also prepared to move forward with my life even if they did not accept me as my true authentic self.

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

Ben: The isolation of being in the closet can sometimes lead to stories or expectations of yourself that aren’t necessarily helpful, or true. For me, as a bisexual, some of those expectations sounded like “I’m not queer enough,” “I don’t fit into the queer community,” or “people won’t believe I’m bi/queer.” I looked to my queer friends and even to LGBTQ+ advocates on social media and was relieved to find that they had many of the same fears about coming out as I did. I found that learning from other people’s experiences could help validate my own feelings, even if we had a different orientation or gender. As a queer Latinx, I also sought validation from people who shared similar intersections around my identity, which helped me navigate the concerns I had about coming out to my family.

Travis: My friends were very supportive so I was really able to lean on them. It was also helpful to just search online for other people’s coming out stories. Before I could tell my family, I knew I had to reach a point where I would be secure in my identity regardless of the outcome of that conversation. Part of the reason it’s so important to share coming out stories is because hearing other people’s experiences helps inspire you to do the same.

What advice would you give to others considering coming out? 

Ben: Above all, put your safety first. Try your best to not take on the burden of guilt for not being your authentic self — that is not a reflection of you, but a reflection of how our environment can fail to provide the validation we deserve. Take your time and build your comfort with folks who will validate your experience. There’s a whole community of people who will back you up and care for you if someone you come out to is hurtful or invalidating. 

Travis: Do it if, and when, you’re ready. You can never control how others will react, so just accept that other people’s responses have nothing to do with you. It took me years to reach that point with my family. It can be incredibly tough, and you can never know in advance how anyone will respond, but if they cannot accept you for your true authentic self, there are plenty others out there who will.

Do you have any suggestions for allies? 

Ben: I would stress the importance of familiarizing yourself with queer history and how our struggle for acceptence has evolved over the years. The LGBTQ+ community and allies have so much to be proud of today, like the repeal of “Don’t ask, don’t tell” (a former U.S. policy that directed military applicants to not disclose their sexual orientation), the legalization of gay marriage, and more queer representation on our screens — just to name a few.

At the same time, while all of those are certainly celebratory milestones, I ask that allies also recognize that our pride comes from so much more than a handful of legislative victories over the last decade. Our pride comes from the queer folks who came before us and fought for our visibility by rallying voices to speak out against injustice. Allies can research events such as the Compton’s Cafeteria riot, the Stonewall uprising, or the works of the Combahee River Collective. Understanding this historical context is important for also understanding the intersectional nature of the LGBTQ+ struggle for acceptance and restorative justice. Even though we have much to celebrate, our struggle continues as we fight for those who are still excluded or marginalized. 

Travis: Listen. The number one thing you can do is to listen and accept what someone in the LGBTQ+ community is telling you as their truth. It may change in the future — and that’s okay! Sexuality and gender are not a binary, and both can be incredibly fluid.

For parents: how you discuss sexual orientations and gender identities at home can leave a lasting impact on your children. I remember asking my mother about her thoughts on gay marriage, and she shared a more traditional view of marriage as a union between a man and a woman. That stuck with me for a long time and is a key reason I waited so long to tell them who I truly am. Read your toddler a book about a gay couple that gets married, teach your teens about prominent members of the LGBTQ+ community (and why they’re important), and if your LGBTQ+ child asks you to drive them to gay prom, treat the scenario as completely normal — because it is.

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

Ben: For me it’s a requirement that a company I work for prioritizes diversity and inclusion. I appreciate that Alto provides visibility into the progress that we’ve made towards building a diverse team that reflects the diversity of the patients we build solutions for. We also hold space to identify the work that still needs to be done. It’s really validating to have your background recognized at company celebrations and events or in spaces like employee resource groups (ERGs)*. It’s also important that we do all we can in our everyday actions to foster a collaborative and inclusive environment — one where people feel comfortable enough to be their authentic selves and not like they have to mask their gender, race, neurodivergence, or any other part of their identity. 

Travis: The U.S. — and the world — is made up of so many different people. There’s diversity of thought and beliefs, educational experiences, socioeconomic status, gender, race, A homogenous company that doesn’t mirror that diversity  will never be able to serve the entire population, and will miss out on a lot of opportunities. Alto’s mission is to fulfill medicine's true purpose — to improve quality of life — for everyone who needs it. The key word to me is everyone, and to truly fulfill the promise of that mission, we need a company as diverse as our customers. I personally find it rewarding to work at a company that values diversity and has strong representation of many identities, because that’s how the best ideas come to fruition and ultimately how the most positive impact is achieved.

At Alto, we believe in a world where every perspective matters. Diversity fosters creativity and creates innovation, and 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 LGBTQ+ team members, 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

*ERGs are meant to empower community groups within an organization by directly linking decision makers and implementing policies that support the group’s specific needs. The groups often center around a shared identity or experience and focus on building community, providing support, and contributing to its members’ personal and professional well-being. By creating an open forum for employees to come together, discuss challenges and opportunities, and foster a sense of belonging, ERGs help both individuals and organizations thrive.

Get an inside look at the patients team at Alto Pharmacy to learn what it's like to work on Alto's customer-facing apps, which projects are on the horizon, and who makes the best barbecue short ribs.

Get to Know the Team That Builds Alto's Customer-Facing Apps

Imagine an app that allows you to buy things and have them delivered to you the same day, for free. Now take that app and put it in a highly regulated space like pharmacy. You face the challenge not only of building an e-commerce platform from scratch, but also of navigating medication pricing, federal and state regulations, and patient safety—and that's just the way the Patients Team likes it.

"It's a really exciting and fun problem to solve," says Mike Riess, the team's Engineering Manager. Software Engineer Angelique Nehmzow agrees: "There's a really strong product and design aspect, like more traditional startups, but then everything gets a little bit more interesting because it's healthcare."

Below, we chat with the team to learn what it's like to work on Alto's customer-facing apps, which projects are on the horizon, and who makes the best barbecue short ribs.

What does the Patients Team do at Alto? 

Ask anyone on the team why they joined, and chances are, they'll tell you they wanted to be on the product team closest to Alto's customers: "We really try to own the customer experience," says Peter Zeng, the latest Software Engineer to join the team. "If a customer is coming to the web app, or they're coming to our mobile app, we want to make sure that they're able to onboard with us as easily and conveniently as possible."

The team is also responsible for the customer experience beyond onboarding, from the moment a customer schedules a medication for delivery to the time that it shows up on their doorstep. "We already offer great services like free, same-day delivery and cost savings. The Patients Team empowers customers to make the most of our offering," Nehmzow explains. "You can see what prescriptions you have, check on the status of your order, and schedule automatic refills. In a more traditional pharmacy, you don't get that kind of visibility. You have to call them up or even wait in line in person. At Alto, it's a different experience."

What was it like in the team's early days?

Today, there are eleven engineers on the team working to build that better end-to-end experience—but it wasn't always that way. When the team first formed in 2019, it consisted of just three members: Riess, Brian McRae, and Andy Lau, all of whom are still on the team.

"The first priority for us was just stabilizing the foundations," Riess says of the team's early days. Every other week, the three team members, along with Alto co-founders Matt Gamache-Asselin and Jamie Karraker, would meet to audit the app's core flows. "For the first three months we probably didn't make it through some flow at least 50% of the time," Riess recalls. "There would be a ton of bugs in the onboarding experience, things that weren't working with the flows or navigation or deep linking."

Among the team's first projects was a redesign of the checkout flow. "There was a lot of work to be done to streamline the checkout flow, which is pretty much the main function of the app," says McRae, who initially joined the team as a software engineer and later transitioned into product management. "We had to make it easier to add a payment, add your addresses, everything you need to do to schedule your prescription for delivery."

"The growth of the team, in terms of both size and stability of the platform, has allowed us to swing at more interesting bets for the company," Riess says. In particular, the Patients Team has turned their attention toward experiences personalized for specific medical conditions.

"Different customers have different needs. A customer who wishes to start a family will have a different experience than a customer who needs to order their routine heart medications that they've been taking for the last eight years,” McRae says. “The challenge for us is how we serve all these customers well through the app."

"I think that's where Alto can be such a differentiator," Riess adds. "A world-class pharmacy experience is about so much more than just dispensing medications. We want to build tools for customers that help them get the most out of their medications—everything from simple videos teaching them how to perform injections safely at home to the ability to synchronize deliveries for multiple prescriptions for managing complex health conditions."

With these new projects on the horizon, engineers have ample opportunity to focus on the areas that excite them most. "We're full-stack and mobile and web," Nehmzow says. "Part of the team focuses more on experimentation, iterating quickly, and using data to make decisions. Part of the team focuses more on platform work, tooling, and improving the developer experience. There are a lot of areas to explore and contribute to."

One spring night, the Patients Team gathered in a back yard in San Francisco’s Mission District for short ribs and an impressive spread of side dishes. "Kudos to Robbi, who's the grill master. I just provide the grill!" Nehmzow says, laughing. While the team barbecue was the first time some members had met in person, Zeng notes that the team has been supportive of one another even while working remotely during the pandemic.

"The first real project that I was assigned to was working with the communications system. Before writing my first piece of code, I spent two weeks exploring what already exists and understanding the different parts of the system," Zeng says. "I've been really impressed with how understanding my teammates have been. They make the space for you to learn all the different pieces of code we own."

That culture of support is by design, reflected in the six principles—complete with matching emojis—at the top of the #patients-team Slack channel: "Empower each other," "be an owner," "find the path," "learn by doing," "embrace complexity," and "foster trust." 

While these principles echo Alto's company-wide values, they are unique to the Patients Team. "For a long time, we were the only external-facing product team at Alto," Riess says. "These principles were intended to be this motivation around how we win. It's a combination of how we treat each other, how we reason about decision making, and how we approach solving a problem that's never existed before."

As the team looks toward the future, those principles have never been more relevant: "We have a goal and an area we want to focus on, but in terms of which projects we're going to do, it's not a top-down thing," Nehmzow says. "It's very much, 'We're going to figure out how to solve this problem together, even when it's difficult.' That's my favorite part about the team."

The Patients Team is hiring! Learn more about open positions here.

Alto Pharmacy is recognized by Forbes as one of America’s Best Startup Employers in 2021, ranking 13th among 60 healthcare startups.

Alto Pharmacy Announced as One of Forbes Best Startup Employers

After discovering that half of all prescriptions aren’t even picked up—resulting in 125,000 avoidable deaths every year—we set out to build a new kind of pharmacy that focuses on the person behind every prescription.

Here at Alto, we’re transforming a $500 billion industry by reinventing what a pharmacy can do—from hand-delivering medications for free to offering on-call help by text or chat. Our customers are at the center of everything we do, and it shows. After delivering more than one million prescriptions, we have an NPS score of 86 and over a thousand five-star reviews on Yelp.

In addition to delivering a better pharmacy experience for everyone who needs medicine, we’re committed to cultivating a better workplace for for our team, every day. That’s why we’re honored to be recognized by Forbes as one of America’s Best Startup Employers in 2021, ranking 13th among 60 healthcare startups. Inclusion on the list was based on professional reputation, employee satisfaction, and growth, among other criteria. 

This accolade follows several others in recent months including LinkedIn’s Top Startups in 2020 and San Francisco Business Times Largest Bay Area Digital Health Companies in 2020. In addition, Alto’s CEO, Matt Gamache-Asselin, recently received recognition as one of The Top 25 Consumer Health Tech Executives of 2020 by The Healthcare Technology Report. 

“We have a lot to be proud of in the past year, especially in light of the challenges presented by the COVID-19 pandemic,” shared Gamache-Asselin. “I’m so proud of the hard work and commitment exhibited by every member of our team in providing exceptional pharmacy care in our communities. As we continue to expand our services to more and more people, we’ll also be growing our team of incredibly knowledgeable and caring professionals.”

Are you passionate about shaping the future of pharmacy? Join us as we  deliver our industry-leading pharmacy care to millions of Americans. 

For the full employers list and an overview of the selection methodology, head to the Forbes site. .

Alto Pharmacy Announced as One of Forbes Best Startup Employers 

Forbes 2021 America's best startup employers

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.

At Alto, we value effective communication across all teams. In our latest blog post software engineer Eric Leite shares how he set out to make it easier to understand how our repositories change over time while minimizing disruption to engineers’ existing workflows.

How (and Why) We’re Standardizing our Commit Messages

Have you ever tried to debug a production issue by looking at your commit history, only to find a bunch of commits that don’t seem to be connected to any specific feature? Or maybe you've pulled the latest version of a dependency and noticed a bug that wasn’t there before?

It’s hard to pinpoint where a problem might have begun if your project (or its dependencies) don’t rely on standards to commit and release code. This was a problem I set out to tackle in my organization: How can we make it easier to understand how our repositories change over time while minimizing disruption to engineers’ existing workflows?

At Alto, we value effective communication. We keep our pharmacists and operations team in the loop about every new feature we release to production on a daily basis. We also announce changes to our codebase in a dedicated Slack channel to keep our engineers informed. But that raises the question: How do we ensure that someone doesn’t forget to make an announcement? And can we reduce the time we spend writing one up? Introducing a commit standard would enable us to use automated tooling that makes communication about code changes effortless.

Consider an open-source repository with hundreds of contributors. Project owners often adopt standards and industry best practices because it makes the project easier to maintain as the number of contributors increases. Eventually, our engineering team will grow to this point—and, just like in an open-source project, we can’t expect engineers to retain all of our conventions in their heads when they contribute. Standardizing commit messages eliminates one of the many variables around how we commit code. It can give engineers more confidence in their releases, build trust in our codebase, and increase productivity.

Many engineers have a distinct working style. If you propose a change to their everyday workflow, you will likely encounter some resistance. That’s why identifying and working with key stakeholders before you introduce a new process can help ensure its success. One way to do this is to chart stakeholders on two axes—influence in the organization and interest in the project:

I used this chart to decide how I would direct my communication with the team. Folks who fell into the “low influence” and “low interest” quadrants didn’t need to be involved in the whole process. Instead, I kept them informed by using project-specific slack channels and documentation in Notion to communicate status updates and summarize meetings. Topics that required a team decision were discussed verbally rather than using Slack to avoid potential miscommunications.

The more likely someone was to push back on the project or give me valuable feedback, the more involved they were. I included those who fell into the “high influence” and “high interest” quadrants in almost every meeting. These folks served as a kind of litmus test for my ideas. They typically had high standards and expectations and needed to be convinced that a change was worthwhile if they were going to get behind it. Keeping people like this involved in the discussion is a great way to ensure that your initiative will produce value for your organization.

In a perfect world, we’d have standardized commits in every repository. However, given that Alto is a fast-moving startup, foundational changes need to be rolled out incrementally to minimize churn, validate impact, and allow us space to learn and iterate. There’s often not enough time or resources to do everything, and going all-in on something may require more effort than it’s worth.

We began by identifying the knowledge gaps we currently have about commit standardization and how we could iteratively validate the required process changes. We initially considered beta testing with the production app that runs our day to day operations because it had the most contributors and the most to gain from standardization. However, we didn’t want to risk blocking the majority of our team or experimenting with a project that was critical to business operations. The next best option was our internal component library—it had fewer contributors, so fewer engineers would be blocked if something went wrong, and more projects depended on it, so the potential impact would still be significant.

Given that one of our company values is to Focus On Impact, and that internal changes like this are difficult to measure, we quantified our level of success or failure using a team survey. We sent out a series of questions at the start of the project asking the team to rate their satisfaction with our current commit, review, and release processes. We plan to compare these results with a follow-up survey to measure changes in ease of committing code, confidence in releasing, and our developer NPS.

After closing our knowledge gaps and getting a baseline understanding of how the team felt about our release processes, we decided to adjust the scope to include the following changes:

Commit Standardization (i.e., formatting and enforcement of commit titles)

Versioned Release Automation (i.e., automatic version cuts, changelogs, and notifications)

We looked toward existing open source solutions to make these changes because we were on a tight schedule. There were many options to choose from, so narrowing them down to a shortlist before presenting them to the team helped speed up the decision-making process. The best tools for the job will depend on your engineering organization, of course, but we prioritized maturity, flexibility, and compatibility with our existing workflows during our evaluation.

We landed on the Conventional Commits standard because it has been vetted and used extensively in other projects, and a whole ecosystem of release tooling has been built around it. It also has a short learning curve, is flexible enough to work with all our repositories, and only enforces the bare minimum necessary to generate semantic versions based on commit titles.

We chose Commitizen to help engineers get familiar with the new standard, Commitlint to warn about (but not block) contributions with invalid commits, and Semantic Pull Requests to serve as the final gate for validating commit titles. This way, non-standardized commits are only stopped from being merged when a pull request is made, and it can be easily corrected using the GitHub UI.

The open-source tooling for release automation was sparse and highly specialized, but we found Semantic Release to be the exception as it offered the most mature, flexible solution. It manages everything from cutting a release to generating a changelog to publishing packages and notifications. It also isn’t limited to only publishing NPM packages, making it an excellent fit for our multi-language codebase.

While we have a ways to go before versioned releases are automated in all of Alto’s repositories, we’ve made a significant first step with commit standardization. Some engineers have already proactively adopted the new standard without any tooling, and I’ve personally found that it has helped my commits stay focused and become more granular.

So far, we’ve standardized our component library. The commit history in this repository used to look like this:

Commits now have more context in them that’s visible at a glance (e.g., feature vs. fix), and breaking changes are explicitly noted in the commit message using an exclamation point (e.g., refactor!). These commit titles are used to automatically generate a changelog any time we cut a release. We can even automatically cut and version-bump a release for every new commit because we follow a commit standard.

The next phase of this project will be to review and act on the feedback from the follow-up survey. We will continue to build on top of these standards with release automation tooling and discuss what process changes make sense for the rest of our codebase. We are confident that through these changes, we will be able to de-risk code contributions, reduce the burden of cutting a release, and better prepare for our engineering team’s future growth.

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

How (and Why) We’re Standardizing Our Commit Messages

In July 2020, Catherine Scott joined Alto as Head of IT, responsible for building and leading a high performing IT team. We sat down with Scott to learn more about her plan to build Alto’s IT strategy and support teams focused on End-User Support, Infrastructure & Networks and Business Applications. 

Airbnb’s Former Head of Business Technology Joins Alto

In July 2020, Catherine Scott joined Alto as Head of IT, responsible for building and leading a high performing IT team. Previously, Cat spent five years at AirBnB where she acted as the Global Head of Business Technology during their worldwide growth and was pivotal in delivering exceptional technology experiences to employees. With this expertise, and over 20 years experience spanning startups to Fortune 500 Companies, we are excited to officially call her an Altoid! 

We sat down with Scott to learn more about her plan to build Alto’s IT strategy and support teams focused on End-User Support, Infrastructure & Networks and Business Applications. 

Welcome to Alto! What excites you most about recently joining the team? 

Thank you! I’ll start by sharing that I am excited by companies that have a strong mission. This was an important consideration for joining Airbnb.  When contemplating what was next, I knew that this was a primary driver for my next move.  Alto’s mission - to improve the quality of life for everyone - very much resonated with me. 

Aside from that, my conversations with Altoids during the hiring process reflected a sense of passion and humility that I found to be rare in a successful company. There is a culture of really intelligent, driven individuals here that are unpretentious about their accomplishments. 

Likewise, any time I evaluate an opportunity for growth, I assess the impact that I can have based on my experience. Given my background in consulting, startups, and Fortune 500 companies, I found Alto’s goals to be in line with my ability to improve efficiency and help IT mature into being viewed as a critical enabler to our business.

Blog

Catching up with Elnaz Moshfeghian, Alto’s new VP of Strategic Planning & Business Operations

Get to know Jake Moffatt, Engineering Manager on the Alto Assistant Team

Celebrating National Coming Out Day at Alto

Get to Know the Team That Builds Alto's Customer-Facing Apps

Alto Pharmacy Announced as One of Forbes Best Startup Employers

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

How (and Why) We’re Standardizing Our Commit Messages

Airbnb’s Former Head of Business Technology Joins Alto

Help Us Shape the Future of Healthcare

Are You Right for Alto?

How Alto Pharmacy Is Using Tech to Put Patients First

Women Leading the Way

Switch to a better pharmacy.