A Business Analyst candidate at RSM US described three roughly thirty-minute interviews with partners and managers, focused on fit, teamwork and travel, with one question on valuation basics and a slow decision.
$93K
Avg. Base Comp
$105K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
One candidate who interviewed for a Business Analyst role at RSM US described three interviews of about thirty minutes each, spread over a few weeks and run by different partners and managers rather than people from the team they would join.
The conversations were about personality and experience, not technical testing. Expect opening questions like "Why RSM? Why consulting?", followed by behavioral questions on how you work in teams, including whether you tend to take charge or hold back. Interviewers also asked about the candidate's background, their expectations for the role and their willingness to travel to multiple locations. One interviewer asked them to walk through finance concepts related to valuations, so it is worth brushing up on the basics even though no case work or heavy technical testing came up.
Candidates in related RSM roles describe a similar tone: relaxed, conversational and centred on why they chose the firm. Preparation is mostly about a clear motivation, a couple of teamwork examples and an honest position on travel.
Because the interviewers were not on the hiring team, the candidate left without a clear picture of the day-to-day work. Ask directly what the role involves. The same candidate waited about six weeks after the final interview before hearing a rejection, so follow up politely and keep other applications moving.
Synthesized from 15 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 Rsm Us Llp process.
I went through three back-to-back thirty-minute rounds for this role. The first was an HR screening to get to know my background, followed by a culture conversation with the vertical Partner who wanted to understand how I'd fit with the team and their work style. The final round was with a Director and involved a real case study based on one of their client engagements—I had to analyze an operational challenge and provide strategic and functional recommendations.
What struck me most was how conversational the whole process felt. The interviewers seemed genuinely interested in my experience and expertise rather than just checking boxes. They walked me through their client's situation and wanted to hear my thinking on how to solve it, which felt more like a real consulting scenario than a typical interview. The case study wasn't a theoretical puzzle; it was rooted in actual work they'd done, which made it both more challenging and more meaningful to prepare for.
The Partner in particular was skilled at drawing out my approach—not just what I'd recommend, but why I'd recommend it and what I'd consider in prioritizing across different functional areas. The whole experience took about ninety minutes total, and by the end I had a clear sense of what the role would actually involve. I received an offer shortly after.
Prep tip from this candidate
Prepare for a real client case study framed around operational or strategic challenges—not a textbook case. Review common consulting frameworks, but focus on asking clarifying questions and explaining your reasoning, not just arriving at an answer. The Partner interview is key; they're assessing both technical thinking and cultural fit.
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 Rsm Us Llp
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Longest Streak Users | |
| Size of Joins | |
| Top 3 Users | |
| Experiment Validity | |
| Bagging vs Boosting | |
| Hurdles In Data Projects | |
| Revenue Retention | |
| P-value to a Layman | |
| Sort Strings | |
| Fair Coin | |
| Resumable Fact Table Load | |
| Cyclic Detection | |
| Precision and Recall | |
| Assumptions of Linear Regression | |
| Duplicate Rows | |
| Forecasting New Year Revenue | |
| Classification and Regression | |
| Testing Price Increase | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| Using R Squared | |
| Late Deliveries | |
| Multicollinearity in Regression | |
| User Event Data Pipeline | |
| Swap Variables | |
| Mouse Search | |
| Seller Type Modeling |
Synthesized from candidate reports. Individual experiences may vary.
The Business Analyst candidate's early interviews were about thirty minutes and conversational. The standard opening questions were why RSM and why consulting. Interviewers were partners and managers, not necessarily people from the team the candidate would join.
Across the three interviews, questions covered how the candidate works in teams, whether they take charge or hold back, their background, expectations for the role and willingness to travel to multiple locations. One interviewer asked them to walk through finance concepts related to valuations. No case work or heavy technical testing was reported.
After the final interview, this candidate waited about six weeks before receiving a rejection and described the silence in the meantime as frustrating. They also said they never got much clarity on the day-to-day job, so ask about the role and the timeline before you leave each conversation.
