Interview experience
Birlasoft Interview Questions and Answers (2026)
Overview
Section titled “Overview”Birlasoft’s fresher process is rated easy-to-medium overall, but it stands out for two things most peers skip: a pre-recorded English/communication assessment ahead of the written test, and a direct HR question on night-shift comfort for client-facing accounts.
Birlasoft interview process at a glance
Section titled “Birlasoft interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| English/communication assessment (some drives) | 15-30 min | Listening and speaking tasks, pre-recorded |
| Online Written Test | 60-100 min | Programming (C/C++/Java), DBMS, OS, DS, architecture, testing, networking, aptitude, 2 easy coding questions |
| Technical Interview | ~30 min | Project discussion, SQL joins, ACID properties, tech-trend questions |
| Managerial/HR Interview | 20-30 min | Family background, motivation, 2-year plan, shift flexibility |
English/communication assessment
Section titled “English/communication assessment”Several Trainee Engineer and fresher drives open with a pre-recorded English assessment - listening comprehension and speaking tasks answered into a recorder rather than a live panel. It’s a screen on communication clarity, not technical knowledge, but candidates who skip practicing it can get filtered before the written test even starts.
Common questions
- Listen to a short passage and answer comprehension questions
- Speak for a set time on a simple prompt (e.g. describe your hometown or a hobby)
- Read a passage aloud clearly within a time limit
Online Written Test
Section titled “Online Written Test”A long-form test (up to about 100 minutes, roughly 120 MCQs on some drives) blending aptitude and reasoning with programming and CS-fundamentals questions across DBMS, OS, data structures, C/C++, software architecture, testing, and networking, plus two easy coding problems.
Common questions
- Quantitative aptitude and logical reasoning MCQs
- DBMS, OS, and data-structure fundamentals MCQs
- Remove all vowels from a given string
- Deduplicate and sort an array
Technical Interview
Section titled “Technical Interview”A relatively light, resume-anchored round - project walkthrough, SQL joins, ACID properties, and a couple of current-technology-trend questions. Not much heavy DSA; freshers report core Java, Spring Boot basics, HTML/CSS/React, and Git/Bitbucket familiarity being enough.
Common questions
- Walk through your final-year or internship project end to end
- Write a SQL query using an INNER JOIN vs a LEFT JOIN
- Explain the ACID properties of a database transaction
- What do you know about a recent technology trend relevant to your stack?
- Have you used Git or Bitbucket - describe your typical workflow
Full round-by-round narratives are on the Birlasoft interview experience page.
Managerial/HR Interview
Section titled “Managerial/HR Interview”A conversational closing round on family background, career motivation, and a 2-year plan - and, distinctively, a direct question on night-shift comfort since several Birlasoft accounts serve clients across time zones.
Common questions
- Tell me about your family background
- Why Birlasoft, and what do you know about the company?
- Where do you see yourself in the next 2 years?
- Are you comfortable working night shifts or rotational shifts for client accounts?
- Do you have any questions for the panel?
Sample answer frameworks for each of these are on the Birlasoft HR interview questions page.
Why the English assessment and shift question stand out
Section titled “Why the English assessment and shift question stand out”Two things separate Birlasoft’s process from a typical IT-services drive: a pre-recorded English/communication assessment before the technical stages even begin, and an explicit HR question on night-shift willingness. Both trace back to the same reason - Birlasoft’s enterprise accounts (SAP, Oracle, and other client-facing engagements) often run on client time zones and require clear, confident spoken English for client calls. Candidates who treat the English assessment as an afterthought, or dodge the shift question instead of answering it honestly, are the most common avoidable rejections reported.
Common technical interview questions and answers
Section titled “Common technical interview questions and answers”Q: Write a program to remove all vowels from a string.
The clean approach is a single pass with two indices into a character array: a read index that walks every character and a write index that only advances when the character is not a vowel. Check membership against the set a, e, i, o, u in both cases - lowercasing the character once is cleaner than listing ten literals - and finally truncate the result to the write index. That is O(n) time and O(1) extra space if the language lets you mutate the buffer, or O(n) space if strings are immutable, as in Java or Python, where you would append to a StringBuilder or list and join at the end. The point interviewers check is that you do not repeatedly concatenate onto a string inside the loop, since immutable-string concatenation makes the whole thing O(n squared).
Q: How would you deduplicate and sort an array?
Sort first with the library sort, which is O(n log n), then run a single pass with a write pointer that copies an element only when it differs from the previous kept element - that removes duplicates in place in O(n), so the total is O(n log n) time and O(1) extra space. The alternative is to insert everything into a hash set and then sort the set’s contents, which is also O(n log n) overall because the sort dominates, but uses O(n) extra space. If the values are integers within a small known range, counting sort with a boolean or frequency array drops it to O(n + k). Mention which one you would choose and why: in-place sort-then-scan when memory matters, hash set when you need to preserve first-occurrence order before sorting.
Q: What is the difference between an INNER JOIN and a LEFT JOIN?
An INNER JOIN returns only rows where the join condition matches on both sides, so unmatched rows from either table disappear from the result. A LEFT JOIN returns every row from the left table, filling the right table’s columns with NULL where there is no match - so if there are 100 employees and 90 have a department assigned, INNER JOIN gives 90 rows while LEFT JOIN gives 100. That NULL behaviour is exactly how you find missing relationships: SELECT e.name FROM employees e LEFT JOIN departments d ON e.dept_id = d.id WHERE d.id IS NULL; lists employees with no department. The trap is putting a condition on the right table in the WHERE clause instead of the ON clause, because a WHERE filter on a NULL-filled column silently converts your LEFT JOIN back into an INNER JOIN.
Q: Explain the ACID properties of a transaction.
Atomicity means the transaction is all or nothing - a funds transfer either debits one account and credits the other or does neither, with rollback undoing partial work using the undo log. Consistency means the database moves from one valid state to another, honouring every constraint, trigger, and foreign key. Isolation means concurrent transactions do not see each other’s uncommitted intermediate state, implemented by locking or by multi-version concurrency control, and tunable through the four isolation levels from Read Uncommitted to Serializable. Durability means once COMMIT returns, the change survives a crash, which is achieved by write-ahead logging - the log record is forced to stable storage before the commit is acknowledged, even if the data pages are still only in the buffer cache.
Q: Describe your Git workflow, and when would you rebase instead of merge?
The standard flow is to branch from the mainline for each feature or ticket, commit in small logical units, push the branch, and open a pull request for review before merging. Merge creates a commit with two parents and preserves the true history, which is what you want on shared branches; rebase replays your commits on top of the updated base, giving a linear history but rewriting commit hashes - so the rule is never rebase a branch that others have already pulled. Day to day, git pull --rebase keeps your feature branch current without cluttering it with merge commits, and an interactive rebase before review lets you squash noisy work-in-progress commits. Conflicts are resolved by editing the marked regions, staging with git add, and continuing the merge or rebase; git log and git diff on the two sides are what tell you which change should win.
Q: What is the difference between an abstract class and an interface?
An abstract class can hold state - fields, constructors, and fully implemented methods alongside abstract ones - and a class may extend only one of them, so it models an is-a relationship with shared implementation. An interface declares a contract; historically it held only method signatures and constants, and a class can implement many, which is how languages without multiple inheritance still get multiple capability. Modern Java blurs this with default and static methods in interfaces, but interfaces still cannot hold instance state or constructors, and their fields are implicitly public static final. Practically, reach for an abstract class when several subclasses genuinely share code and a base identity, and an interface when unrelated classes need to expose the same behaviour - Comparable and Serializable being the obvious examples.
Q: Compare arrays and linked lists.
An array stores elements in contiguous memory, so indexing is O(1) arithmetic on the base address and iteration is cache-friendly because entire cache lines of useful data are prefetched. Insertion or deletion in the middle costs O(n) because everything after the point must shift, and a fixed-size array must be reallocated and copied to grow, though amortised doubling makes append O(1). A linked list stores each element in a separate node with a pointer, so inserting or deleting given a reference to the node is O(1), but reaching the kth element takes O(k) traversal and every node carries pointer overhead with poor locality. In practice a dynamic array wins for most workloads because of cache behaviour, and linked lists earn their place mainly inside other structures - the recency list of an LRU cache, or collision chains in a hash table.
Q: What is the difference between a process and a thread?
A process is an independent execution unit with its own address space, code, data, heap, and file descriptors, so one process crashing does not corrupt another. A thread is a unit of execution within a process; threads share the heap, globals, and open files but keep their own stack, registers, and program counter, which makes creating and switching between them far cheaper than between processes. The shared memory is both the benefit and the risk - two threads updating the same variable without a mutex or atomic operation produce a race condition, and lock ordering mistakes produce deadlock. Inter-process communication needs an explicit mechanism such as pipes, sockets, message queues, or shared memory segments, whereas threads communicate simply by reading and writing the same objects.
Frequently asked questions about Birlasoft interviews
Section titled “Frequently asked questions about Birlasoft interviews”What is the Birlasoft interview process for freshers?
Birlasoft’s fresher hiring typically runs four stages: 1. English/communication assessment (some drives, 15-30 minutes) - pre-recorded listening and speaking tasks. 2. Online Written Test (about 60-100 minutes) - programming (C/C++/Java), DBMS, OS, data structures, architecture, testing, networking, and aptitude/reasoning/verbal sections, plus 2 easy coding questions. 3. Technical Interview (about 30 minutes) - resume/project discussion, SQL joins, ACID properties, and current tech-trend questions. 4. Managerial/HR Interview - family background, motivation, and a 2-year plan, plus willingness to work night shifts. Total timeline is usually a few weeks depending on the campus drive.
Does Birlasoft test spoken English before the technical rounds?
On several fresher/trainee drives, yes - a short pre-recorded English/communication assessment (15-30 minutes of listening and speaking tasks) runs before the main online test. It’s a filter on communication clarity, not a technical round, but skipping practice on it can cost you a shot at the written test.
What questions are asked in Birlasoft interviews?
Birlasoft interviews commonly cover core Java, Spring Boot basics, HTML/CSS/React for full-stack roles, SQL joins, DBMS/ACID properties, Git/Bitbucket familiarity, and questions drawn directly from your resume and projects. Heavy DSA is not the focus - most freshers report basic-to-medium coding at most. The HR round typically asks about willingness to work night shifts and what you know about Birlasoft.
How many rounds are there in the Birlasoft interview?
Birlasoft typically runs 3-4 rounds for freshers: an optional English assessment, an Online Written Test, a Technical Interview, and a Managerial/HR Interview. Some off-campus or lateral drives skip the English assessment and go straight from the written test to interviews.
How should I prepare for Birlasoft interviews?
For Birlasoft, revise core Java, HTML/CSS/React basics, SQL joins and ACID properties, and DBMS/OS/networking fundamentals for the written test, practise quantitative aptitude and verbal reasoning, and be ready to discuss whether you’re comfortable with night shifts since several Birlasoft accounts run on client time zones. If your drive includes an English assessment, practice speaking clearly and confidently into a recorder beforehand.