Backstage Blog

• Engineering
• API
• Architecture
• Microservices
• Productivity

Discover how service architecture has evolved at Soundcloud over the past few years...

• Reverse Dependencies
• Engineering
• Testing
• Tooling
• Automation

Let's take a look at techniques we can use to confidently release updates to an internal library that's integrated into hundreds of projects across the company — even if they're API-breaking changes.

• Engineering
• Engineering Culture
• Operations

In this post, we share some of the best practices we apply when SoundCloud engineers take on out-of-hours support duties.

• Learning
• Diversity
• Recruiting
• Engineering
• Engineering Culture

DeveloperBridge is a year-long, full-time, paid traineeship program where participants learn from and work with engineering teams at SoundCloud. The DeveloperBridge program was launched in 2017 with the goal of further supporting diversity and inclusion at SoundCloud and giving back to the tech community.

• Engineering
• Interviewing
• Remote

At SoundCloud, we changed our hiring strategies to adapt to hiring remotely during COVID-19.

• Engineering
• Interviewing
• Code Challenge

SoundCloud engineers and recruiters recently comprehensively rethought the backend engineering take-home challenge. This is the second in a small series of posts, and it contains the recruiting perspective and the results of the changes.

• Engineering
• Interviewing
• Code Challenge

SoundCloud engineers and recruiters recently comprehensively rethought the backend engineering take-home challenge. This is the first in a small series of posts about what we did and why.

• Engineering
• Finagle
• Twirp
• Scala
• Open Source
• Announcements

This article announces the release of Twinagle, an open source implementation of the Twirp protocol for Scala/Finagle.

• Engineering
• Go
• Monitoring
• Open Source
• Typescript
• React
• Announcements

A new approach to exception monitoring, designed for high scalability...

• Data
• Engineering
• Architecture

Two years ago, if an engineering team at SoundCloud needed data produced by another team, in many cases, that team would have had to start by building a dataset from the raw data. That meant there was no standard way to structure data into a dataset, there were errors in understanding and interpreting raw data, and there was no reuse of datasets across teams. Ownership of datasets was with the teams consuming data, even when the data itself was owned and best understood by someone else. By agreeing on an ownership strategy, a common shape for datasets, and standard tooling, SoundCloud was able to streamline these problems away. Now the data and datasets are provided by those who know best about their data, along with the help of tooling built by those who know best about building tools. Read on to learn what datasets look like at SoundCloud and how they are built.