Belzabar Interview Experience for Sr. Computer Scientist (3.4 years Experienced )
Interview Experience
Profile: Sr. Computer scientist (3.4 years Experienced ) , frontend JS developerThere were 4 rounds of interview:Round 1:It was a written round where I have to find nth pr...
Full Details
Profile: Sr. Computer scientist (3.4 years Experienced ) , frontend JS developer There were 4 rounds of interview:
Round 1 It was a written round where I have to find nth prime numbers in the most optimal way. https://www.geeksforgeeks.org/dsa/sieve-of-eratosthenes/ https://leetcode.com/problems/count-primes/ I cleared this round. And I was called for face to face interview
Round 2 This was a technical round. Following were the questions asked Difference between React 15 and React 16 How Angular executes its life cycle(Internal working) How Change Detection Works Why Angular change detection is fast Differences between let, var, const (It's internal implementation) How closures work One question on DP which I didn't remember Implement Singleton Design pattern implement Observable design pattern Try to implement your own async/await Implement your own jquery function to update DOM JS architecture. I cleared this round. This round mainly focus on your in-depth knowledge of how things work
Round 3 This round was with the Director and Manager of Belzabar. They were nice persons About my project and company Implement your own tree shaking algorithm (Here I thought about nodes having arbitrary pointers to other nodes using there and instance. In the first pass mark the functions using similar concept of sieve-of-eratosthenes algorithm. The second pass remove unused nodes and function.) Types of design pattern I have implemented Design patterns Created dynamic routes and components in angular es5 and es6 syntax Implement your own JSON.stringify and JSON.parse This round also focuses on your thinking process for the problem given to you. I cleared this also :)
Round 4 This was HR round I got the offer :) The company focuses on your thinking process and In-depth knowledge of the Framework, you have worked on.
About This Question
This is a candidate experience report from a belzabar interview for a frontend role (senior level) during the recruiter round reported in 2025.
It covers the following topics: Trees, Dynamic Programming, Oop, Math .
Topics
More Belzabar Interview Questions
About Belzabar Interview Reports
This question was reported by a candidate who interviewed at Belzabar. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Belzabar are the higher-signal extractions to take from this report.
For broader preparation context, the Belzabar interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Belzabar reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Belzabar Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Belzabar reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.