
One candidate's ABB Business Analyst interview began with an English test, then a group discussion, a personal case on mergers and strategy, and a hiring manager interview. Here is how to prepare.
$104K
Avg. Base Comp
$128K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
One candidate's ABB Business Analyst interview was substantial rather than a single conversation. The candidate started with a mandatory online English test, then moved into a group discussion built around business cases, a personal test case in English, and a final interview with the hiring manager. That candidate accepted an offer.
The analytical center of the process was the case work. The candidate was given about an hour for a personal case, and the questions centered on mergers and company strategy, particularly understanding past company decisions and how they would approach similar situations. Practicing merger and strategy scenarios, and explaining your reasoning aloud, looks like the most relevant preparation.
The group discussion was the most stressful part for this candidate, partly because it was held in Italian, which was not their first language. Language and format may vary by location, so ask the recruiter what to expect and be ready to contribute clearly in a group.
Behavioral questions were standard: tell us about yourself and describe a time you handled a difficult deadline. The hiring manager conversation was more relaxed and covered role details and expectations, leaving room for your own questions about the team. Because this is one candidate's account, treat the sequence as one example rather than a fixed format.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Abb process.
I applied to ABB and got through the initial screening phase, which involved a recruiter confirming my background and interest. After that, I had a Teams interview where the hiring manager asked me to walk through my experience — tell me about yourself, what your roles and responsibilities have been in previous positions, and how you've approached critical analysis in your work. The conversation then shifted into more technical territory specific to the role. They dug into my understanding of financial statements and month-end accounting processes, asking which entries typically repeat each cycle and how I'd handle the procedural side of closing. One question caught me off guard a bit: how would I navigate conflict if it came up in the role. It felt less like a technical question and more about temperament and problem-solving under tension. The whole Teams call lasted around an hour and felt collaborative rather than grilling. After that, I was invited onsite for a final interview. That visit was more in-depth — another conversation with the hiring manager and possibly other team members, though the details blur a bit. A few days after leaving, I got a verbal offer, which was followed up with the written offer shortly after. The process moved fairly quickly once I got past screening, and the team seemed genuinely interested in how I thought through problems rather than just quizzing me on definitions.
Prep tip from this candidate
Be ready to discuss your hands-on experience with month-end close procedures and the specific journal entries that repeat — this was a core focus. Also prepare for behavioral questions around conflict resolution and critical thinking, as those seemed equally weighted with technical knowledge in their assessment.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Abb
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Prime to N | |
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| Size of Joins | |
| Cyclic Detection | |
| Feature Store Integration | |
| Instagram TV Success | |
| Assumptions of Linear Regression | |
| Out of Stock Inventory | |
| Covariance vs Correlation | |
| Classification and Regression | |
| Seller Type Modeling | |
| SARIMA in Retail Forecasting | |
| Loan Model | |
| Multi-Reaction | |
| The Pirate’s Hunt | |
| D2C Socks e-Commerce | |
| Gas Station Counting | |
| String Palindromes | |
| Data Stream Median | |
| Safe Deployments | |
| Testing Constraints | |
| Search Timeout | |
| Your Strengths and Weaknesses | |
| Client Solution Pushback | |
| Alternative Vendor Tradeoff | |
| Expected Churn | |
| Tableau Filters and Parameters | |
| International e-Commerce Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports that the process began with a mandatory online English test sent before any interviews. Prepare as you would for a written language screen, and expect that it may gate whether you are called in for later stages.
The candidate reports a group discussion on business cases and found it stressful, partly because the discussion ran in Italian rather than their first language. Practice structuring a view, listening, and contributing concisely, and confirm the language with the recruiter.
The candidate reports a personal case in English with roughly an hour for analysis. Questions focused on mergers, company strategy, and understanding past company decisions. Practice breaking down merger scenarios and explaining how you would approach a similar decision.
The final stage was a conversational interview with the hiring manager. The candidate was asked to introduce themselves and describe handling a difficult deadline, then discussed role expectations and asked about the team. Have a concise story ready and prepare questions of your own.