Sentry Experienced Engineer Interviews: 14 Experiences

Shared by janebeingjane ·
Company
Sentry
Level
Full-time
Stages
OA → Phone screen → Onsite

Sentry experienced engineer reports, 2021–2026: a 2026 phone screen was a URL-shortener design; earlier onsites built a package manager and a parking lot.

At a glance

  • Process (software engineers): recruiter, then hiring manager, then a technical phone screen or a take-home, then final rounds with several engineers (SWE 02; SWE 01 describes only the phone screen).
  • Asked since 2024: a URL-shortener design pushed toward production problems (SWE 01, May 2026); a final round billed as system design that was mostly live coding (SWE 02, Jul 2025); a practical coding question given out loud to a manager candidate (EM 01, Jul 2024).
  • Difficulty: the 2026 phone screen moved fast, with many short probes, and the candidate failed it (SWE 01).
  • Practise first: Design a URL Shortening Service (SWE 01).

Coverage: 14 experienced reports: 9 software engineers, 1 senior frontend engineer, 1 iOS engineer, 2 site reliability engineers and 1 engineering manager. 5 are from Jan 2024 to May 2026; 9 are from 2021 to 2023 and sit in each role's History. Locations given: San Francisco and Toronto.

Roles in this article: Software engineer (9) · Senior frontend engineer (1) · Engineering manager (1) · Site reliability engineer (2) · iOS engineer (1)

Other Sentry cohorts: Sentry SWE new grad OA and technical screen · Sentry SWE intern OA and technical interview · Sentry software engineer interviews, hiring level not reported

Software engineer

What came up

Each of the three recent software engineer reports covers a different step, so no topic repeats. One had a URL-shortener design on the phone screen (01), one a final round that turned into live coding (02), and one only behavioral questions with the hiring manager (03).

Questions we found

System Design

Question Reports Last seen
Design a URL shortener, then scale it 1 May 2026 (report date)

Behavioral (BQ)

Question Reports Last seen
How do you approach complex or ambiguous technical tasks? 1 Jul 2025

3 detailed candidate timelines, loops, and screens

SWE 01: URL-shortener phone screen

Report date: May 2026 · Role: Software Engineer (PhD, changing jobs) · Result: Failed the phone screen

Technical phone screen

  1. Design a URL shortener. It started from a basic system that already worked. The interviewer then pushed it toward production problems, step by step: the service layer, the database, caching and sharding.
  2. Then: how would you find the cause of a product issue, and which metrics would confirm it?
  3. The probes came quickly. The candidate's lesson: keep each answer short so there is time for all of them.

SWE 02: Take-home, then a "design" round that was live coding

Interview date: Jul 2025 · Role: Senior Software Engineer · Result: No offer, no feedback

  1. Recruiter screen.
  2. Hiring manager conversation.
  3. Take-home assignment (content not described).
  4. Final rounds with several engineers and a senior leader. The round billed as system design was mostly live coding. One question: how do you approach complex or ambiguous technical tasks?

SWE 03: Behavioral round with the hiring manager

Interview date: Jan 2024 · Role: Senior Software Engineer · Location: Toronto · Result: No reply

  1. Recruiter call.
  2. Hiring manager: standard behavioral questions about past experience and projects, answered in the situation–task–action–result style. No single question was named.

History (before November 2023)

These six reports are older than about three years. They are not counted above.

SWE H01: Parking lot and package manager onsite

Report date: Apr 2023 · Role: Software Engineer (changing jobs) · Result: Passed the onsite

  1. Recruiter outreach, HR call, hiring manager call, then a phone screen whose question the author forgot.
  2. Onsite round 1: a parking lot. It is object-oriented design, but the code must run. Park and unpark; reject when all spots are full. Follow-ups: small, medium and large cars and spots (a small car fits a large spot, not the reverse); a distance from each spot to the door, using a formula the candidate picked, with the nearest spot handed out first; then several entrances with different distances.
  3. Onsite round 2: an npm- or brew-like package manager. Installing a package pulls in its dependencies, and theirs. Uninstalling a package that another installed package needs must fail. Uninstalling a package also removes dependencies nothing needs any more, but keeps packages the user installed on purpose.
  4. Onsite rounds 3 and 4: behavioral (questions not named). The candidate said none of it was too hard.

SWE H02: Set up your own environment, then an easy coding task

Interview date: Feb 2023 · Role: Senior Backend Engineer · Location: San Francisco · Result: No offer

  1. Recruiter, then a hiring manager talk about background (not technical).
  2. Before the coding round, the candidate had to set up a local containerized environment: a web service with its datastore, plus a job queue with its own datastore. This was because their main language was not Python.
  3. Technical with the hiring manager, LeetCode-easy: given a list of words, find all their occurrences in a block of text. The candidate solved it.

SWE H03: Implement a class, then extend it

Interview date: Aug 2022 · Role: Senior Engineer · Result: Offer declined

  1. Online code screen.
  2. Online onsite with two coding and design challenges, plus experience and team-fit talks with managers.
  3. One challenge: code a class for a given API, explain its runtime, then handle a new assumption and make it faster. The other: write classes to model something, then add two features. The candidate replaced the real names with placeholders.

SWE H04: React build and three data-structure designs

Report date: Oct 2021 · Role: Senior Software Engineer · Location: Toronto · Result: No offer

  1. Six interviews with about ten people: build something in React; three design rounds where you create a class or data structure and explain the trade-offs; a development manager; a VP of Engineering.

SWE H05: Intro call about current work

Interview date: Aug 2021 · Role: Senior Software Engineer · Result: No offer

  1. A 30-minute intro call full of detailed questions about the candidate's current work, its data and its systems (practice). It felt rushed, and the interviewer said little about the role.

SWE H06: npm dependency design and a timestamp structure

Report date: May 2021 · Role: Senior Software Engineer · Location: Toronto · Result: No offer

  1. Recruiter phone call, 30 minutes.
  2. A 1-hour technical conversation with an engineer.
  3. Two 1-hour coding rounds. The tasks: design npm, but only the data structure and algorithm that manage package dependencies; and a data structure that runs some operations on timestamps. The report gives no more detail on the second one.

Senior frontend engineer

One report, with one named behavioral question.

Question Reports Last seen
Your most challenging frontend project 1 Mar 2024

FE 01: Six interviews, eight people

Interview date: Mar 2024 · Role: Senior Frontend Engineer · Result: No offer

  1. Screening call.
  2. Behavioral interview: describe the most challenging frontend project you have worked on.
  3. Technical interview (content not described).
  4. Virtual onsite: two technical interviews and one with a C-level leader. Six interviews and eight people in all.

Engineering manager

One report. No question was named.

EM 01: Practical coding, explained out loud

Report date: Jul 2024 · Role: Engineering Manager · Location: San Francisco · Result: No offer

  1. Recruiter, then hiring manager.
  2. Technical evaluation: a high-level, practical coding question (not a LeetCode-style one), given out loud, in the candidate's language of choice.
  3. The interviewer seemed unprepared, spent about 15 minutes explaining one edge case and would not write out examples.

Site reliability engineer

Both reports are older than about three years, so they sit in History.

History (before November 2023)

SRE H01: Why work here, then silence

Report date: Jul 2023 · Role: SRE Engineer · Result: No reply

  1. Initial interview: why do you want to work here? Nothing followed.

SRE H02: Manager asks about your biggest challenge

Report date: Feb 2023 · Role: SRE · Location: San Francisco · Result: No offer

  1. The recruiter call was rescheduled several times.
  2. Manager interview, open-ended and behavioral: the biggest challenge in your career.

iOS engineer

History (before November 2023)

iOS H01: Recruiter and manager video calls

Interview date: Apr 2021 · Role: Software Engineer (iOS) · Location: Toronto · Result: No offer

  1. Recruiter video call, 35 minutes, focused on experience.
  2. Manager video call, 45 minutes. The manager seemed distracted.

Common questions

What is the first technical round for experienced Sentry engineers?

For software engineers it varies: a URL-shortener design phone screen in 2026 (SWE 01) and a take-home in 2025 (SWE 02). Older reports had a phone screen whose question was forgotten (SWE H01), an easy coding task with the hiring manager (SWE H02) and a 1-hour technical conversation with an engineer (SWE H06). For the 2024 manager candidate it was a verbal practical coding question (EM 01).

Which language can I use in a Sentry technical interview?

The candidate's choice in the manager's technical (EM 01). One 2023 backend candidate had to bring a local environment because their main language was not Python (SWE H02).

Can I use AI or my own IDE in a Sentry interview?

None of the 14 reports say.

Does Sentry run your code in the interview?

In one 2023 onsite the parking-lot design had to run (SWE H01). No other report says.

What to practise

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.