Sentry SWE Intern OA and Technical Interview: 16 Experiences

Shared by janebeingjane ·
Company
Sentry
Reports
8 interview reports
Level
Internship
Stages
OA → Phone screen → Onsite

Sentry SWE intern reports, 2018 to 2026: a 60-minute word-wrap OA, then one technical where 3 of 8 recent reports got a graph or dependency problem.

At a glance

  • Process: OA (HackerRank, 60 minutes, one problem; reports 04, 06), then one technical with an engineer and a hiring-manager talk (03, 05, 07). The recruiter or HR call came before the technical in one report (03) and after it in another (05).
  • Asked since late 2023: a graph or dependency problem in the technical, 3 of 8 (last Feb 2026: reports 01, 03, 05), and one more candidate advised preparing graphs and topological sort (08); the word-wrap OA, 3 of 8 (last Dec 2025: reports 02, 06, 08).
  • Difficulty: the live graph round was called "not too difficult" (03) and an easier medium where reading the prompt was the hard part (05). The OA felt harder: one called it LeetCode-hard (08), and another ran out of time on edge cases (06).
  • Practise first: Dependency-Aware Package Manager for the technical and Word Wrap with Even Justification for the OA.

Coverage: 16 software engineering intern reports. 8 are from Nov 2023 to Feb 2026; 8 are from 2018 to 2023 and sit in History. Locations given: Vienna, Toronto, Los Angeles and the U.S.

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

What came up

The technical round is where the graph pattern shows up. Three of the eight recent intern reports name a graph, DFS or dependency task there, and a fourth advised preparing graphs and topological sort (08).

Topic Reports Last seen
Graph or dependency problem (technical) 3 of 8 Feb 2026
Word wrap / text justification (OA) 3 of 8 Dec 2025
Unnamed string-manipulation OA 2 of 8 Jan 2025
What you know about Sentry (recruiter) 1 of 8 Sep 2024

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Word Wrap with Even Justification (a LeetCode 68 variant) 3 Dec 2025 (report date)

Low-Level Design (LLD/OOD)

Question Reports Last seen
Build a package manager from scratch 1 Feb 2026 (report date)

Behavioral (BQ)

Question Reports Last seen
What do you know about Sentry? 1 Sep 2024 (report date)

8 detailed candidate timelines, loops, and screens

01: Graph traversal and a package manager from scratch

Report date: Feb 2026 · Role: SWE Intern · Result: Waiting for the final round

First technical

  1. Graph traversal, and building a package manager from scratch: packages depend on other packages, so installing one means walking its dependency graph.
  2. The candidate had moved on to the final round. Language, tools and timing were not mentioned.

02: Vienna OA, text justification

Report date: Dec 2025 · Role: Software Engineer Intern · Location: Vienna · Result: No reply after the OA

  1. The OA came two to three weeks after applying.
  2. It was a variation of LeetCode 68, Text Justification: the word-wrap problem.
  3. Nothing came back after that.

03: DFS with a full-time engineer

Report date: Jul 2025 · Role: Software Engineer Intern · Result: No offer

  1. Phone screen.
  2. HR conversation.
  3. Technical with a full-time engineer: a depth-first search question. The candidate said it was not too difficult.
  4. Software manager: no technical questions, only experience and fit.

04: HackerRank string task with no camera

Report date: Jan 2025 · Role: Software Engineer Intern · Location: Toronto · Platform: HackerRank · Result: No offer

  1. The first round was a HackerRank string-manipulation challenge with no camera. The candidate said an optimized solution was essential.
  2. No later rounds followed.

05: Graph technical before the recruiter call

Report date: Sep 2024 · Role: SWE Intern (Summer 2025) · Location: U.S.

  1. OA: all tests passed. The candidate was not sure which platform it ran on.
  2. Technical: a graph problem, an easier medium. The hard part was understanding the prompt and asking the right clarifying questions.
  3. Recruiter call, 30 minutes: what they knew about Sentry (practice) and about two behavioral questions.
  4. Hiring manager round was still pending at the last update.

06: Word-wrap OA, 7 of 10 tests

Report date: Aug 2024 · Role: SWE Intern (Summer 2025) · Platform: HackerRank · Result: Rejected

OA (60 minutes, one problem)

  1. Lay words out into lines of width n, padding with underscores. Center a line that holds one word. Keep a hyphenated word whole when it fits; otherwise split it right after the hyphen. This is the word-wrap problem.
  2. They passed 7 of 10 tests and ran out of time on edge cases.

07: One-hour virtual technical after the OA

Report date: Feb 2024 · Role: Software Engineer Intern · Result: Rejected

  1. OA: a string-manipulation question.
  2. Virtual technical, about 1 hour: one problem, then more discussion about it. The candidate solved it fully.
  3. Hiring manager talk. The rejection came even after the full solve.

08: Text-justification OA, graphs on the phone

Report date: Nov 2023 · Role: SWE Intern (undergraduate junior)

  1. OA: a modified Text Justification problem that felt LeetCode-hard: the word-wrap problem.
  2. Phone interview: the candidate advised preparing graphs and topological sort for it. The exact problem was not given.

Patterns across the reports

  1. Graph work in the technical. Three recent reports put a graph or dependency problem in the one technical (01, 03, 05), and 08 advised preparing graphs for the phone interview. Only 01 names the task. The others give the topic: DFS (03) and a graph medium with a hard-to-read prompt (05).
  2. One engineer, one problem. Three reports describe a single technical with an engineer before the manager talk (03, 05, 07). One of them gives the length: about an hour, one problem plus discussion (07).

Common questions

What is the first technical round for Sentry interns?

A technical round, with an engineer where reports say (03, 05, 07). In 3 of 8 recent reports it was a graph or dependency problem (01, 03, 05); 08 advised preparing graphs and topological sort. Older reports had an npm-like package manager (H04, Sep 2022), an inventory tracking design (H03, Jan 2023) and two LeetCode mediums (H06, 2021).

How long is the Sentry intern technical interview?

About 1 hour for one problem plus discussion, in the only recent report that gives a length (07).

Can I use AI in the Sentry intern interview, and which IDE or language?

No intern report says whether AI is allowed or which IDE the live round uses. A 2023 candidate said the OA let them pick any common language (H02), and a 2018 phone round ran on CoderPad (H08).

What is the Sentry intern OA like?

HackerRank, 60 minutes, one problem with about 10 tests (06). From Aug 2023 it was the word-wrap problem (H02, 02, 06, 08); before that, the bad-word filter (H05, H07).

What does the Sentry intern recruiter call ask?

In one 2024 report it was 30 minutes: what you know about Sentry and about two behavioral questions (05).

What to practise

History (before November 2023)

These eight reports are older than about three years. They are kept for the round details, but they are not counted above.

H01: HackerRank OA, then a straightforward technical

Report date: Sep 2023 · Role: Software Engineering Intern · Location: Los Angeles · Platform: HackerRank · Result: No offer

  1. HackerRank OA, then a technical interview the candidate called straightforward: average LeetCode-medium questions (not named).

H02: New word-wrap OA, unfinished

Report date: Aug 2023 · Role: Software Engineer Intern (Summer 2024) · Result: Did not finish; expected no phone interview

  1. A new string problem that year, 60 minutes: the word-wrap problem. The output is a list of lines.
  2. Any common language was allowed (Python, C, Java and so on).
  3. Many edge cases, such as several words exactly as long as the width. The candidate suggested writing a brute force before the OA.

H03: Inventory tracking design

Report date: Jan 2023 · Role: Software Engineer Intern · Result: No offer

  1. OA, medium difficulty.
  2. Technical: an algorithm question about designing an inventory tracking system. No further details were given.
  3. Behavioral interview a couple of days later.

H04: Build npm from scratch, no requirements given

Interview date: Sep 2022 · Role: Software Engineer Intern · Result: No offer

  1. A long HackerRank OA.
  2. Live technical: implement a package manager like npm from scratch. No requirements or input format were given, and the interviewer did not answer clarifying questions.
  3. The recruiter had suggested classic coding-interview prep. The candidate felt the task did not match that.

H05: Bad-word OA, 5 of 8 tests

Report date: Aug 2022 · Role: Software Engineer Intern (Summer 2023) · Result: Rejected after the OA

  1. The bad-word filter, the same OA as the two years before. It had 8 tests; the candidate passed 5 and had no time left to fix the rest.

H06: Two LeetCode mediums with follow-ups

Report date: Oct 2021 · Role: SWE Intern (Summer 2022) · Result: Pending at last update

  1. OA, easy.
  2. Technical: two LeetCode-medium problems with follow-ups (not named).
  3. Final: an informal talk with the hiring manager.

H07: 60-minute bad-word OA

Report date: Sep 2021 · Role: Software Engineer Intern · Platform: HackerRank · Result: Did not pass

  1. One problem, 60 minutes: the bad-word filter. The inputs are a string of bad words and a sentence. A * stands for any run of letters at the start or end of a bad word. Each matching word becomes asterisks of the same length.
  2. The candidate spent too long reading and chasing a faster idea, then ran out of time debugging. Their advice: write the brute force first.

H08: URL shortener in a Flask codebase

Interview date: Sep 2018 · Role: Software Engineer Intern · Platform: CoderPad · Result: No offer

  1. Two phone interviews on CoderPad, then an onsite.
  2. One phone task: implement a URL shortener inside an existing Flask codebase. The report does not say which of the two phone rounds it was.
  3. The second phone interviewer spent a long time explaining tools, pushed his own answer and ran 20 minutes over.

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.