A very long process but quite enjoyable I must say
Recruiter screen - Standard recruiter questions
Coding round - Expect a LC Medium, something around user ping intervals which involves partitioning the array
Values round - Lot of behavioral questions, checkout company values to answer in that format
Coding round (solo) - Had to do a minicom project like a small version of intercom
Coding round (pairing) - Same as earlier except now an engineer will join and help you solve the problem etc., she was very friendly as well
Data model design round - Database design read more around ER diagrams, normalization etc., you should be good
Role chat - You'll meet an EM and you can ask questions to him now about the company and the role
After this point, if you get a yes then you move to HM round (Note: this doesn't mean you can expect an offer, it's not like Google or Meta where you go through multiple team matches if HM says no then it's a no hire), prepare behaviorals they expect you to have some product sense, fullstack all around development sense etc.,
I received an offer. Overall the experience was very positive I really enjoyed it and the recruiter and everyone was very friendly. Unfortunately I couldn't join I'll definitely apply in the future
Interview questions [1]
Question 1
Recruiter screen - Standard recruiter questions
Coding round - Expect a LC Medium, something around user ping intervals which involves partitioning the array
Values round - Lot of behavioral questions, checkout company values to answer in that format
Coding round (solo) - Had to do a minicom project like a small version of intercom
Coding round (pairing) - Same as earlier except now an engineer will join and help you solve the problem etc., she was very friendly as well
Data model design round - Database design read more around ER diagrams, normalization etc., you should be good
Role chat - You'll meet an EM and you can ask questions to him now about the company and the role
HM round - Team match
It initially took 2 weeks to schedule a meeting with the talent person, but they were then quick to follow up with the problem solving interview. The interviewer acted more as an observer rather than a peer and he was not particularly confident about Java as a language. I solved the problem, but was unable to test the solution in the given time because of a misplaced parenthesis on Java comparators. I didn't spot the mistake by the end and neither did the interviewer. I think this is the reason for the rejection, but I can't be 100% sure since they didn't provide any feedback.
I applied through a recruiter. The process took 7 weeks. I interviewed at Intercom (Dublin, Dublin) in Apr 2026
Interview
A Recruiter reached out on LinkedIn, two initial phone screens.
Engineering manager meeting, leadership principles and culture fit. Two rounds of back to back technical interview with very easy/toy problems.
The final interview was with an engineer who made no attempt to communicate clearly or professionally. Dimly lit room, off camera, and speaking in an unintelligible monotone. The interview wrapped up 10 minutes early as the engineer was disinterested in discussing the problem at hand.
The whole process took 7 weeks.
I applied through a recruiter. I interviewed at Intercom (London, England) in Mar 2026
Interview
After recruiter reached out, a values interview and a live coding interview was scheduled. The coding was easy, a load balancer question.
I was told my technical round went well and the values round the answers were not concise and very detailed.
Interview questions [1]
Question 1
Load balancer - assigning conversation to teammates with a limited capacity.
Senior Product Engineer applicants have rated the interview process at Intercom with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 47.3% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -