Expires 04/01/2021

Specialty Pharmacy

We're here to support you through COVID-19 with free home delivery.

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

Alto Pharmacy Technician

Alto Pharmacist

Our mission at Alto is to fulfill medicine’s true purpose — to improve quality of life — for everyone who needs it.

Services that reduce travel and encourage social distancing are now more essential than ever, not only for vulnerable populations but all of us as members of our communities. Alto’s free same-day doorstep delivery ensures you have safe and reliable access to medications in this time of uncertainty. 

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

Alto / Blog

For an inside perspective on sales at Alto, we sat down with Craig Thompson, our Vice President of Sales, to learn about his experience at Alto and his advice for qualified sales professionals looking to join the team.

An Inside Look at a Sales Career with Alto

Why Our Sales Team is Central to Our Mission at Alto

Like so many big ideas, Alto began with a question: what if we reimagined the pharmacy experience to make people happier and healthier? Improvements were begging to be made: not only were most people and providers frustrated and dissatisfied with the status quo,  but medication non-adherence—when people don’t take the medication they’re prescribed—has hovered at 50%. In addition to $300 billion in avoidable medical costs, non-adherence is estimated to cause approximately 125,000 preventable deaths per year in the United States. 

With these problematic statistics in mind, Alto set out to do more than just dispense and deliver medications. Our mission is to fulfill medicine’s true purpose: to improve the quality of life for everyone who needs it. We aim to make our better pharmacy experience available to 100 million people by 2025 and we’ve raised over $350 million—including more than $250 million at the beginning of the year—in pursuit of this goal. 

To reach more people and expand into new markets, we are building a strong, mission-driven sales team to help forge the way. For an inside perspective on sales at Alto, we sat down with Craig Thompson, our Vice President of Sales, to learn about his experience at Alto and his advice for qualified sales professionals looking to join the team.

Can you tell us about your own career path and why you joined Alto?

Prior to joining Alto, I spent about 20 years in the medical device space. Early on, I worked for a few different companies before landing at Abbott Vascular where I started as a sales representative, led trainings across the U.S. as the Director of Medical Education, then pivoted back to become VP of Sales. I always envisioned that my next role would be a bigger version of that position; one where I could swing big and settle in for the long haul. 

What intrigued me about Alto was the size of the market. We spend more than $330 billion on prescription drugs a year in the U.S., but it didn’t seem like anyone was nailing the pharmacy experience, especially from the patient’s perspective. When I met Matt, Alto’s CEO, I was impressed by his patient-centered mission and his humble approach. The opportunity to build something from the ground up really appealed to me. I also loved the idea of working alongside a team of high caliber people with diverse professional backgrounds.

Alto represents a true convergence of healthcare and technology. Moving from medical devices or pharmaceuticals and coming here, you learn new ways to communicate and have access to new technology and resources.  We have our eyes on the future and a vision for how we want to scale. By keeping a strong focus, we’ve more than doubled our revenue each year for the past few years. As we continue to expand into major markets across the U.S., we’re looking to bring in highly talented people with existing relationships to build out our sales team. 

While we've delivered fantastic growth over the last few years, we're still in a phase of evolution where a new member of the team can have a meaningful impact on our organization. This is an ideal opportunity to take part in building something new and to know that as you help build a better business, you’re also helping to improve people’s and healthcare professionals’ lives. Not only have we leveled up the patient experience with our app, but we’re also making the pharmacy experience easier for healthcare professionals. Alto is uniquely suited for those who care about benefiting the stakeholders we work with. It’s genuinely all about the mission.

What makes a successful partnership manager at Alto? 

We’re looking for builders—creative people who can operate in ambiguity and thrive in a startup environment. Working at Alto is an opportunity to build new territories and make a real difference for people. It’s for those who want to create novel solutions rather than work with rails around them. We need innovative people with existing relationships who are motivated by Alto’s mission to improve lives. 

What exciting challenges await a potential team member? 

We're really at the tip of the iceberg as far as the products that we are bringing forward. There's a ton of work to be done as we consider how we can continue to meet the needs of both people and health care professionals. We’re always working to develop services and technology that can help impact adherence rates, improve the overall quality of life for people, and make physicians' lives easier by reducing the burden that exists on their teams from insurance companies. 

There will be a ton of opportunities for people to come in, demonstrate success, and find fulfilling professional paths. One of my visions for the coming year is to develop additional resources dedicated to professional and personal growth and implement programs with specific learning tracks. 

We work cross-functionally and are always open to learning new ways of operating and finding success. If you’re excited by the opportunity to create something new rather than inherit an existing territory, we’d love to hear from you. 

This is an exciting time to join the team at Alto. As we continue to forge new territory, expand into new markets, and develop our specialty areas, we’re already on track to achieve $1 billion in annual recurring revenue by 2021. To maintain this trajectory, we’re looking to grow our team with highly skilled individuals who align with our values and are motivated to create change. There is abundant opportunity to not only achieve success but find fulfillment by working toward a mission that positively impacts people’s lives.  

If you've found yourself considering embarking on a new adventure, we’d be thrilled to have you consider Alto as your next career milestone. Visit our careers page to see if we're actively hiring in your city. If you're not quite ready to make a move, join our talent community and follow us on LinkedIn to stay apprised of upcoming opportunities. 

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.

This fall, we had the opportunity to meet Tiffany Remington and her husband Caleb, who spoke to us about the importance of having a pharmacy partner they could rely on through their own infertility journey.

Fertility Patient Story: Tiffany Shares Her Experience with Alto

How One Couple Navigated Their Infertility Journey

Facing fertility issues can feel like entering completely unfamiliar territory. From deciding when and how to pursue treatment to navigating the ensuing procedures and medication protocols, uncertainties can surface at every turn. However, while no two journeys are completely alike, there is so much to be learned from the many hopeful parents who have traveled the various paths of infertility treatment before. 

This fall, we had the opportunity to meet Tiffany Remington and her husband Caleb, who spoke to us about the importance of having a pharmacy partner they could rely on through their own infertility journey. Read on to learn more about how the process unfolded in Tiffany’s own words and her advice for others going through a similar experience. 

My husband, Caleb, and I love to seek out adventure in almost everything we do. For the past two years, we’ve been living full-time in an RV that we renovated into the coziest home on wheels. Before pursuing our wild dreams of living tiny, we created a one-off event called The Greatest Wedding Ever Donated, where we turned our wedding into a gala and benefit concert and raised $207,000 for charity. 

So what’s next in our books? Starting a family. To our surprise, it took us a year and a half to start our journey of growing our family, and most of the waiting was out of our control. When we had our initial visit with our reproductive endocrinologist back in May of 2019, we thought things were going to happen fast—boom, bam, baby in the utero in one month. We quickly found out how intense the process is and how little we fully understood. All we knew was that we needed help. 

My husband was born with a condition called cystic fibrosis (CF), a genetic condition that creates a thick buildup of mucus in his lungs and other organs of his body. 98% of men with CF are also born infertile due to the absence or underdevelopment of the vas deferens (think of it as the highway for the sperm). After trying to conceive for two years on our own, we had a gut feeling that the lottery win for natural conception was not in the cards. We are a couple affected by male factor infertility.

After choosing a clinic, we had blood work done within the month. We then planned for Caleb’s microTESE, a surgical procedure to extract sperm from the seminiferous tubules of a male’s testes and epididymis. Unfortunately, that was round one of delays. We had to wait five months for an open spot for surgery. The initial disappointment rapidly turned into gratitude knowing that we had more time to fully wrap our head around this process, find a community for support, and educate ourselves in the decisions we would have to make along the way.

In February of 2020, we joyfully celebrated the eleven vials of sperm that were collected and were ready to start our IVF protocol. To ours and the world’s dismay, COVID-19 restrictions were put into place and our clinic shut down in March, just as we were about to begin. Due to Caleb’s health and the nature of the virus, we decided to move our IVF funds back to his medical emergency savings in case something happened. 

For five and a half months, we waited. We finally came to a place of comfort to move forward once our clinic allowed for new patient protocols to resume. We officially started our IVF stimulation protocol for egg retrieval at the beginning of August. After fifteen days of shots, we pulled the trigger and were able to produce seventeen beautiful mature eggs. Of the seventeen eggs, fourteen were fertilized, thirteen made it to Day 3 Blastocysts, four to Day 5 Blastocysts, and two to Day 6. We ended up with a total of six embryos that got sent off for PGS testing. A week later, we found out that of the six embryos, three came back genetically normal.

We wanted to keep the momentum going, so we opted to transfer our first frozen embryo as soon as possible. I had surgery to remove a couple of polyps and by the beginning of October, I was in the clear with a healed uterus, ready to welcome our baby home. With the transfer protocol moving rapidly, I knew I had to find a new pharmacy that I felt like I could rely on. 

During egg retrieval, I ordered from my clinic’s partnered pharmacy without realizing that I had much of a choice otherwise. My medication was delivered to the wrong address, and the idea that it might happen again stressed me out because timing is everything in this process! When speaking with some of my IVF friends, I kept hearing about Alto Pharmacy. I took a deep dive to see what all the “buzz” was about.

I could feel the grin stretch across my face when clicking enter on the URL. The website was already drawing me in. This is a pharmacy? Free delivery, advice, price investigation, and they work with your insurance? I’ve been managing my husband’s medication for years. I know first-hand how time-consuming all of the things that Alto provides can be—it’s a full-time job. This isn't just a pharmacy, it's a care team.

When I saw that Alto would take the burden off my shoulders, I was INSTANTLY sold. No need for spreadsheets, no need to play phone manager while connecting insurance and pharmacies, no need to Google down a rabbit hole. They would take care of all the details and that in itself is priceless.

I had my nurse place my next order with Alto and within the hour I had a text message to my phone prompting me to download the Alto app where I could manage deliveries and medications, connect with a pharmacist, and track my orders. Again, mind blown. An app? For a pharmacy? Can someone bring Alto their crown? One of the best parts is that the delivery windows were only a couple of hours—not like most other pharmacies where you have to wait the entire day to receive your medications. They also have one of their own courier team members HAND-deliver it to you.

Boutique service with savings—I couldn’t be a bigger fan. This whole IVF process can sometimes make you feel like a number. Alto is one of those companies doing it right by honoring you as a human. They show up in your texts. They show up in the app. They show up on the phone. I felt heard and fought for.

If you are walking through this (in)fertility process, or any medical journey for that matter, my advice is: don’t be afraid to advocate for yourself. Speaking as both a caretaker and patient, medicine is often routine and anonymous, and personalized care has not yet been perfected. Pharmacy choice, specifically, matters. Are they reliable? Do they advocate for you as a patient? Can they cut costs? What’s their customer service like? What are patient reviews? Do they deliver on time? You have a choice, even if the options aren’t clear at the start.

The team at Alto is ready to be your partner through it all, from your first cycle to your last. Questions about using Alto? Visit alto.com/fertility or give us a call at 1-800-874-5881. Our team is available 9 am - 9 pm PT Monday - Friday and 10 am - 6 pm PT on weekends. 

To connect with Tiffany and Caleb follow them on Instagram @ustheremingtons. 

Disclosure: Tiffany received medications at no cost from Alto Pharmacy in order to share her opinion about our services. The views expressed are solely her own. 

Fertility Patient Story: Tiffany Shares Her Experience with Alto 

We offer the latest advice on how you can access the medications and services you need while protecting yourself from infection with COVID-19.

Navigating HIV Treatment and Prevention During COVID-19

Living with HIV during the COVID-19 pandemic

It’s been over six months since the first stay-at-home orders swept across the country, and we’re just beginning to replace widespread uncertainty about the coronavirus with real-world data. There’s still much we don’t know about how COVID-19 affects those living with HIV, but researchers are working quickly to glean insights from cases over the past months. 

Though our understanding is continually evolving and the data is limited, experts believe that people with HIV who are receiving treatment have the same risk for COVID-19 as the general population. We do know, however, that people with weakened immune systems are more likely to get severely sick from COVID-19, which underscores the already vital importance of preventing new HIV infections and ensuring access to treatment. 

If you are at risk of HIV infection or living with HIV, we encourage you to not put prevention or treatment on hold. It’s also crucial that you stick to the plan outlined by your doctor as closely as possible, especially by taking your medications correctly and on time. As your pharmacy, we’re here to help you overcome any challenges in maintaining your regimen that may arise. Let’s walk through the latest advice on how you can access the medications and services you need while protecting yourself from infection with COVID-19.

Is COVID-19 illness more severe in people living with HIV?

As we mentioned, when HIV is being treated, it does not seem to increase the risk of infection or severe illness. Those who are living with HIV and not on treatment or virally suppressed, however, may be at greater risk of COVID-19 complications. Additionally, older people living with HIV and those with other underlying health conditions may also be at greater risk of serious illness from COVID-19. It’s important to take precautions to protect yourself from COVID-19 infection by following CDC guidelines, such as wearing a mask, social distancing, and washing hands and high-touch surfaces often. 

We know that people living with HIV are more vulnerable to respiratory infections when their HIV is not well managed. That’s because their weakened immune systems may be unprepared to deal with an invading virus. For this reason, it’s incredibly important to continue your antiretroviral treatment (ART) as prescribed. If you are having difficulty continuing your treatment for any reason, talk with your healthcare provider right away.

What additional precautions should people living with HIV take?

The most important actions you can take for your health are to continue your HIV treatment and avoid potential exposure to the coronavirus. Follow the preventative guidelines outlined by the CDC to protect yourself and others from getting sick. Additionally, you should take the following precautions:

Keep your regular medical appointments and discuss ways you can reduce your risk of exposure to COVID-19 during your visits. Use telehealth services whenever possible; your doctor can advise you on the remote options available to you.

Keep at least a 30-day supply of your HIV medications on hand as well as any other medications or supplies you need to manage your health. If possible, ask for a three-month supply and choose a pharmacy that offers home delivery to avoid spending time in close contact with others while standing in lines. (Alto’s couriers will hand-deliver your medications to your doorstep, so you never have to worry about mail delays either!)

People living with HIV are at a higher risk of serious flu-related complications, make sure all your vaccinations are up-to-date, especially your flu shot.

The CDC recommends maintaining a healthy diet, aiming for 8 hours of sleep every night, and taking steps to reduce stress. 

If you start to feel sick, especially if you have a dry cough, fever, fatigue, and/or a loss of smell or taste, stay at home and contact your doctor immediately so you can determine your next steps. You will need to self-isolate to avoid spreading the coronavirus to others as you await instructions from your doctor. For this reason, we strongly recommend having a plan in place for if you get sick, including keeping 30 days’ worth of medications, food, and other supplies on hand.

How can I get tested for HIV during the COVID-19 pandemic?

It’s as important as ever to know your HIV status. If you’re at risk for HIV, talk to your healthcare provider about your options for getting tested. The CDC has stressed the importance of continued access to HIV testing and encourages people who are at risk for HIV infection to get tested in ways that support social distancing and stay-at-home orders (when they are in place), such as self-testing when possible. They have created this resource that lists self-testing services by state. You can also find in-person testing locations here. 

I’ve lost my insurance. How can I continue to get my HIV medication?

As we face this public health crisis, record numbers of people are also losing their jobs and employer-based coverage. If you’re currently uninsured or cannot afford your out-of-pocket costs, there are resources that can help. HIV.gov puts out this list of toll-free helplines that can help you find programs and services in your state to lower your treatment costs. They also list a variety of federal resources here. 

The AIDS Drug Assistance Program (ADAP), which is part of the Ryan White HIV/AIDS Program was created to help cover the cost of HIV-related prescription medications for people who have limited or no prescription drug coverage. Eligibility may vary by state, so find out more by using the ADAP Directory to identify your local program. 

How can I continue to access PrEP during the COVID-19 pandemic?

If you are at risk of HIV exposure, protecting yourself needs to remain a top priority. PrEP, or pre-exposure prophylaxis, is an HIV prevention method that's available by prescription. We explain more in our article, “All About PrEP for HIV Prevention.”

If you are already taking PrEP, talk to your provider about the possibility of telehealth options for the time being and see if you can get a prescription for a 90-day supply of PrEP. To find an in-person or online provider, visit one of the following websites:
PleasePrEPme.org
Greaterthan.org

If you need help paying for PrEP, there are assistance programs available that can cover the costs. PleasePrEPme.org maintains a comprehensive list of available resources here. 

What are some ways to cope with stress and anxiety right now?

It’s normal to experience heightened emotions during times of stress. And, unfortunately, some of the actions we are taking to protect ourselves, such as social distancing, can negatively impact our emotional well-being. Here are some ways you can protect your mental health and cope with the stress and uncertainty of the COVID-19 pandemic.

Unplug when you need to. It’s important to stay informed, however, the constant cycle of news reports and social media updates can become all-consuming and overwhelming. Take breaks from your devices when necessary and try to focus on reliable news sources and avoid social media accounts and websites that may be spreading rumors or false information.

Find soothing activities and practice them daily. Maybe you turn to a calming classic like meditation when you need to recharge or perhaps nothing makes you happier than whipping up a batch of chocolate chip cookies from scratch. Whatever helps you unwind is good for your emotional well-being and overall health. 

Stay on top of your health and wellness. Stress can disrupt your usual healthy habits. Try to move your body frequently, incorporate healthy foods, and get a full night’s sleep. You may not succeed every day and that’s okay. Just do your best to keep up your healthy habits most of the time. 

Seek help if you need it. If feelings of fear, anger, sadness, worry, or numbness interfere with your responsibilities for several days in a row or if you find yourself turning to unhealthy coping strategies like drugs or alcohol, please reach out for help. The CDC offers this list of free and confidential resources.

We are committed to ensuring you receive your HIV medications safely and on time throughout the COVID-19 pandemic. Our pharmacy locations are fully stocked, our couriers are ready, and our pharmacists can assist with coordinating early refills and longer fills. We offer free, contactless delivery, plus ongoing access to support and advice.  

Reach out to our HIV speciality team at 1 (800) 874-5881 (call/text) or send us a message through our mobile app. We’re available from 9 am - 9 pm PT Monday - Friday and 10 am - 6 pm PT on weekends.

This content is not intended to be a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or another qualified health provider with any questions you may have regarding a medical condition.

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.

You were the Global Head of Business Technology (Products) at Airbnb for 5 years. How did this experience shape your outlook on strategic growth and what was the most important lesson that you learned? 

When I joined Airbnb the IT organization was in its infancy. We were present in 192 countries and yet there were only six people assigned to the global team.  It was imperative to create a global strategy quickly that would both enable the hyper-growth of the company and consider how to scale in a cost effective way.

I think the key takeaway is that IT is everywhere. It's a foundational layer supporting how everything functions. Thinking about IT early in a company’s lifecycle is essential, but above that you have to ensure everything is thought of from a scalable perspective. If we only build for right now there will inevitably be a technical rework later so making sure the IT services are both built for increased volume and still cost effective is important.

Can you share a little bit about your goals at Alto for the remainder of the year? 

Right now I’m very focused on what I would call core/foundational IT (network infrastructure, IT support function, etc.) -- essentially the programs that are the enablers for everyone. I’m also working closely with Alto’s Director of Security to ensure that we continue to protect our patients' data with the utmost level of reliability. 

Next year I’d love to start addressing  how IT can enable more business return on investment. For example, managing and implementing 3rd party applications. Typically, and this was the same at Airbnb, if everyone is going off and buying different, potentially duplicative, applications, we start to leave money on the table and can have disjointed data and compromise security. This is where IT starts to become a case for ROI and business benefit. 

I’ll actually contend that Alto is a forward thinking in recognizing the importance of IT. Because of this, I know I’ll be able to create positive benefits because we’ll be in front of the curve. At the end of the day, if we can grow in a thoughtful manner, we’ll arrive at a place where we’ll have a really high performing IT organization that contributes to the bottom line. 

You know, my motto is to “embrace the adventure.” I love spending time outdoors, whether hiking, skiing, or sailing, so it really resonates in my professional life as well. I feel excited about developing an IT strategy that will ensure high quality services both in our sites and remotely, protect our internal data, maximize productivity of our workforce, and ultimately contribute to the company mission of improving the quality of life for everyone.

The good news is, having done this before, I don’t think there’s anything that’s a surprise yet. During the interview process, I knew that this role would require another ground-up build and that it would require a strategic and thoughtful leader. Having said that, the results are always less about me and more about what the team has been able to do and how we have contributed to Alto’s success.

On that note, how would your prior teams describe you? 

I think, or hope, my team would say that I’m incredibly supportive in removing anything that is keeping them from being able to achieve maximum impact or create maximum value for the company. I define myself as authentic, trustworthy and driven -- and value those qualities in others. I definitely have a high bar for excellence and want my team to be successful at performing but at the same time, I’m also there to help when needed and support their professional development. 

Stylistically I’ve always been a leader where I kind of exist to support others and provide thought leadership. You are nothing without your team. To quote Steve Jobs, "It doesn't make sense to hire smart people and tell them what to do; we hire smart people so they can tell us what to do." This philosophy is one that has always resonated with me. 

How do you feel about technology changing our work culture given the current climate of COVID-19? 

Alto is the first job where I joined having never met a single team member in person. It’s definitely changed things up but I’m pretty comfortable with it at this point. Looking forward though, I think it’s important to consider how we can recreate the “magic” that happens in person when a number of our workforce is remote. 

COVID highlighted the significance of innovative IT related to remote work and collaboration that is essential for everyone. That area of creativity is where I think IT will fundamentally shift how we continue to work and communicate with one another in what may be an increasingly remote workforce. 

Are you working on any passion projects outside of Alto at the moment? 

Yes! I’m very passionate about animals and am currently looking to rescue another dog. Aside from that, I’m recently new to the Tahoe, CA, area so hope to become more embedded in community volunteering. 

My other personal passion project is actually an overhaul remodel on our Tahoe house which has required a fair amount of architecture and engineering for my husband and myself. It’s a fun project that keeps us constantly engaged with one another. 

What would you say to someone interested in joining the Alto team, specifically in a technology driven role? 

Just do it, it’s an amazing opportunity! I believe so strongly in what Alto is doing. If you ever have an opportunity to work for a company that is founder-led you should make it happen. There is a palpable passion that resonates throughout a company when the founders are present. It’s an experience worth doing because it creates a belief and excitement around the company that might not happen otherwise. 

For more information on Scott, or to connect with her directly, reach out via LinkedIn. If you have any questions about Alto, or are interested in joining our team, please visit alto.com/careers. 

Airbnb’s Former Head of Business Technology Joins Alto 

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.

Blog

An Inside Look at a Sales Career with Alto

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

Fertility Patient Story: Tiffany Shares Her Experience with Alto

Navigating HIV Treatment and Prevention During COVID-19

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

Airbnb’s Former Head of Business Technology Joins Alto

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

How Alto Saves You Money on Prescriptions

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

Building an Engineering Career at Alto

Alto's Head of Talent Shares His Personal Health Journey

Why a Software Engineer Turned Down 8 Other Offers to Join the Alto Team

Switch to a better pharmacy.