I started with scheduling that took longer than I expected—about two weeks to get the meeting with the talent person—but once I was in, the next step moved quickly into a problem-solving interview. The interviewer mostly observed rather than partnering like a peer, and the interaction also felt a bit shaky around Java. I solved the problem, but I couldn’t fully validate it within the time because of a misplaced parenthesis around Java comparators. I didn’t spot the mistake before the session ended, and the interviewer didn’t catch it either.
That same overall pattern showed up for me in a different attempt: I’d been put into a timed problem-solving format where I had to both code and explain my thinking as I went. I wasn’t able to finish within the allotted time—around 50 minutes—and even though I felt like I’d communicated enough to earn progress, I didn’t make it to the next round. In both experiences, the problems themselves were manageable, but the clock and small implementation details seemed to make the difference, and I never got helpful feedback to be sure what they were weighing most heavily.
3 months ago
After a recruiter reached out, I went through a structured two-stage process. Stage one started with a problem-solving and values round, which was scenario-based with agents and their limits. I remember having to reason through how the scenario should work before moving into the values portion.
Once that was done, I had the second stage with a Minicom round and then a design round. The format felt very organized on paper: first the scenario and values check, then a Minicom exercise (a coding-style task based on a small repo), and finally a design discussion. I also had a question thrown in about what technology they used for the UI and whether it was React, which made the process feel like it covered both product and engineering context.
4 months ago
Easy Negative Berlin
My experience was defined by how disorganized the follow-through felt after I did the work. I went into an interview where the technical question star…
4 months ago
Easy Negative Dublin, Dublin
My process felt methodical and thorough, and I could tell it was meant to be a real evaluation rather than quick checkboxes. It started with a recruit…
5 months ago
Average Positive Berlin
My process started with a quick recruiter conversation, then moved into two back-to-back interviews that felt like they were testing two different thi…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Stages
The interview process typically begins with a recruiter screen, followed by a mix of technical and values assessments, culminating in an onsite or multi-round interview. Candidates often experience a structured flow with clear expectations laid out in advance.
Candidates face a variety of technical challenges, including coding exercises that often require knowledge of data structures and algorithms, with a focus on clean reasoning and implementation under time constraints. Some rounds involve pair programming or Minicom-style tasks.
Coding challengesData structuresMinicom
Behavioral & Values Assessment
Behavioral interviews focus on alignment with Intercom's values, often using scenario-based questions and prompts that require candidates to reflect on past experiences and decision-making processes. This aspect is crucial for evaluating cultural fit.
Behavioral questionsCultural fitValues alignment
Communication & Feedback Issues
Many candidates report frustrations with the lack of timely communication and feedback throughout the process, often feeling left in the dark after interviews. This can lead to a negative overall impression despite a well-structured interview experience.
CommunicationFeedbackCandidate experience
Interview Environment & Tools
The technical interviews often involve whiteboarding or online coding platforms, which can introduce challenges such as tool reliability and interviewer preparedness. Candidates noted that these factors can significantly impact their performance.
WhiteboardingTechnical toolsInterview environment
Overall Difficulty & Expectations
Candidates generally perceive the difficulty of the interviews as moderate to high, with a strong emphasis on both technical skills and cultural alignment. Many felt that the process was rigorous but also expressed a desire for clearer expectations regarding evaluation criteria.