Glassdoor users rated their interview experience at Intellias as 100% positive with a difficulty rating score of 4 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Software Engineer and rated their interviews as the hardest, whereas interviews for Software Engineer and roles were rated as the easiest.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at Intellias in Apr 2026
Interview
I had a generally positive experience with the interview process.
The process consisted of several stages:
1. Initial HR screening
2. Technical interview (backend + frontend tasks)
3. Client interview with a coding exercise (Python + problem-solving)
All interviewers I spoke with were professional, and the technical discussions were relevant and close to real-world tasks.
The overall process felt well-structured and gave a good understanding of the product and expectations.
One area that could be improved is communication transparency. There were noticeable delays in responses and a lack of intermediate updates, which made it difficult to understand the current status of the process. More timely and proactive communication would significantly improve the candidate experience.
Interview questions [1]
Question 1
(livecode): merging overlapping time ranges in Python
Three total interviews. The process began with an initial HR screening call focused on background, interest in the role, and general fit for the company. This was followed by two separate internal interviews with members of the marketing team, where I was asked about my experience, campaign coordination skills, and approach to working in a fast-paced environment. Overall, the process felt structured, fairly straightforward, and professional, with clear communication between stages.
I applied through a recruiter. I interviewed at Intellias (Burgas) in Feb 2026
Interview
The job interview started immediately with a lifecoding session. No personal information. No previous job experience. Nothing that should be at the start of the common interview. Moreover, the livecoding session was in a common Windows notepad (it brought me back to my university years). Then there were a few normal questions, but after that interviewer started to ask "geek" questions about the garbage collector that are not related to the conceptual character of you as a programmer. My advice would be to ask more practical questions instead of dry and boring theoretical ones.
Interview questions [1]
Question 1
Every garbage collector type details why this one (GC type) was created, etc. Other questions were deeply about the GC topic in detail, but I don't remember them all.