
Sentry (CA) Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 60 interview experiences · FREE TO READ
Which role are you interviewing for?
17 roles · 60 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Sentry (CA).
Solutions Engineer
So, first there was a recruiter screen, then I sent over my availability for the next round, which was a hiring manager presentation interview. That went well, and I sent a follow-up after that. Then came a HackerRank assessment, which I also completed. After that, I had a project discussion with the Hiring Manager. The final part was the interview loop, which had 6 interviews in total. It included two Solutions Engineers in one round, a Customer Executive interview, a Customer Manager interview, and a one-hour presentation with Q&A with several people. There was also a technical round where I had to code in a language I didn't know and answer questions about web fundamentals and databases. Lastly, I had a final chat with the Director of Solutions. This whole process was pretty long and took a lot of prep. I had to put together a big presentation about a past project, covering all the technical bits, how data flowed, how it was collected, and the integration setup. The questions mainly revolved around understanding the data points, how data gets captured, and how different systems connect. Everyone I spoke with was really nice and the vibe was good. The presentation part went smoothly, and most follow-up questions were about the tech and data side of things. But, after all that, I got a standard rejection email pretty quickly with no real feedback. It was kind of a bummer considering how much time I put in, especially preparing a custom proof of concept and that hour-long presentation. I asked for feedback and got a super short reply two weeks later saying they wanted someone with more customer experience, which was weird because the conversations felt positive. All in all, the process took a lot of my time but was pretty opaque and didn't give any useful feedback in the end. They make you prepare detailed presentations and tech explanations, but then you just get a generic rejection with barely any explanation. The interviewers were professional and friendly, but the whole thing felt frustrating because of the time it took and the lack of helpful feedback afterward.
- How do you capture data points?
- How do systems interact with each other?
- Could you elaborate on the technical implementation of the project?
Solutions Engineer
It started with an HR Screen, then a chat with the Hiring Manager that included a quick technical demo. After that, there was a HackerRank assessment. The final round was quite extensive, involving a technical panel demo, behavioral questions, and a technical aptitude test. It was a long process, but thankfully, the interviewers seemed to acknowledge the length of the final round, so they were aware of what they were asking.
- Can you demo a product with which you are familiar?
- Please answer a debugging question.
- Complete a very simple coding exercise in a language unfamiliar to you.
Software Engineer
The interview process included multiple stages: a recruiter screen, a conversation with the hiring manager, a take-home assignment, and several final-round interviews with engineers and a senior leader. The process felt well-structured overall, and the interviewers were professional throughout. However, there was a significant delay between application and the first response, followed by a fairly compressed schedule. One of the technical interviews was framed as a system design round, but focused primarily on live coding rather than architecture. No feedback was shared at the end of the process, which made it harder to evaluate my performance or improve.
- How would you tackle challenging or unclear technical problems?
Product Designer
I applied on their website. The process had 6 stages over a few weeks. First was a Recruiter / Product Design Manager chat, just a friendly intro about my background, experience, and why I'm interested. Then a UX Challenge, which was a whiteboard exercise based on a weird, unrealistic scenario, probably to see how I handle uncertainty and talk through my thinking. After that, an Engineering Manager interview, another nice chat focused on how I'd work with engineers and in teams. Next up was a Portfolio Review with a Senior Designer and the Product Design Manager. The questions were good and specific to the job, but I felt the Design Manager had already decided. They kept saying how technical Sentry is, which seemed to shape the discussion and the Senior Designer's view. Then a Technical Interview with a Senior Designer where I had to design and code a type scale system for an app UI – tested design and coding skills. Finally, a wrap-up with the Chief Creative Officer, a chill chat about how I thought the process went and my reflections. No feedback was given at this point. The whole thing was organized but slow, about a week between each stage. I spent about 5 hours total, not counting prep. The recruiter or team didn't communicate much between rounds, and I got no feedback after being rejected, just a polite reply to my follow-up.
- What motivates you to seek employment at Sentry?
- Can you share details about your professional background, your experience, and what specifically draws you to this position?
- In a hypothetical and perhaps unrealistic situation, how would you tackle ambiguity and articulate your thought process?
Sentry (CA) Interview Questions
Quoted word for word from Sentry (CA) interview reports.
“Find all instances of a given list of words within a text.”
Read reports →“Implement an Incrementor that raises an abstract value by one and provides the values recorded over the past five minutes.”
Read reports →“Can you implement a URL shortener using Flask?”
Read reports →“Describe a data structure suitable for performing operations on timestamps.”
Read reports →“How would you implement a bad word filter?”
Read report →“What are queues and how do they work?”
Read report →“Could you solve a Depth First Search algorithm problem?”
Read report →“Given an additional assumption, how would you improve the performance of the coded class?”
Read report →“How do systems interact with each other?”
Read report →Formats, difficulty and experience
Across all 60 Sentry (CA) interview reports.