# Strava Engineering

Engineers building the home for your active life. - Medium

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Summer at my dream company!

DevFeed: [Summer at my dream company!](<https://devfeed.tech/articles/summer-at-my-dream-company-66944.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/summer-at-my-dream-company-a7c46aac76fe?source=rss----89d4108ce2a3---4>)

Author: Om Kamath

Published: 2026-10-07T16:01:02Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Sports](<https://devfeed.tech/topics/sports.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [company](<https://devfeed.tech/tags/company.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [international-student](<https://devfeed.tech/tags/international-student.md>), [internship](<https://devfeed.tech/tags/internship.md>), [internship-experience](<https://devfeed.tech/tags/internship-experience.md>), [internships](<https://devfeed.tech/tags/internships.md>), [interview](<https://devfeed.tech/tags/interview.md>), [process](<https://devfeed.tech/tags/process.md>), [recruiting](<https://devfeed.tech/tags/recruiting.md>), [run](<https://devfeed.tech/tags/run.md>), [running](<https://devfeed.tech/tags/running.md>), [strava](<https://devfeed.tech/tags/strava.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

The author describes landing a Strava AI/ML Platform Engineer internship after applying during a 48-hour posting window announced a week ahead. Recruiters replied 3-4 weeks later; interviews covered technical problem-solving, resume discussion with a hiring manager, and HR logistics. The author says recruiting provided specific preparation guidance and describes the technical interview as collaborative, though interview formats may vary by team. In the role, they worked across AI models, server engineering, and clients, improving the LLM evaluation pipeline and handling maintenance tickets and ambiguous production work. The account highlights weekly activity time, team learning sessions, executive access, and a small intern cohort; the author found the summer both fun and productive.

### Source excerpt

Here's how the last few months have actually looked for me: apply, tailor, keywords, cold mail, referral, repeat. For the first few months of this year, this is all that was going through my mind. Countless applications and resumes filled with a variety of uncertainties. Mental health -- well, what's that? Thanks to a few people I kept pushing through. What also kept me sane? Running. Like a literal lunatic, I ran. Cold? Hot? Raining? Snowing? Wore my socks, put on my shoes and off I was. Something that helped me with my consistency was the run club near my grad school campus. (Shoutout to the Roosevelt Island Run club) Every Tuesday at 7pm. I was there. Started off with 10:30mins/mile pacing group, soon advanced to the 08:30mins/mile. What stayed consistent along with my running is tracking my workouts and runs on Strava and that's exactly where I ended up interning at! Uncanny coincidence -- this was the title for my final presentation. The Application Process Unlike most other companies that have their internship postings open for months, Strava does it differently. The posting is open for just 48 hours. They are kind enough to let everyone know a week in advance the exact days it will be opened up. This has two benefits: Only interested candidates are likely to apply. If you apply, your resume is more likely to be reviewed. Since I had been following one of the recruiters at Strava on LinkedIn, I had set a reminder for the posting date (usually in the month of February). The day arrived and I applied. The Interview Process I heard back from the recruiters 3-4 weeks after applying for the internship. There were 6 internship roles ranging from Data and AI roles to PM roles. I had applied for the AI/ML position. The overall process is very lean with just 3 rounds of interviews: Technical Round Hiring Manager Round HR Round I had never expected to hear back and it came as a pretty big surprise to me. After being a part of countless interviews, I was quite numb to it (

## A Summer on the Achieve Team

DevFeed: [A Summer on the Achieve Team](<https://devfeed.tech/articles/a-summer-on-the-achieve-team-62827.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/a-summer-on-the-achieve-team-dabed37298f7?source=rss----89d4108ce2a3---4>)

Author: Tanaka Makoni

Published: 2026-09-30T16:01:02Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [implementation](<https://devfeed.tech/topics/implementation.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apple-watch](<https://devfeed.tech/tags/apple-watch.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [comes](<https://devfeed.tech/tags/comes.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experience](<https://devfeed.tech/tags/experience.md>), [extension](<https://devfeed.tech/tags/extension.md>), [framework](<https://devfeed.tech/tags/framework.md>), [getting](<https://devfeed.tech/tags/getting.md>), [glance](<https://devfeed.tech/tags/glance.md>), [intern](<https://devfeed.tech/tags/intern.md>), [internships](<https://devfeed.tech/tags/internships.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [strava](<https://devfeed.tech/tags/strava.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Strava's widgets fetch and display current activity data despite running only when iOS requests a refresh: each iOS widget uses a timeline provider to query Strava's APIs, then caches successful results so it can show the last good snapshot if a later fetch fails. The intern worked on lock screen and performance prediction widgets, and on expanding goal tracking on Apple Watch while migrating complications from deprecated ClockKit to WidgetKit. Because watchOS restricts independent background network requests, the watch widgets use a different design: the authenticated watch app fetches goals, writes a snapshot to shared storage, and signals the widgets, which read and render it without network access. Performance prediction widgets were in internal testing at the time described.

### Source excerpt

As a subscriber on Strava, a lot of value comes from access to the Progress tab which is Strava's home for tracking activity metrics, goals and performance over time. This summer, as a Software Engineering intern, I worked with the team behind the Progress Tab to enhance this surface to answer a specific question: how much of that experience could move beyond the app itself, out onto the other iOS surfaces athletes glance at all day? Picture of me and my mentorGetting Strava Off the Screen: Widgets Today Strava ships goal and streak widgets for the home screen. My work this summer centered on extending that ecosystem to new widget families in line with iOS' latest updates. I worked on building lock screen widgets, a new performance prediction widget, and bringing widget support to the Apple watch app. Three things motivated the investment. Expanding presence -- getting Strava's metrics in front of athletes without asking them to open the app. Subscriber value -- surfacing the kind of data (goal progress, performance predictions, streaks) that makes a subscription feel worth paying for. Active moments -- turning a passive glance into nudges for users to be more active. What a widget actually is A widget is a small, glanceable UI extension that lives outside your app. It shows you something at a glance without making you open the app. But it's also a separate program with its own life. It can't see inside the app, can't reuse the app's credentials, and can't reach the app's data. Nor does it run continuously. Instead, it renders a snapshot of your data, hands that snapshot to the system, and goes back to sleep. The operating system decides when to wake it up and ask for a fresh version, and it doesn't hand out unlimited wake-ups. So the real engineering problem is: how do you get accurate, current data into a small program that's asleep most of the time and can't directly retrieve it from the app? Apple's answer is WidgetKit, a single framework that now spans the home sc

## My Summer at Strava

DevFeed: [My Summer at Strava](<https://devfeed.tech/articles/my-summer-at-strava-58892.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/my-summer-at-strava-375656e322b6?source=rss----89d4108ce2a3---4>)

Author: Connor Davis

Published: 2026-09-23T16:01:03Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [alex](<https://devfeed.tech/tags/alex.md>), [code](<https://devfeed.tech/tags/code.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [data](<https://devfeed.tech/tags/data.md>), [data-platform](<https://devfeed.tech/tags/data-platform.md>), [error](<https://devfeed.tech/tags/error.md>), [innovative-thinking](<https://devfeed.tech/tags/innovative-thinking.md>), [intern](<https://devfeed.tech/tags/intern.md>), [internship](<https://devfeed.tech/tags/internship.md>), [internships](<https://devfeed.tech/tags/internships.md>), [introduction](<https://devfeed.tech/tags/introduction.md>), [learning](<https://devfeed.tech/tags/learning.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [offsite](<https://devfeed.tech/tags/offsite.md>), [outdoors](<https://devfeed.tech/tags/outdoors.md>), [perspectives](<https://devfeed.tech/tags/perspectives.md>), [platform](<https://devfeed.tech/tags/platform.md>), [production](<https://devfeed.tech/tags/production.md>), [project](<https://devfeed.tech/tags/project.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

Strava intern Connor Davis replaced Drift's failure-prone AWS Lambda decoding path with a Snowflake Python UDF, moving Thrift decoding into the warehouse where the data already resides. The old Lambda failed when decoded jobs exceeded a size threshold; the new design loads Thrift schemas and UDF logic from an S3 stage and converts encoded data to JSON within SQL queries. Davis selected this option after weighing an SQS-buffered Lambda and a Kubernetes service, citing fewer external calls and less infrastructure to maintain. After working around third-party parser bugs and fixing a null-handling mismatch, he validated the replacement against the old service on live data, used two stakeholder-approved canary cutovers with rollback plans, then migrated callers in stages before decommissioning Lambda. He reports that tens of thousands of recent failures fell to zero on rerun and that the pipeline now decodes more than 450 million rows daily. The account also describes an intern hackathon project adding natural-language-assisted filters for Strava activity search.

### Source excerpt

Introduction Hi, I'm Connor Davis, a rising senior at the University of Michigan studying Computer Science and Mathematics. This summer I was an intern on the Data Platform team at Strava in San Francisco. I grew up surrounded by sport and a passion for the outdoors. Being a skier, skateboarder, surfer, and mountain biker has required the analytical creativity I've gained from Computer Science. Attempting new tricks or tackling uncharted obstacles demands innovative thinking and approaching situations from different perspectives to derive a solution. For instance, in surfing, I constantly manipulate the pop-up timing on a wave since each one is unique. In learning to kickflip on my skateboard, I procedurally experimented with different foot positions and evaluated which worked better than others. Thus, a disciplined mentality is rewarded. The adrenaline rush I get from sports is exhilarating. The process of finally landing a trick after hours of repetition is euphoric, just like successfully running your code. This summer, I leaned on this process that action sports had taught me to solve a real production problem at Strava. My Project I walked into a scene of chaos on my first day. It was the week of the horizontal team offsite, where many Stravioli from other offices across the world came to SF HQ to connect. Throughout my internship, I've had the privilege of being able to consult the experiences and perspectives of people with many different backgrounds, and it felt very special to be a part of this off the bat. Also, on my very first day, my mentor Alex sent me an error message from our Drift service. How daunting. At Strava, many of our microservices communicate using Thrift, which is a protocol that encodes data into a compact binary format to make interservice communication faster and more efficient. This also means that data received looks like a jumble of symbols and numbers, which is not entirely useful for a human trying to make sense of it. Drift is the

## Rain: A key-value store for Strava's scale

DevFeed: [Rain: A key-value store for Strava's scale](<https://devfeed.tech/articles/rain-a-key-value-store-for-strava-s-scale-26575.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/rain-a-key-value-store-for-stravas-scale-7f580f5b4848?source=rss----89d4108ce2a3---4>)

Author: Derick Yang

Published: 2025-01-24T18:02:11Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [dataset](<https://devfeed.tech/topics/dataset.md>), [Big data infrastructure](<https://devfeed.tech/topics/big-data-infrastructure.md>), [Database](<https://devfeed.tech/topics/database.md>), [Apache Cassandra](<https://devfeed.tech/topics/cassandra.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>)

Tags: [batch](<https://devfeed.tech/tags/batch.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cassandra](<https://devfeed.tech/tags/cassandra.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data](<https://devfeed.tech/tags/data.md>), [data-pipeline](<https://devfeed.tech/tags/data-pipeline.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [datasets](<https://devfeed.tech/tags/datasets.md>), [datastores](<https://devfeed.tech/tags/datastores.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [developers](<https://devfeed.tech/tags/developers.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [features](<https://devfeed.tech/tags/features.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [maps](<https://devfeed.tech/tags/maps.md>), [rain](<https://devfeed.tech/tags/rain.md>), [scale](<https://devfeed.tech/tags/scale.md>), [spark](<https://devfeed.tech/tags/spark.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

Strava's Geo team needs to serve large, immutable datasets from recurring batch pipelines for products such as routing, heatmaps, and Strava Metro. The excerpt identifies a tension between large batch writes and read performance, the cost of keeping rarely accessed data in production databases, and inflexible externally defined schemas. Previously, PalDB served small side datasets, but larger files had to be downloaded from S3 for each service deployment, making deployments take over 20 minutes and duplicating substantial data in memory across service instances. Cassandra could handle batch writes, though the excerpt cuts off before describing its limitations or Rain's design and results.

### Source excerpt

Much of our heatmaps are built on batch data outputs stored in Rain At Strava, we love maps -- some of our most loved features are nestled on map surfaces. My team, the Geo team, is focused on building and improving these products. On the Geo and Metro teams, we tend to work with large datasets: aggregations of open source map data via OpenStreetMaps, GPS data points from uploaded activities, third-party datasets for properties like elevation, and beyond. This aggregated dataset eventually turns into Geo features we know and love, like the global heatmap, Strava Metro, the routing product, route suggestions, elevation profiles, and points of interest. We perform these data aggregations in a rather hefty data pipeline, run on a regular cadence to ensure we're serving up-to-date geo data. One of the Geo team's key challenges is efficiently serving large, immutable (write-once, read-many) datasets produced by our pipeline. This is particularly hard for compute-intensive use cases like routing, where: Write-Optimized vs. Read-Optimized Conflict: Traditional read-optimized data stores struggle with large batch writes without impacting read performance or introducing significant operational complexity. Cost Constraints: Storing rarely accessed datasets in production databases can be prohibitively expensive -- especially for projects like Strava Metro, which are accessed sporadically. Schema Complexity: Defining schemas externally from the service that uses them can be costly and inflexible for developers. Previously Our previous solution to large writes used a combination of datastores: PalDB and Cassandra. PalDB is a binary data format ideal for small datasets. The README states that it is optimized for "side data", relatively small datasets you read "in passing" on your service. PalDB is unideal, however, for larger datasets. In our case, since each service deployment required downloading the key-value file from S3, our deployments were taking upwards of twenty minutes. S

## Scaling Challenge Leaderboards for Millions of Athletes

DevFeed: [Scaling Challenge Leaderboards for Millions of Athletes](<https://devfeed.tech/articles/scaling-challenge-leaderboards-for-millions-of-athletes-26576.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/scaling-challenge-leaderboards-for-millions-of-athletes-9ab09ef01381?source=rss----89d4108ce2a3---4>)

Author: Mike Kasberg

Published: 2024-01-18T17:01:41Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Sports](<https://devfeed.tech/topics/sports.md>)

Tags: [challenge](<https://devfeed.tech/tags/challenge.md>), [leaderboards](<https://devfeed.tech/tags/leaderboards.md>), [programming](<https://devfeed.tech/tags/programming.md>), [relational-databases](<https://devfeed.tech/tags/relational-databases.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [sql](<https://devfeed.tech/tags/sql.md>), [system-design-concepts](<https://devfeed.tech/tags/system-design-concepts.md>)

### AI overview

Strava replaced its Redis based challenge leaderboards after participation reached 1.2 million athletes and inefficient access patterns threatened reliability. In particular, calling HGETALL on a hash containing every challenge member required work proportional to leaderboard size; bursts of challenge completions could overload Redis and disrupt other queries. The new Gauntlet system uses MySQL for durable storage and indexed leaderboard operations. Because counting all scores above an athlete's score still scales linearly, it caches scores at spaced ranks, finds the nearest better cached score, then counts only the bounded number of entries between that point and the athlete's score. Batched updates maintain these cached ranks, with occasional rebalancing. Strava dark launched writes before exposing leaderboards, then tested the interface internally before enabling athlete facing challenges. The article reports a country leaderboard load dropping from over 40 seconds to under 250 ms in one comparison, with average response time more than ten times faster. The excerpt does not provide details beyond the described design and results.

### Source excerpt

Strava challenges offer a fun way for athletes to compete against themselves and others! Back in 2020, our legacy challenge leaderboard system was running into bottlenecks and scalability problems on a regular basis, and we often found ourselves putting out fires to keep the system stable. In late 2020 and early 2021, I worked on a project to replace the old leaderboard system with a new one that could handle a much larger number of athletes competing in challenges. This blog post is about that project. I drafted most of this post when the project wrapped up in 2021, but didn't get it published before I went on paternity leave -- and then I forgot about it. I think the project was interesting and worth sharing, so I'm glad I finally remembered my draft (three years later 🫣) and found some time to put in the finishing touches and get it published! Enjoy! In January 2020, Strava's monthly 5K running challenge attracted more than half a million participants for the first time. This was a big milestone, doubling the participation from just a year earlier when we had only a little more than 250,000 participants in the January 2019 5K challenge. But we weren't done growing! Just 5 months later, our challenge participants doubled again and we broke 1 million participants in a monthly challenge for the first time with the May 2020 5K, where 1.2 million Strava athletes participated! In less than a year and a half, the number of athletes participating in Strava's monthly challenges had quadrupled. As you can imagine, the increase in challenge participation came with a significant increase in load on our systems. In particular, we were beginning to approach the limits of what our existing challenge leaderboard system could handle. If the number of challenge athletes participating in our monthly challenges were to double again, our challenge leaderboard system wouldn't handle it well. We needed to do something to improve the way our leaderboard system scaled with more challenge

## AN EVENTFUL SUMMER AT STRAVA

DevFeed: [AN EVENTFUL SUMMER AT STRAVA](<https://devfeed.tech/articles/an-eventful-summer-at-strava-26571.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/an-eventful-summer-at-strava-5692882e5f4f?source=rss----89d4108ce2a3---4>)

Author: Bisman Sodhi

Published: 2024-01-08T20:19:46Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [etl](<https://devfeed.tech/topics/etl.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [elt](<https://devfeed.tech/topics/elt.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [airflow](<https://devfeed.tech/tags/airflow.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [amazing](<https://devfeed.tech/tags/amazing.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-airflow](<https://devfeed.tech/tags/apache-airflow.md>), [aws](<https://devfeed.tech/tags/aws.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [cadence](<https://devfeed.tech/tags/cadence.md>), [california](<https://devfeed.tech/tags/california.md>), [collect](<https://devfeed.tech/tags/collect.md>), [computer](<https://devfeed.tech/tags/computer.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [craft](<https://devfeed.tech/tags/craft.md>), [created](<https://devfeed.tech/tags/created.md>), [daily](<https://devfeed.tech/tags/daily.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-platforms](<https://devfeed.tech/tags/data-platforms.md>), [internships](<https://devfeed.tech/tags/internships.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

A Strava software engineering intern built a daily Apache Airflow pipeline to move Snowplow events that fail schema validation from gzip files in S3 into Snowflake, replacing their temporary storage in Elasticsearch. The pipeline decompresses the files, stages data before production loading so S3 failures do not leave partial production data, and creates six SQL views tailored to the different bad-event schemas. The views reduce duplicated data and query latency; a Tableau dashboard displays event counts and metrics. The account also describes a JAMS hackathon project integrating Spotify with Strava and storing athlete, activity, and song information.

### Source excerpt

Hi my name is Bisman and I studied Computer Science at University of California, Santa Barbara. During summer of 2022, I had the most amazing experience working as a Software Engineer Intern on Strava's Data Platform Team. In the first fews weeks, I learned the tools my team uses and then spent the rest of the time working on my project. TRACKING BAD EVENTS For my major summer project, I created a data pipeline that pulls user behavior data out of external storage and persists it in our data warehouse. Strava uses a service called Snowplow to collect this user behavior data, like loading a club page or uploading a profile photo. Sometimes, this data fails to match the schema that we've set, and a piece of data that fails this schema validation is called a bad event. Previously, these bad events were temporarily stored in an Elastic Search. Persisting this data in Snowflake, our data warehouse, makes it accessible to a wider audience. It also makes it easier to incorporate the bad events data with other services used at Strava. To start my project, I created a directed acyclic graph in Apache Airflow, a scheduling framework, using python that extracts bad events data from the S3, AWS's storage service, buckets on a daily cadence. This data was stored as gzip files on S3 which I decompressed and stored the data as JSON blobs. As I was working with billions of rows of data, it was important to maintain data integrity and take measures in case data failed to load from S3. Therefore, I loaded data into a staging table in Snowflake. The staging table ensured that if loading from S3 failed, the production table would remain untouched. This data was then loaded into the production table free of any partial data. After all the data was loaded into the production table, I created six view tables because there were six different types of bad events stored in the production table. I collaborated with our stakeholders -- data analysts -- throughout this process to craft tables bas

## Ac(count)ing for Scale

DevFeed: [Ac(count)ing for Scale](<https://devfeed.tech/articles/ac-count-ing-for-scale-26569.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/ac-count-ing-for-scale-becf9c27b104?source=rss----89d4108ce2a3---4>)

Author: jana

Published: 2023-04-26T18:23:14Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [async](<https://devfeed.tech/topics/async.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-platform](<https://devfeed.tech/tags/api-platform.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [approach](<https://devfeed.tech/tags/approach.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [count](<https://devfeed.tech/tags/count.md>), [limit](<https://devfeed.tech/tags/limit.md>), [limits](<https://devfeed.tech/tags/limits.md>), [number](<https://devfeed.tech/tags/number.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [partners](<https://devfeed.tech/tags/partners.md>), [scale](<https://devfeed.tech/tags/scale.md>), [strava](<https://devfeed.tech/tags/strava.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Strava needed to enforce per application limits on athlete authorizations, but counting refresh token rows on every authorization would be too costly for partners with millions of connected athletes. The team considered an event-driven counter, which would need safeguards against duplicate or missed events and a complex baseline backfill, and probabilistic recounting, which is simpler but leaves large counts staler. They chose probabilistic recounting: smaller applications are recounted on every token event, while larger ones are sampled at configurable rates, with missing counts computed when first encountered. A test count query took about 16 seconds, so recounts ran asynchronously; production initially hit database timeouts, which were raised. After tuning the sampling rate, monitoring showed no significant change in server latency or database CPU. The excerpt says authorization enforcement was the next step, but does not describe its implementation.

### Source excerpt

Tens of thousands of API applications interact with Strava's publicly available API, from small projects whose only users are the developers who created them to larger partners like Garmin, Zwift, Wahoo, or Peloton, who upload thousands of activities to Strava daily on our athletes' behalf. Recently the API & Platform team undertook a project to redefine the way that Strava supports API applications and allows them to interact with Strava data (read more about the updated Developer program here). As part of the effort to redefine the management of API applications, a main requirement of the project asked that we be able to assign and enforce a limit to the number of athletes who are allowed to authorize an application on their behalf, what we called an application's athleteCapacity. On creation of a new application, the default athleteCapacity is a single athlete -- the application owner. Developers can subsequently apply to have their limits increased. In order to enforce the assigned athleteCapacity we needed to know how many athletes had authorized any given API application to read and write data to their Strava account, what we termed as an application's connectedAthletesCount. When a new athlete attempts to authorize an application on their behalf (as pictured below), we wanted to be able to ascertain whether the authorization would cause the connectedAthletesCount to exceed its athleteCapacity. The prompt shown to an athlete to request their permission to authorize an external application to connect to Strava on their behalf. We planned to perform the check of an application's `connectedAthletesCount` against its `athleteCapacity` on click of "Authorize". If authorization would cause the application to exceed its athleteCapacity, we would prevent the athlete from authorizing. Otherwise we would allow authorization to proceed. Our use of the OAuth2.0 standard for external access to our API gave us an easy proxy for determining the connectedAthletesCount. As part

## Searching for Success at Strava

DevFeed: [Searching for Success at Strava](<https://devfeed.tech/articles/searching-for-success-at-strava-26577.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/searching-for-success-at-strava-22b9bf205dbf?source=rss----89d4108ce2a3---4>)

Author: Navika Budhraja

Published: 2022-11-15T17:01:28Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [also](<https://devfeed.tech/tags/also.md>), [am](<https://devfeed.tech/tags/am.md>), [android](<https://devfeed.tech/tags/android.md>), [away](<https://devfeed.tech/tags/away.md>), [base](<https://devfeed.tech/tags/base.md>), [based](<https://devfeed.tech/tags/based.md>), [basketball](<https://devfeed.tech/tags/basketball.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [code](<https://devfeed.tech/tags/code.md>), [computer](<https://devfeed.tech/tags/computer.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [craft](<https://devfeed.tech/tags/craft.md>), [develop](<https://devfeed.tech/tags/develop.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [environment](<https://devfeed.tech/tags/environment.md>), [internships](<https://devfeed.tech/tags/internships.md>), [micro-frontends](<https://devfeed.tech/tags/micro-frontends.md>), [react](<https://devfeed.tech/tags/react.md>), [searching](<https://devfeed.tech/tags/searching.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

A Strava web engineering intern migrated the My Routes page from the Ruby on Rails monolith Active to a React microfrontend, then added filtering and search for saved routes. The migration involved setting up and federating the microfrontend behind a feature flag, building the UI from Figma designs, and replacing placeholder content with real user data fetched through GraphQL. The intern describes GraphQL integration as new but manageable with pair programming, documentation, and help from server engineers. The project also included bug fixing and Jest UI tests. The excerpt presents onboarding across Active and the web monorepo, React practice, and team support as useful parts of completing the work during a 12-week internship.

### Source excerpt

Me and my mentors Patrick & NomnomsIntroduction Hi, my name is Navika Budhraja and I'm a rising senior at UC San Diego studying Computer Science. This summer I was a web-frontend engineering intern on the Athlete Services team and consequently, got to learn a lot about how to develop athlete-facing products! During my internship, I worked with 3 other interns, Emily (Server), Sahil (iOS), and Ryan(Android), on a project to add filtering and searching logic to athlete's saved routes, which in my case, meant working on the My Routes page on the web. "Old" My Routes that I would be improving Like the paths of many Strava routes, adding this feature on the web was not going to be a straightforward process. As you may already know, Strava is currently in the process of moving code out of their Ruby on Rails monolith called Active to React-based frontends. Since the code for the current My Routes page lives in active, I was also tasked with migrating the page from active to a React microfrontend before adding filtering/search logic. 😱...My Face exactly when I first read my project description, especially with super rusty React skills and no conception of what a microfrontend was (was it like a tiny frontend or like a craft, hipster frontend sort of like a microbrew?). However, what I came to learn is that when you work in an incredibly supportive and encouraging environment, the process of rolling out a requested feature in just 12 weeks with no experience isn't actually as daunting as it sounds. In the spirit of the Warriors winning the championship earlier this summer (Yes, I am still riding the high), I will break down these past 12 weeks in terms of quarters of a basketball game! First Quarter: Onboarding & Jams Although I wanted to jump in and start working on a project right away, I first had to get acclimated to a new code base, actually 2 new code bases: active (the monolith) and web (the monorepo where my microfrontend will live). By fixing some minor bugs on the w

## A Taste of Pakora

DevFeed: [A Taste of Pakora](<https://devfeed.tech/articles/a-taste-of-pakora-26568.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/a-taste-of-pakora-cf3b5de261ec?source=rss----89d4108ce2a3---4>)

Author: Avery Dunn

Published: 2022-11-01T16:02:01Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [monolithic-architecture](<https://devfeed.tech/topics/monolithic-architecture.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Code Modularity](<https://devfeed.tech/topics/code-modularity.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [company-culture](<https://devfeed.tech/tags/company-culture.md>), [computer-science](<https://devfeed.tech/tags/computer-science.md>), [database](<https://devfeed.tech/tags/database.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [intern](<https://devfeed.tech/tags/intern.md>), [internship](<https://devfeed.tech/tags/internship.md>), [internships](<https://devfeed.tech/tags/internships.md>), [microservice-architecture](<https://devfeed.tech/tags/microservice-architecture.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [modules](<https://devfeed.tech/tags/modules.md>), [monolith](<https://devfeed.tech/tags/monolith.md>), [rails](<https://devfeed.tech/tags/rails.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [ruby-on-rails](<https://devfeed.tech/tags/ruby-on-rails.md>), [scala](<https://devfeed.tech/tags/scala.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

Strava is transitioning from a large Ruby on Rails monolith, which handles its user interface, business logic, and database access, to Scala microservices. The excerpt describes microservices as separate but cooperating modules: teams can focus on smaller areas, depend less on one another, and keep project work contained, while coordinating on broader concerns when needed. The author says this improves developer experience and aligns with the API's evolution from REST to GraphQL. The excerpt ends as it begins explaining API terminology, so it does not provide further transition details.

### Source excerpt

My name is Avery Dunn and I am a rising master's student at Washington University in St. Louis studying computer science. For the past 12 weeks, I have been a software engineering intern on the API & Platform pod of the Foundation team. I am an active Strava user and have been for approximately 3 years with my favorite activity being running. Some other activities I enjoy are playing the piano, reading novels, or skiing (more of a luxury rather than a hobby). My internship at Strava has been a wonderful experience to help me learn, grow, and develop into becoming a more well-rounded, conscientious software engineer. Whether it was working with a recent hire or seasoned "Stravioli," the positive and ambitious company culture shined brightly throughout the course of the summer. In Transition From a Monolithic to Microservice Architecture Strava currently maintains a code monolith-a huge Ruby on Rails codebase that controls the user interface, business logic, and database access. For a growing company like Strava and the continuous development of ideas being made into new features, a code monolith doesn't make for a great developer experience. Trying to parse through a massive codebase and making sure that all the moving parts are in order so that a typo that was somehow glossed over can successfully be changed makes me a little dizzy, personally. The developers at Strava thought so too, and decided to embark on a transition from the Ruby on Rails singular software application to Scala microservices. Over the course of my internship, I gained insight into the process of restructuring a singular software application into Scala microservices and the benefits of that result. Scala microservices can be thought of as modules that work together but separately. They encourage diversification of teams such that each team has less of a dependence on one another like they would for a monolithic codebase. Figure 1: Comparison of a monolithic codebase architecture versus distribut

## Personal Heatmaps

DevFeed: [Personal Heatmaps](<https://devfeed.tech/articles/personal-heatmaps-26574.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/personal-heatmaps-f51d15a0db2b?source=rss----89d4108ce2a3---4>)

Author: J Evans

Published: 2022-10-28T21:15:46Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [Algorithms](<https://devfeed.tech/topics/algorithms.md>), [Image](<https://devfeed.tech/topics/image.md>), [Google Maps](<https://devfeed.tech/topics/google-maps.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [algorithm](<https://devfeed.tech/tags/algorithm.md>), [color](<https://devfeed.tech/tags/color.md>), [cycling](<https://devfeed.tech/tags/cycling.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [flat](<https://devfeed.tech/tags/flat.md>), [gis](<https://devfeed.tech/tags/gis.md>), [google](<https://devfeed.tech/tags/google.md>), [google-maps](<https://devfeed.tech/tags/google-maps.md>), [gps](<https://devfeed.tech/tags/gps.md>), [gradient](<https://devfeed.tech/tags/gradient.md>), [grid](<https://devfeed.tech/tags/grid.md>), [heatmap](<https://devfeed.tech/tags/heatmap.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [map](<https://devfeed.tech/tags/map.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [projection](<https://devfeed.tech/tags/projection.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [running](<https://devfeed.tech/tags/running.md>), [strava](<https://devfeed.tech/tags/strava.md>), [surface](<https://devfeed.tech/tags/surface.md>), [tiling](<https://devfeed.tech/tags/tiling.md>), [traversal](<https://devfeed.tech/tags/traversal.md>), [unique](<https://devfeed.tech/tags/unique.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

### AI overview

Strava's Personal Heatmap overlays an athlete's GPS activity on an interactive map, with frequently traversed paths shown brighter. It uses the Mercator projection and 256x256 pixel map tiles so map sections can be rendered and served during zooming and panning. Each zoom level subdivides tiles into four: level 0 shows the planet in one tile, level 1 in four, and the scheme continues to level 20, where a tile covers roughly a house-sized area. The excerpt introduces separate map and activity-heat image components but ends before explaining how they are generated.

### Source excerpt

This post discusses the algorithm behind Personal Heatmap, one of Strava's most acclaimed subscriber features. Product Overview The Personal Heatmap feature has been around in some form since 2015, but we gave it a major overhaul in 2020. For those unfamiliar, the heatmap is an aggregated view of an athlete's GPS-enabled activities on Strava. Activity data is rendered onto a map according to path traversal frequency; the more an athlete runs on a road, the brighter -- i.e. "hotter" -- that road shows up on the map. The result is a beautiful color gradient displaying the intricate web of past activities, unique to each athlete. The Personal Heatmap is displayed on an interactive world map, also known as a slippy map. Athletes can seamlessly zoom in and out or pan around to arbitrary views of the map, and their activity heat stays displayed the entire time. To enable this, we must provide a scheme for rendering and serving subsections of the world map on the fly. Enter map tiling. Mercator Projection & Map Tiling Map tiling is the practice of subdividing a map into many discrete images that can be stitched together and rendered as a single image in real-time during map navigation. The first step in choosing a tiling scheme is picking what world map to use. Enter, the Mercator Projection, the most commonly used projection of Earth as a flat, rectangular surface. We use this projection in all of our mapping products, including heatmaps. https://medium.com/media/d9e120d13950dd0f1bb4ee14108aa9a9/href Now, imagine a grid overlaying the Mercator projection. Each grid section is known as a tile, a pixel image with resolution 256x256. Every tile has an associated zoom level, and tiles are defined recursively according to this zoom level. A tile at a given zoom level can be subdivided into four equal sized tiles at a next zoom level. For example, Zoom level 0 displays the entire planet in a single 256x256 pixel image. Zoom level 1 displays the world in four 256x256 pixel images.

## Opportunity Arises From the Most Unexpected

DevFeed: [Opportunity Arises From the Most Unexpected](<https://devfeed.tech/articles/opportunity-arises-from-the-most-unexpected-26573.md>)

Original publisher: [Read original article](<https://medium.com/strava-engineering/opportunity-arises-from-the-most-unexpected-614e9e13dcb9?source=rss----89d4108ce2a3---4>)

Author: Ryan Paragas

Published: 2022-10-25T16:01:27Z

Content type: article

Language: en

Sources: [Strava Engineering](<https://devfeed.tech/sources/strava-engineering.md>)

Topics: [implementation](<https://devfeed.tech/topics/implementation.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [experience report](<https://devfeed.tech/topics/experience-report.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [Bootcamp](<https://devfeed.tech/topics/bootcamp.md>), [Sports](<https://devfeed.tech/topics/sports.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [3](<https://devfeed.tech/tags/3.md>), [android](<https://devfeed.tech/tags/android.md>), [background](<https://devfeed.tech/tags/background.md>), [books](<https://devfeed.tech/tags/books.md>), [children](<https://devfeed.tech/tags/children.md>), [class](<https://devfeed.tech/tags/class.md>), [classes](<https://devfeed.tech/tags/classes.md>), [claude](<https://devfeed.tech/tags/claude.md>), [college](<https://devfeed.tech/tags/college.md>), [created](<https://devfeed.tech/tags/created.md>), [delegates](<https://devfeed.tech/tags/delegates.md>), [designs](<https://devfeed.tech/tags/designs.md>), [develop](<https://devfeed.tech/tags/develop.md>), [development](<https://devfeed.tech/tags/development.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [easy](<https://devfeed.tech/tags/easy.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [environment](<https://devfeed.tech/tags/environment.md>), [events](<https://devfeed.tech/tags/events.md>), [internships](<https://devfeed.tech/tags/internships.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [route](<https://devfeed.tech/tags/route.md>), [strava](<https://devfeed.tech/tags/strava.md>)

### AI overview

Ryan describes how Strava's supportive internship helped him grow as a software engineer after an unconventional path through work and a bootcamp. On the Athlete Services team, he began refactoring the large Saved Routes presenter into separate presenters, view delegates, and filter factories while building route filters for sport, keyword, distance, elevation, starred status, and creator. The work was new to him, including Kotlin and a project of this scale; mentor guidance and code reviews helped him break it into manageable pieces and think more carefully about business logic. He also highlights intern events, leadership AMAs, and peer camaraderie, especially valuable while working from home. The excerpt presents ongoing learning and support as central to his positive experience.

### Source excerpt

About Me: Hey there! My name is Ryan, and I come from an unconventional background. I am not like most interns from the group in 2022. I've dropped out of college 3 times, worked in different fields for about 10 years, then transitioned into a bootcamp. Now working with Strava, they have set the expectation of what it should be like working in a professional environment. My Experience at Strava: Strava has been nothing but a wonderful experience. The weekly events they hosted to really engage the interns are motivational. The weekly AMAs were definitely my favorite of all the intern events. We got to meet the leaders of Strava and get to know them personally. The person I was most inspired by was Claude Jones. Claude also came from an unconventional background. He is a self taught programmer and worked his was up to VP of Engineering, leads motivational talks, and writes his own children books. From him I've learned that even if I don't come from a university, then I'll be able to make it in this field. So long as I continue to develop myself. https://medium.com/media/adf714e44d6915dfd4229f36178d2c49/href Aside from all the events we got to participate in, the support from my team, mentors, and managers provided for me was a whole new experience. I was given the chance to learn so much, and that definitely did not go to waste. The Project: I am on the Athlete Services Team, and my team's project was to create filters for the Saved Routes. The designs wanted us to be able to filter by sport, key word, distance, elevation, whether the route is starred or not, and who it is created by. Development: Creating this feature sounds easy right? Get the state of the filters, save it to the sheet, and apply it to the query. Yes, but there is more to it. The routes presenter and all of its associated classes are huge. So the android team wants to start refactoring that class into separate presenters, view delegates, and filter factories. Which I had the pleasure to start. In al