# Bluesky Interview Guide (2026): Decentralized Social Engineering

Source: https://www.techinterview.org/companies/bluesky-interview-guide/
Updated: 2026-07-12 · techinterview.org

**TL;DR —** A Bluesky engineering interview combines conventional coding and system-design rounds with questions specific to decentralized social networks, so expect to reason about the AT Protocol, federation, and how user identity and data move across independent servers. Interviewers weigh distributed-systems thinking — content addressing, data portability, moderation at scale, and behavior under partitioned or untrusted networks — as much as clean, correct code. Candidates who can explain trade-offs between openness and consistency stand out more than those who only optimize a single-server design.

Bluesky is the decentralized social network built on the AT Protocol — the modern alternative to Twitter/X. Funded by Twitter spinout, now an independent company. The interview is technically rigorous with focus on the federated protocol design and the unique scale challenges of decentralized social.

## Process

Recruiter screen → 60-minute coding pair → onsite virtual: 2 coding, 1 [system design](/category/system-design/), 1 craft deep-dive, 1 [behavioral](/post/3233460379/behavioral-interview-questions-2026-star-method-amazon-leadership-principles-and-winning-answers/). Cycle: 3–5 weeks.

## What they actually ask

- Design a federated social network with decentralized identity — identity is portable here: in AT Protocol a user is a DID (decentralized identifier) paired with a handle, so an account can move between hosting providers without losing its followers. Interviewers probe how you separate identity, per-user data storage, and the indexing layer, and how you keep account portability and data ownership real rather than cosmetic.

- Design [timeline algorithms](/post/3233474168/system-design-twitter-news-feed-timeline-fanout-on-write-fanout-on-read-celebrity-problem-ranking-caching/) for AT Protocol — reason through the fan-out tradeoff (precompute each user's timeline on write vs. assemble it at read time) and where custom feed generators plug in. Be ready to discuss ranking, feed freshness, and how an aggregation service stitches posts from many independent servers into one coherent view.

- Design content moderation across federated servers — the hard part is moderating without central control. Talk through labeling services, stackable moderation that users can subscribe to, and how one server enforces its own rules when the underlying data lives elsewhere; expect follow-ups on spam, abuse, and illegal content when you don't own every node.

- Coding: practical TypeScript/[Go](/post/3233474456/go-golang-interview-questions-2025-goroutines-channels-interfaces-error-handling-context-generics-concurrency-patterns/), often with distributed-systems framing — expect real tasks over puzzle trivia: parse and transform data, build a small service, handle concurrency and errors cleanly. Write idiomatic code and be ready to explain how it behaves under network failures or partial data.

- Behavioral: mission alignment with open social web, written communication — bring an actual point of view on decentralization and why an open social web matters; a generic "I love the mission" answer falls flat. Because the team is distributed, they weight clear async writing, so be ready to explain a past technical decision in writing rather than just out loud.

## Levels and comp (2026)

- SE: $180K–$240K total

- Senior SE: $260K–$340K

- Staff: $370K–$480K

- Principal: $500K–$650K

## Prep priorities

- Be fluent in TypeScript / Go (the bulk of the codebase) — practice writing production-quality code in both, not just [algorithm patterns](/algorithm-patterns-cheat-sheet/): know the standard libraries, error handling, and concurrency primitives you'd reach for day to day.

- Understand AT Protocol and federated social architectures — read the protocol docs on DIDs, personal data servers, relays, and App Views so you can sketch the full path a post takes from being written on one server to showing up in someone else's feed.

- Read about ActivityPub, Mastodon, and the broader fediverse for context — be ready to contrast AT Protocol's account-portability model with ActivityPub's server-bound identity, since knowing that tradeoff shows you've thought about decentralization past the buzzwords.

## Frequently Asked Questions

### Is Bluesky remote-friendly?

Distributed-first. Small team (~50 employees) globally. Quarterly off-sites.

### How does Bluesky compare to Mastodon or Threads?

Mastodon is ActivityPub-based, federated. Threads is Meta-controlled. Bluesky uses AT Protocol with different decentralization model. Bluesky engineering pays competitively.

### What is the engineering culture?

Mission-driven (open social web), small team, technically deep. Strong fit for engineers excited about the future of social networks.