Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

HiLabs Software Engineer Interview Questions & Rounds

29 min read

How the HiLabs software engineer interview works: OA with MCQs, DSA and SQL technical rounds, design and HR rounds, from real candidate experiences.

In this article
On this page

[Draft] How to Crack HiLabs: The Software Engineer Interview, From Real Experiences

Last updated November 20, 2026 · 26 min read · For campus new grads, SDE II, senior engineers and technical leads

Built by the Codinzhub team. This guide is built from HiLabs software engineer interview experiences that candidates shared, including an experience and OA questions on Codinzhub. The process changes by year, campus and level, so treat this as a map, not a promise.

The 30-second version. For HiLabs software engineers, mostly hired through IIT campus drives in India, the process starts with an online assessment: MCQs plus 2 coding questions in the reports that give a count, with one sitting at 60 minutes. Campus candidates then had 2 or 3 interviews, mostly technical, with an HR round at the end in some reports, and the 3 campus reports that give timing were decided in 1 or 2 days. Campus technical rounds mixed one DSA problem with SQL, CS fundamentals and questions on your resume. SDE II and senior candidates added design or architecture questions, and two of them had a managerial round. The habit that matters most: think out loud, state complexity and edge cases, and be honest about what you do not know.

What this guide is, and what it is not

This guide is built from 22 HiLabs software engineer reports from 2022 to 2026: 13 interview experiences from 12 candidates, and 9 online-assessment sittings shared on Codinzhub. They cover campus new grads, SDE II and senior engineers; every location stated is in India. Most reports are from IIT campus drives, and experienced-hire reports are short.

It is:

  • A map of the process, stage by stage, as candidates described it
  • The question patterns that keep coming back, and the follow-ups to expect
  • A six-week plan and practice problems matched to those patterns

It is not:

  • A list of leaked questions or a promise of what you will be asked
  • An official description of HiLabs's process
  • An offer rate. Outcomes in candidate posts are self-reported and are not a statistical sample.

Important things to know before you start

These are the HiLabs-specific facts that change how you prepare.

The OA tests more than coding. In the reports that describe the test, coding sat next to MCQs: OS, OOP, DBMS and C++ in 2022, Java and JavaScript fundamentals in an off-campus test, and 35 AI/ML questions in one IIT BHU section. One 2022 test allowed Java only, so check the allowed languages in your invite.

SQL is an interview topic. Three candidates were asked SQL inside a technical interview, from an easy GROUP BY and JOIN query to a temporary-table query and inner vs outer joins. A fourth had database deep dives in a design round.

Framework depth is tested. In 5 of the 20 technical reports, interviewers went deep on frameworks and languages: React-Redux (from an internship on the resume), JavaScript, Spring Boot, dependency injection, Java multithreading. Only list tools you can explain.

Round-by-round breakdown

Candidates described five stages: application, shortlisting, an online assessment, the interview rounds (technical, then design for experienced hires, then HR or managerial), and the decision.

Stage 1: Application, where candidates applied

Most software engineer evidence comes from Indian campus drives, mainly IITs. Experienced hires applied online or through a recruiter. Offices named in the reports are Bengaluru, Pune and Chennai.

ChannelWhat candidates said
Campus placementThe largest group: 6 campus interview reports (IIT BHU 2022, an IIT Kanpur report posted in 2023, Chennai and Pune in December 2024, and two IIT Kanpur reports from the 2025 season that may describe the same drive), plus OA questions shared on Codinzhub from IIT Bombay, IIT Kharagpur, IIT BHU and IIT Roorkee (one of them off-campus).
Applied online or on the company website3 candidates: a 2025 SDE whose process took 2 months and ended without an offer, a Technical Lead who was not selected, and a senior engineer (posted 2022) who got an offer.
Recruiter outreachOne senior engineer in Bengaluru (2025) was approached by a recruiter. The process took 1 week.
Hiring challengeHiLabs's Code Wizard contest page targets Java Full Stack and Java Big Data professionals with over five years of experience; winners get a direct interview, subject to HR and hiring-panel approval.

What helped. The 2022 campus candidate said to read the job description carefully before the drive. A 2025-26 campus hire prepared with Striver's sheet, LeetCode and NeetCode.

Stage 2: Shortlisting, how candidates moved forward

Shortlisting is thinly reported for software engineers. In the one campus report with numbers, the OA cut the list sharply; for experienced hires, one candidate described an intro call before the interviews.

  1. Campus shortlist and the OA cut (one 2022 report). At IIT BHU in 2022, 162 students opted in, over 100 were shortlisted, and 43 were called to interviews after the online assessment. That candidate solved 7 of 10 MCQs and one of the two coding problems and still made the interview list, so a partial score was enough that year.
  2. Intro call (one 2025 report). A candidate who applied online for an SDE role had an intro call, then interviews of 1 hour each. The whole process took 2 months.

No software engineer report describes a recruiter questionnaire, a personality test or a transcript request. No report gives a CGPA cutoff for SDE roles.

What candidates advised. Read the job description carefully before the drive, and be honest in the interviews about what you do not know.

Stage 3: Online assessment

Campus candidates and some experienced candidates took an online assessment (OA), a timed test of MCQs and coding problems, before any interview. No report describes a separate phone screen.

Online assessment

How it works. The OA mixes multiple-choice questions with coding. In 2022 the IIT BHU test had 10 MCQs on OS, OOP, DBMS and C++ and two coding problems worth 20 and 50 points. Tests shared on Codinzhub look bigger: an IIT BHU sitting had 3 sections with 35 AI/ML questions in the first (one page calls it 35 data-science MCQs plus 5 SDE subjective questions), an IIT Kharagpur question came from section 3, and an off-campus test had 34 MCQs on Java and JavaScript fundamentals. An IIT Roorkee on-campus test had 2 coding questions in 60 minutes. One 2025-26 IIT Kanpur SDE named HackerRank as the platform. One 2022 test allowed Java only. No report mentions AI tools.

At a glance

  • Length: 60 minutes in the one IIT Roorkee sitting that states it; not reported elsewhere
  • Questions: 2 coding questions in each of the 3 reports that give a count, with MCQs in 2 of them
  • What was asked: MCQs on CS fundamentals, Java, JavaScript, SQL, React, Spring and AI/ML; coding on graphs, arrays, math and linked lists
  • Most common: No single repeated question

OA questions shared on Codinzhub. These pages show only the title, college and OA date publicly. Where the technique is not visible, the topic is marked Not reported.

QuestionDriveTopic
Number of connected components via LCMIIT Bombay, 2 November 2026Graphs
Graph: count paths with an even total weightIIT Kharagpur, 2 November 2026Graphs (directed, weighted)
Charging units in a rowIIT BHU, 29 October 2026Arrays
Maximum number of operationsIIT BHU, 5 November 2026Not reported
Reverse linked list number additionIIT BHU, date not shownLinked lists
Maximum bitwise AND value across permutation cyclesOff-campus (IIT Roorkee candidate)Bit manipulation
Maximum MEX after decreasing array elementsOff-campus (IIT Roorkee candidate)Arrays
Count distinct numbers divisible by KIIT Bombay (AI Engineer)Math

Five more OA questions (maximum number of toys, find product, reverse number, a connected-components problem from IIT Roorkee, and count distinct characters in a string) are in the question bank.

Stage 4: The interview loop

Campus loops had 2 or 3 interviews, mostly technical. Two campus reports had a separate HR round at the end, and a third folded HR questions into the last technical interview. The 3 campus reports that give timing were decided in 1 or 2 days. The fullest experienced report (SDE II) had a DSA round, a machine coding or design round and a managerial round. Interviews were 30 minutes each in one 2025 campus report and 1 hour each in one 2025 experienced report; no other report gives a length.

Technical interviews (DSA, SQL and your resume)

At a glance

  • Length: 30 minutes per round in one 2025 campus report; not reported elsewhere
  • Questions: 1 or 2 coding problems plus SQL, CS-fundamentals or framework questions per round
  • What was asked: DSA (dynamic programming, binary search, hashing and tries, linked lists, arrays), SQL, your resume and internship projects, and web or Java framework depth
  • Most common: No single repeated question

Four of the 9 candidates with a technical round described the same campus mix: one DSA problem, then resume or internship discussion, SQL and CS fundamentals. SQL came up in the interview for 3 candidates. Framework questions covered React-Redux (from an internship on the resume), JavaScript, and Java, Spring Boot and React for experienced hires.

Several reports name only the topic of the coding problem: binary search, then trie and hashing (IIT Kanpur, 2025), a LeetCode-medium linked list with some OS questions (Chennai, 2024), an array problem (SDE II) and DSA puzzles (IIT Kanpur, posted 2023). The 2022 candidate said interviewers were friendly and gave hints. The reports disagree on DSA weight: a December 2024 Pune candidate said DSA "was not asked much", while a Chennai candidate that month said the rounds focused on DSA and CS fundamentals.

QuestionFollow-upLevel
1-D DP problem, then a 2-D DP from recursion to optimised DPHow many recursive calls, then how many distinct solutionsNew grad
SQL: easy query using GROUP BY and JOINNot reportedNew grad
Two medium SQL queries, one needing a temporary tableThe second was tricky; hints were givenNew grad
Blind man and pills puzzleNot reportedNew grad
Print every element of a nested array in JavaScriptNot reportedNew grad
Write code for the roots of a quadratic equationNot reportedSDE II
Inner vs outer joins, then optimising queries in a NoSQL databaseNot reportedSDE II
What is dependency injection?Not reportedSDE II

React-Redux (advantages, hooks, lifecycle), cookies and a "Remember me" login, Spring Boot controllers, and Java streams, lambdas and multithreading are in the question bank.

Machine coding, LLD and system design (experienced hires)

At a glance

  • Length: 1 hour per interview in one 2025 report
  • Rounds: 1 design-focused round in the SDE II report; a 2025 SDE loop was mostly design and databases
  • What was asked: high-level design, database choice, machine coding and low-level design (LLD, class-level design), microservices and design patterns, and your current architecture
  • Most common: No design repeated

No campus report describes a system design round. Among 4 experienced candidates, a 2025 SDE had 1-hour interviews on system design and database deep dives, and a Technical Lead was asked about microservices and a design pattern. HiLabs's reply to one review says its rounds reflect the distributed systems and architecture work its teams do.

Reported designs.

  • Design a distributed cache system (SDE II, machine coding and high-level design round)
  • Design a hotel booking platform, choosing between SQL, NoSQL and document databases (SDE, 2025)
  • Explain your current role and your system's architecture (senior engineer, 2025)

HR and managerial round

At a glance

  • Length: Not reported
  • Questions: Not reported
  • Themes: your resume, why you are moving, experience-based managerial questions, business awareness

On campus the HR round came last (Chennai 2024; IIT Kanpur 2025-26, where it was called "tricky"), or HR questions were folded into the last technical interview (Kanpur 2025). In 2022 at IIT BHU there was no separate HR round. Experienced loops ended with a managerial round (SDE II and a senior engineer in 2025). Only 2 actual prompts were reported for software engineers.

Reported questions.

  • How could a recession affect the company? (new grad, 2022)
  • Why are you looking for this change? (senior engineer)

See all HR questions in the question bank.

Stage 5: Decision and offer

Decision. No report describes a hiring committee, team matching or a level change. On campus the decision was fast: 1 day for the Chennai and Pune candidates in December 2024, and 2 days for an IIT Kanpur candidate in November 2025. In 2022 at IIT BHU the OA was on 2 November and both technical interviews were on 1 December.

Experienced timelines. These varied from 5 days (a 2022 full-stack Java candidate) and 1 week (a senior engineer in 2025) to under 2 weeks (an SDE II in 2025 and a Technical Lead) and 2 months (an SDE who applied online in 2025).

Outcomes. Of the 12 software engineer candidates with a known outcome, 9 received an offer or were selected (2 of them declined it) and 3 did not get an offer. The data leans towards people who were selected, so do not read it as a pass rate.

Offer. No report gives verified compensation details, so this guide does not include any.

The Codinzhub Next-Round Playbook

Candidates who moved forward at HiLabs did not ace everything; they cleared the OA cut, then explained their own projects and SQL clearly.

To get past the online assessment

  • Do not skip the MCQs. Reported OAs had 10 MCQs on OS, OOP, DBMS and C++ (2022), 34 MCQs on Java and JavaScript fundamentals (off-campus), and 35 AI/ML questions in one IIT BHU section. Revise CS fundamentals and, for AI-adjacent roles, ML systems.
  • Bank the easier coding problem first. In 2022 the problems carried 20 and 50 points; one candidate solved 7 MCQs and only the 20-point problem and still reached interviews.
  • Budget for 2 coding questions in about 60 minutes, the one length reported (IIT Roorkee).

To get past the technical interviews

  • Explain the brute force, then optimise while talking. The 2022 hire went from recursion to an optimised DP and then faced questions on the number of recursive calls.
  • Treat SQL as an interview topic. It came up in the technical rounds for 3 candidates, from GROUP BY and JOIN to a temporary-table query.
  • Expect framework questions: React-Redux (from an internship on one resume), JavaScript, Spring Boot and Java all came up.
  • Use hints. The 2022 candidate was given hints and was selected.

To get past the machine coding and design round

  • For SDE II and above, prepare one high-level design end to end. Reported prompts were a distributed cache and a hotel booking platform.
  • Be ready to compare SQL, NoSQL and document databases with a concrete reason for your choice.
  • Know your current system's architecture well enough to draw it, as one senior engineer was asked to.

To get past the HR and managerial round

  • Prepare a clear answer to "why this change?" if you are switching jobs, as one senior engineer was asked.
  • Read about HiLabs before the drive. One campus interview ended with a question on how a recession could affect the company.
  • Expect it to be a real round. One 2025-26 IIT Kanpur hire called it "tricky".

How the loop differs by level

The loop has the same core at every level (a coding check, then interviews and an HR or managerial round), but campus loops lean on DSA, SQL and your resume, while experienced loops add machine coding, design and framework depth.

LevelWhat candidates describe
New grad (campus SDE)An OA with MCQs and 2 coding questions, then 2 or 3 interviews, with an HR round at the end in some reports; the 3 campus reports that give timing were decided in 1 or 2 days. Based on 6 campus interview reports plus Codinzhub OA pages. Examples: a 1-D then 2-D DP problem, an easy GROUP BY and JOIN query, printing a nested array in JavaScript, and binary search and trie topics. No campus report describes a system design round.
SDE IIBased on two reports. One loop had 3 rounds: a medium DSA problem with LLD, Java and React questions; a machine coding or high-level design round (design a distributed cache); and a managerial round. The other covered quadratic-equation code, SQL joins, NoSQL query tuning, dependency injection and Spring Boot controllers.
Senior SWE and Technical LeadBased on three reports. A 2025 senior engineer had 2 DSA rounds and a managerial round and was asked to explain their current architecture. A Technical Lead took coding tests, then a one-on-one on microservices and a design pattern. An older senior report lists only "why this change". System design or architecture shows up in 2 of the 3.
SDE, level not statedBased on two reports. A 2025 online applicant had an intro call and 1-hour interviews on system design, SQL and databases (a hotel booking platform). A 2022 full-stack Java candidate had an OA in Java only, then a round on Core Java, Spring Boot, streams, lambdas and multithreading.

Most-asked topics

Across 20 reports that describe a technical stage (including 9 OA sittings shared on Codinzhub), questions concentrated in a few areas. The surprise is how often SQL and framework questions sit next to DSA.

TopicWhat it meansSeen inReported examples
Arrays, strings and mathIndex work on lists and text, plus number properties like divisibility or roots9 of 20 reportsCharging units in a row; maximum MEX after decreasing array elements; roots of a quadratic equation
SQL and databasesWriting joins and GROUP BY queries, and choosing a database5 of 20 reportsEasy GROUP BY and JOIN query; two medium SQL queries with a temporary table; inner vs outer joins
Framework depth (web, Java and Spring)Explaining the libraries on your resume: React, JavaScript, Spring Boot, Core Java5 of 20 reportsReact-Redux hooks and lifecycle; dependency injection; Spring Boot controllers
GraphsNodes joined by edges; counting components or paths4 of 20 reportsNumber of connected components via LCM; count paths with an even total weight
System design and architectureDesigning a service at a high level and defending the choices4 of 20 reportsDistributed cache; hotel booking platform; explain your current architecture
Linked lists, binary search, hashing and triesClassic data-structure problems named by topic in campus interviews3 of 20 reportsReverse linked list number addition; binary search and trie questions (titles not reported)
CS fundamentalsOperating systems, OOP and DBMS concepts, often as MCQs2 of 20 reports10 MCQs on OS, OOP, DBMS and C++; a few OS questions in a campus interview
Dynamic programmingBuilding answers from smaller subproblems1 of 20 reports1-D DP, then a 2-D DP from recursion to optimised DP

The question patterns that keep coming back

The HiLabs questions in this dataset fall into five patterns. Most OA statements are paywalled, so learn the pattern behind each title rather than a memorised solution.

1. Arrays, strings and math

The widest pattern: 9 of 20 technical reports touch it, mostly OA questions on arrays, counting and number properties, plus quadratic-equation code (SDE II) and a nested-array question in JavaScript (campus). For "count distinct", use a hash set. For divisibility, count values by remainder. For "MEX" (the smallest missing non-negative number), sort or count, then walk upward. For math code, say the edge cases out loud: a zero leading coefficient, a negative discriminant.

Reported examples. Charging units in a row; maximum MEX after decreasing array elements; count distinct numbers divisible by K; count distinct characters in a string; write code for the roots of a quadratic equation; print every element of a nested array in JavaScript.

2. Framework depth from your resume

Five reports describe interviewers going deep on frameworks and languages: React-Redux, then cookies and a "Remember me" login for a 2022 campus hire; dependency injection, Spring Boot controllers, streams, lambdas and multithreading for Java candidates. The rule: for every technology on your resume, be ready to explain the problem it solves, its core mechanism and one trade-off.

Reported examples. React-Redux: advantages, hooks, lifecycle phases and methods; how cookies and a "Remember me" login work; what is dependency injection; what are controllers in Java Spring Boot; Java depth on streams, Consumer, lambdas, multithreading and interfaces.

3. SQL and databases

SQL appears in 5 of 20 technical reports. In 3 it was a technical-interview question, and in a fourth it was part of a design round. Questions start easy (GROUP BY with a JOIN) and then add a step: a temporary table, a tricky condition, or relational vs NoSQL storage. For multi-step questions, build the query in stages with a common table expression or temporary table, then check NULLs, duplicates and ties.

Reported examples. SQL: easy query using GROUP BY and JOIN; two medium SQL queries, one needing a temporary table; inner vs outer joins, then optimising queries in a NoSQL database; design a hotel booking platform, choosing between SQL, NoSQL and document DBs.

4. Graphs and connected components

Graphs show up in 4 of 20 reports, all in OAs: a 50-point graph problem in 2022, two campus questions dated November 2026 and one undated. "Connected components" points to union-find (merge groups as you read edges) or a DFS from each unvisited node. When edges come from a number rule such as a shared factor or LCM, connect each value to its divisors instead of comparing every pair. For "paths with an even total weight", carry the parity of the path weight in the state.

Reported examples. Number of connected components via LCM; graph: count paths with an even total weight; connected components (IIT Roorkee, question 1 of 2).

5. System design and architecture

Design shows up only for experienced hires: 4 of 20 technical reports, and no campus report. Expect a machine coding or high-level design round at SDE II and above, and questions about the system you work on now. Start with requirements and scale, then the data model, APIs and the bottleneck. For a cache, cover eviction, consistency and key partitioning; for a booking system, start from double booking.

Reported examples. Design a distributed cache system; design a hotel booking platform, choosing between SQL, NoSQL and document DBs; explain your current role and your system's architecture.

Less common: three campus reports name linked lists, binary search, or tries and hashing as interview topics without giving the problem.

Preparing for the HR and managerial round

The HR or managerial round came last in most of the reports that describe it (see Stage 4), but software engineer candidates reported only 2 actual prompts, so prepare from your own experience rather than from a list.

Build your story bank. Prepare six to eight real stories, each under two minutes, each ending in a result you can state. Cover the themes candidates were actually asked about:

ThemeReported prompt (paraphrased)Follow-up to expect
Motivation for the moveWhy are you looking for this change? (senior engineer)Not reported
Business awarenessHow could a recession affect the company? (new grad, 2022)Not reported
Your experienceExperience-based managerial questions (SDE II)Not reported
Your resumeHR-style questions mixed with resume discussion (IIT Kanpur, 2025)Not reported

Know the company. The business-awareness question suggests interviewers want you to know the company. Read HiLabs's product pages before the drive and prepare one or two questions about its products.

Structure each story. Give the situation in one line, then what you did (say "I", not "we"), the result, and what you would do differently. Use real experiences only.

Expect depth. One 2025-26 IIT Kanpur hire called the HR round "tricky" without saying why. A Data Science candidate at the December 2024 IIT BHU drive described a long, personal HR conversation with situational questions on disagreeing with a senior manager and on an impossible client deadline; that is a different role, so treat it only as a hint.

A six-week plan

The plan follows the patterns above, most common first, and ends with timed mocks that feel like the real rounds. Plan on two to three focused hours a day.

  1. Week 1: Arrays, strings and math. Counting with hash sets, divisibility and remainders, MEX, sorting with a greedy pass, and math code with edge cases. Habit: write the time complexity next to every solution.
  2. Week 2: SQL and CS fundamentals. GROUP BY with JOIN, inner vs outer joins, multi-step queries with a common table expression or temporary table, plus OS, OOP and DBMS MCQ revision. Habit: test every query against NULLs, duplicates and ties.
  3. Week 3: Your resume stack. For each framework you list (React, JavaScript, Java, Spring Boot), revise how it works: hooks and lifecycle, cookies and sessions, dependency injection, controllers, streams, lambdas and threads. Habit: explain each one out loud in two minutes.
  4. Week 4: Graphs. Connected components with union-find and DFS, components defined by a number rule, and path counting with a parity state. Habit: draw the graph before writing any code.
  5. Week 5: Lower-frequency patterns. Linked lists, binary search, hashing and tries, and dynamic programming from recursion to memoisation. Experienced candidates: add system design (a cache, a booking system) and one machine coding exercise.
  6. Week 6: Mocks. Take two timed 60-minute OAs with MCQs and 2 coding questions, then four 30-to-60-minute mock interviews that each mix one DSA problem, one SQL question and resume questions. Rehearse your HR answers out loud.

New grads can keep system design to a light read; no campus report had a design round. SDE II and senior candidates should start system design and machine coding in week 2 alongside SQL.

Only two weeks? Spend four days on arrays, strings and math, three on SQL and CS fundamentals, two on your resume stack, two on graphs, and three on timed OAs, mock interviews and HR answers.

Practice problems that match these experiences

These are well-known practice problems that match the patterns above. They are not claims about HiLabs's question bank unless a row says the problem was asked as-is.

#Practice problemPatternSeen in these experiences as
1Smallest Missing Non-negative Integer After OperationsArrays, MEX with remaindersPractice for the MEX-style OA question (its statement is not public)
2Program to find the Roots of a Quadratic EquationMath, edge casesWrite code for the roots of a quadratic equation (SDE II)
3Flatten Deeply Nested ArrayRecursion over nested arrays in JavaScriptPrint every element of a nested array in JavaScript (campus, 2024)
4Department Highest SalarySQL JOIN with GROUP BYEasy SQL query using GROUP BY and JOIN (campus, 2022)
5Combine Two TablesSQL outer joinInner vs outer joins (SDE II)
6Number of ProvincesConnected components, union-find or DFSConnected-components OA questions
7Largest Component Size by Common FactorUnion-find over number factorsPractice for components defined by a number rule, such as the LCM components OA question
8LRU CacheCache eviction (hash map plus linked list)The eviction core of "design a distributed cache system" (SDE II)
9Unique Paths2-D DP, counting distinct solutionsA 2-D DP from recursion to optimised DP, with a follow-up on distinct solutions (campus, 2022)
10Add Two NumbersLinked-list traversal with carryLinked-list practice for the campus linked-list questions
11Implement Trie (Prefix Tree)TriesThe trie-and-hashing interview topic (campus, 2025)
12Puzzle: Blind man and PillsLateral reasoningAsked as-is in one report (campus, 2022)

How to handle a question you have never seen

Most OA statements are not public, so a repeatable method matters more than memorised solutions.

  1. Repeat the problem and one example. In an interview, say the input and output back and agree on a small case. In the OA, write that case as your first custom test.
  2. Say the brute force and its complexity. The 2022 campus hire started with plain recursion on a 2-D DP problem before optimising, and the follow-ups were about that recursion (how many calls, how many distinct solutions).
  3. Name the bottleneck. Repeated lookups suggest a hash set or map; groups that merge suggest union-find; a sorted or monotonic answer suggests binary search; "smallest missing value" suggests counting by remainder or sorting; a SQL question with two steps suggests a temporary table or common table expression.
  4. Say when you are stuck. HiLabs interviewers gave hints in the 2022 report, and the candidate who used them was selected.
  5. Code in small pieces while talking. State each helper's job before you write it. In the OA, solve the lower-point or easier problem fully before the harder one; one 2022 candidate reached interviews after solving only the first problem.
  6. Dry-run one case and fix the wrong line. Trace your example by hand, then try an edge case: an empty input, a single node, a NULL in SQL, a zero coefficient in math code. One candidate missed SQL edge cases even after hints.

Why candidates were rejected

Three software engineer candidates did not get an offer, and none of the three gave a reason. This section lists where candidates said they struggled instead. Treat it as a list of risks, not recruiter feedback.

  • Edge cases in SQL. The 2022 campus candidate said they followed the interviewer's hints on a tricky SQL query but still missed some edge cases. They were selected anyway, but SQL depth is tested in the interview, not only in the OA.
  • Gaps next to your own stack. The same candidate had React-Redux on the resume and was then asked backend questions on cookies and a "Remember me" login. They said their backend experience was limited and shared only a basic understanding. They recommended being honest; the safer fix is to know the basics one layer beyond what your resume lists.
  • Long process, no reason given. A 2025 SDE who applied online went through an intro call and 1-hour interviews on design and databases over 2 months and received no offer. A Technical Lead was not selected after coding tests and a microservices and design-pattern round. A 2022 full-stack Java candidate was not selected after a round on Spring Boot, Core Java and multithreading.
  • Interviewer mismatch for senior candidates. One senior engineer said the DSA rounds were taken by engineers who seemed junior and did not follow the system design they explained. They received an offer and declined it. This is one candidate's view.

Selected vs. rejected: do this, not that

No selected candidate described a perfect interview. What repeated were a few habits, and the gaps candidates admitted show what skipping them costs.

Do thisNot thatWhat the reports show
Think out loud: state assumptions, constraints and complexity as you goSilent coding: writing a solution with no narrationThe 2022 campus hire listed thinking out loud, stating assumptions and sharing time complexity as their main takeaways, and was selected.
Recursion first, then optimise: start with the plain recursion, then add memoisationJumping to a half-remembered DP tableThe same candidate moved from a recursive approach to an optimised DP and answered follow-ups on the number of recursive calls.
Check SQL edge cases: NULLs, duplicates, ties, empty groupsStopping at the first query that runsOne candidate followed hints on a tricky SQL query but still missed edge cases.
Know your resume stack in depth: mechanism, trade-offs, one bug you fixedListing tools you used onceInterviewers went deep on React-Redux, Spring Boot, dependency injection and Java multithreading in 5 of the 20 technical reports.
Be honest about gaps: say what you know and where it stopsBluffing an answerThe 2022 hire said they told the interviewer their backend experience was limited, shared their basic understanding, and still got the offer.

If you remember only five things

  1. The process is short. An OA with MCQs and 2 coding questions, then 2 or 3 interviews; the 3 campus reports that give timing were decided in 1 or 2 days.
  2. Campus technical rounds are a mix. One DSA problem, then SQL, CS fundamentals or framework questions, then your resume.
  3. Think out loud and be honest. The 2022 hire credited thinking out loud, stating complexity and edge cases, and admitting gaps.
  4. The core topics. Arrays, strings and math in the OA; SQL and your resume stack in interviews; graphs in campus OAs; system design only for experienced hires.
  5. Practise the real format. Timed OAs with MCQs, then mock interviews that mix one DSA problem with SQL and resume questions.

FAQ

Does everyone take an online assessment?

No, not in every report. Campus candidates took an OA, and so did a 2022 full-stack Java candidate and a Technical Lead, but a 2025 SDE who applied online described an intro call and then interviews and mentions no test.

Do I need dynamic programming?

Learn the basics. Only one report, from 2022, describes a DP interview problem (a 1-D problem, then a 2-D problem from recursion to optimised DP).

Is system design asked?

Only for experienced hires in this data. The SDE II report had a machine coding or high-level design round (a distributed cache), a 2025 SDE was asked to design a hotel booking platform, and no campus report describes a design round.

How long does it take?

On campus, 1 or 2 days in the 3 reports that give timing. Experienced candidates reported 5 days to 2 months.

Will the interviewer help me?

In the 2022 campus report, yes: interviewers were friendly and gave hints, and the candidate was selected after using them.

About this guide

The Codinzhub team researched and wrote this guide from 22 HiLabs software engineer interview reports from 2022 to 2026, including an experience and OA questions shared on Codinzhub. We kept only what candidates described. The questions are our own short summaries, and the practice links are similar problems, not the exact interview questions, unless marked exact. If you interviewed recently, share your experience on Codinzhub and we will update this guide.

Disclaimer. HiLabs's process changes by role, year, campus and office. Use this guide to build a foundation, and confirm the current format with your recruiter or placement cell.

Search the question bank

The questions from each round above, with practice links for similar problems. Log in to search every question we collected for this role, including questions shared on Codinzhub.

Showing 20 of 58 questions

  • Number of connected components via LCM

    A Hilabs online assessment question shared on Codinzhub (IIT Bombay, 2 November 2026).

    On CodinzhubIIT Bombay, 2 November 2026GraphsCodingOnline assessment
  • Graph: count paths with an even total weight

    A Hilabs online assessment question shared on Codinzhub (IIT Kharagpur, 2 November 2026).

    On CodinzhubIIT Kharagpur, 2 November 2026Graphs (directed, weighted)CodingOnline assessment
  • Charging units in a row

    A Hilabs online assessment question shared on Codinzhub (IIT BHU, 29 October 2026).

    On CodinzhubIIT BHU, 29 October 2026ArraysCodingOnline assessment
  • Maximum number of operations

    A Hilabs online assessment question shared on Codinzhub (IIT BHU, 5 November 2026).

    On CodinzhubIIT BHU, 5 November 2026Not reportedCodingOnline assessment
  • Reverse linked list number addition

    A Hilabs online assessment question shared on Codinzhub (IIT BHU, date not shown).

    On CodinzhubIIT BHU, date not shownLinked listsCodingOnline assessment
  • Maximum bitwise AND value across permutation cycles

    A Hilabs online assessment question shared on Codinzhub (Off-campus (IIT Roorkee candidate)).

    On CodinzhubOff-campus (IIT Roorkee candidate)Bit manipulationCodingOnline assessment
  • Maximum MEX after decreasing array elements

    A Hilabs online assessment question shared on Codinzhub (Off-campus (IIT Roorkee candidate)).

    On CodinzhubOff-campus (IIT Roorkee candidate)ArraysCodingOnline assessment
  • Count distinct numbers divisible by K

    A Hilabs online assessment question shared on Codinzhub (IIT Bombay (AI Engineer)).

    On CodinzhubIIT Bombay (AI Engineer)MathCodingOnline assessment
  • 13

    A Hilabs online assessment question shared on Codinzhub (IIT Bombay AI Engineer OA; statement paywalled Strings Online assessment AI Engineer (campus).

    On CodinzhubIIT Bombay AI Engineer OA; statement paywalled Strings Online assessment AI Engineer (campusCount distinct characters in a string: Second coding question from the same IIT Bombay AI Engineer OA; statement paywalledCodingOnline assessment
  • 1-D DP problem, then a 2-D DP from recursion to optimised DP

    Level: New grad.

    How many recursive calls, then how many distinct solutionsCodingRound not stated
  • SQL: easy query using GROUP BY and JOIN

    Level: New grad.

    Not reportedCodingRound not stated
  • Two medium SQL queries, one needing a temporary table

    Level: New grad.

    The second was tricky; hints were givenCodingRound not stated
  • Blind man and pills puzzle

    Level: New grad.

    Not reportedCodingRound not stated
  • Print every element of a nested array in JavaScript

    Level: New grad.

    Not reportedCodingRound not stated
  • Write code for the roots of a quadratic equation

    Level: SDE II.

    Not reportedCodingRound not stated
  • Inner vs outer joins, then optimising queries in a NoSQL database

    Level: SDE II.

    Not reportedCodingRound not stated
  • What is dependency injection?

    Level: SDE II.

    Not reportedCodingRound not stated
  • Arrays, strings and math

    Level: 9 of 20 reports.

    Index work on lists and text, plus number properties like divisibility or rootsCodingRound not stated
  • SQL and databases

    Level: 5 of 20 reports.

    Writing joins and GROUP BY queries, and choosing a databaseCodingRound not stated
  • Framework depth (web, Java and Spring)

    Level: 5 of 20 reports.

    Explaining the libraries on your resume: React, JavaScript, Spring Boot, Core JavaCodingRound not stated
Page 1 of 3

Keep preparing on Codinzhub

Ready for the next topic?

Keep track of what you’ve learned.