Belzabar Software Interview Experience | Set 4
Interview Experience
I recently had interview at Belzabar.After aptitude round only 69 students were shortlisted out of 256.First Round(F2F):He started asking questions about data structure. Q...
Full Details
I recently had interview at Belzabar. After aptitude round only 69 students were shortlisted out of 256. First Round(F2F): He started asking questions about data structure. Questions were easy.Graph and heap sort were mainly focused topic. Second Round(F2F): In second round, he asked one puzzle(Haretown and Tortoiseville are 45 miles apart. A hare travels at 7 miles per hour from Haretown to Tortoiseville, while a tortoise travels at 2 miles per hour from Tortoiseville to Haretown. If both set out at the same time, how many miles will the hare have to travel before meeting the tortoise en route? ). Then he focused on java basic questions. Third Round(F2F): In this round he asked me 2 code reverse a string without using temp variable. then asked one query( DBMS query to print the nth largest salary in baghel table ). Two 2 linked ques and 3 tree questions he asked like(mirror of tree).
HR 1.tell me about yourself. 2.why do you want to join Belzabar.
About This Question
This is a candidate experience report from a belzabar interview for a swe role during the technical round reported in 2015.
It covers the following topics: Heap, Trees, Strings, Sql, Graph, Sorting, Graphs .
Difficulty rating: Easy
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.