Hitachi Consultancy Interview Experience | Set 3 (On Campus)
Question Details
Round 1 Online test(major elimination)SureShot answer is the key point here, don’t try to attempt all, attempt only those with which you are fully confident because here ...
Full Details
Round 1 Online test(major elimination) SureShot answer is the key point here, don’t try to attempt all, attempt only those with which you are fully confident because here correct answer marking is +1 and wrong answer marking is -2. It consists of two sections: aptitude and technical In the aptitude part, there will be quantitative problems, English grammatical questions, logical questions, and also questions were there from HDFS(Hadoop File System). In the technical round, there will be MCQ questions from: C C++ JAVA DBMS and some programs (C, C++, JAVA) are used to predict output.
Round 2 Case study-based , GD (major elimination) They can give any case study topic. You will be given 10 minutes to read the cases and prepare your points, then you will be called for the GD. In my case, the GD topic was related to survival. Tip: practice some case studies based GD.
Note From GfG Team: For confidentiality reasons, we cannot share the details of case study.
Round 3 Technical interview(major elimination) Here, they will throw questions at you from every aspect C, C++, SQL, automata , DS and they will ask you about your project works too(if any).
Round 4 HR interview This is a minor elimination round. Generally 70% candidates from the previous technical round get selected for the job.
About This Question
This is a reported interview question from a hitachi consultancy interview for a quant role during the oa round reported in 2025.
It covers the following topics: Sql .
Topics
More Hitachi Consultancy Interview Questions
About Hitachi Consultancy Interview Reports
This question was reported by a candidate who interviewed at Hitachi Consultancy. 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 Hitachi Consultancy are the higher-signal extractions to take from this report.
For broader preparation context, the Hitachi Consultancy 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 Hitachi Consultancy reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Hitachi Consultancy 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 Hitachi Consultancy 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.