High level two sections - screening round and onsite.
Onsite
I had progressed to final round and got a reject from the team. I had good experience with first two or three rounds,
The last technical design was poor because the interviewer was not well-prepared, didn't explain the problem well and wasn't helpful at all. When I asked questions, he said this is fine for now.
Later I received the feedback, I didn't perform well and turning me down, because of the round. Normally, when the interviewee isn't performing as expected, the interviewer provides clues and that didn't happen.
If you're someone into backend, then I don't think, so the process is suitable for you. Their interview process is designed for full-stack developers. Watch out for untrained interviewers who can turn your chances down.
Programming round - Practical programming questions
Behavior round - Standard behavior round questions
Solo integration - API development and integrating with FE using vanilla JS or JS library.
Extending integration with pair programming - Like previous round, you will pair program to add a new feature.
Technical design - Given a simple screen you need to design abstract model. Catch: Abstract so abstract and model is so abstract, it's not your typical system design round. It's a hit or miss.
The following metrics were computed from 4 interview experiences for the Intercom Senior Product Engineer role in Dublin, Ireland.
Intercom's interview process for their Senior Product Engineer roles in Dublin, Ireland is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Intercom's Senior Product Engineer interview process in Dublin, Ireland.