Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4 stories

Likes earn the author +10 XP for the first 3 likes each day

New RelicBackend Engineer
Sep 2026

String Compression, Longest Increasing Path, and a Kafka Trace-Grouping Design

Question 1: Implement a method that does basic string compression by counting consecutive repeated characters. If the compressed string is not shorter than the original string, return the original string. Discuss time complexity and space complexity Discuss edge cases Discuss code optimization Question 2: Longest Increasing Path in a Matrix. You can only move in four directions (up, down, left, r…

Onsite0
New RelicSoftware Engineer
Reported Jul 2026

New Relic Software Engineer interview experience: SDE-2 Codility DSA

I interviewed for an SDE-2 track and was rejected after the first technical round. It was a DSA-focused coding session on Codility, centered on data structures and algorithms. The interviewer gave a brief introduction and moved straight to the coding questions. The prompts used real-life scenarios rather than only abstract problems. I did not move past that initial technical checkpoint, and it fe…

RejectedTechnical Screen0
New RelicSoftware Engineer
Reported Jul 2026

Software Engineer interview at New Relic: delayed Portland process

After the recruiter call, I waited almost two weeks before the hiring manager scheduled the Portland interview. On that call, the manager seemed disengaged and did little to build momentum, so the conversation felt flat and uninterested in my experience. Another couple of weeks passed with no update. The recruiter eventually said the search had narrowed and they were pausing candidates, followed…

Rejected0
New RelicSoftware Engineer
Reported Jun 2026

New Relic Software Engineer Interview Experience: good rounds followed by silence

The early part moved quickly. I had technical rounds that went well in a single day, then a hiring-manager conversation a few days later. That conversation felt positive, and communication during it was easy and on track. What threw me off was everything afterward. HR went quiet, and when I messaged, I got nothing back. After about a week of silence, I wanted feedback, even negative feedback, bec…

No responseTechnical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP