State Street Business Analyst candidates describe a mix of screening tests, HR conversations and manager interviews covering SQL, finance basics such as the trade lifecycle, and behavioral stories about past projects.
$90K
Avg. Base Comp
$119K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for State Street Business Analyst or Associate roles describe a process that blends technical fundamentals, finance knowledge and conversational behavioral rounds. Three of the four candidates report three rounds. The fourth describes an initial assessment followed by technical rounds.
Finance content can catch people off guard. One candidate who did not receive an offer says the written test covered derivatives, FX and the trade lifecycle, and that they had prepared mainly for technical questions. A candidate who received an offer was also asked about derivatives, corporate actions, the trade life cycle and portfolios they knew.
SQL comes up in three of the four accounts. One candidate was asked to explain inner versus outer joins using a table example. Another mentions basic SQL functions. A third was asked about SQL, ETL and Python in the manager round. Two candidates were also asked about object-oriented ideas, including abstract classes, interfaces and whether you can create an object of an abstract class.
Behavioral preparation matters too. One candidate describes an HR introduction followed by hiring-manager and team-member rounds focused on business planning, successful projects and handling challenges. Another was asked about a creative problem solved, a major college project, five-year goals and Excel experience. A third was asked why they wanted to work in finance and at State Street. The interviewers are generally described as friendly and the questions as fair rather than puzzle-style. Three candidates received offers and one did not. Bring concrete project examples, review the finance basics, and practice explaining SQL joins aloud.
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 State Street process.
I interviewed at State Street for a Business Analyst role and went through a three-round process. The first round was a written test covering financial concepts — they asked me about derivatives, FX, and trade lifecycle, which caught me off guard since I'd prepped mainly for technical questions. I did okay but realized quickly I needed to brush up on finance fundamentals, not just coding.
The second round was with HR, which was straightforward — typical behavioral stuff like telling them about myself and my background. Nothing too intense there. Then came the manager round, where things got more technical. They dug into my resume experience and asked me about SQL, ETL, and Python. There was a focus on object-oriented design principles too — they asked whether you could create an object of an abstract class, which was testing whether I understood inheritance and OOP concepts at a deeper level. The conversation was pretty casual overall; they didn't seem to care much about polished behavioral answers, more about how I actually thought through technical problems.
What surprised me most was how much the financial domain knowledge mattered. I'd assumed a Business Analyst role at an investment firm would be primarily technical, but they clearly wanted people who understood derivatives, trade lifecycles, and FX basics. The technical round itself wasn't impossibly hard — it was testing fundamentals in SQL, ETL, and OOP rather than algorithm puzzles — but the finance side was a bigger hurdle than I expected.
Prep tip from this candidate
If you're interviewing for a Business Analyst role at State Street, don't skip finance domain knowledge. Study derivatives, FX basics, and trade lifecycle concepts before the written test round. The technical questions focus on SQL, ETL, and OOP principles like abstract classes and inheritance, so be prepared to discuss those with concrete examples from your resume.
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 State Street
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Cumulative Distribution | |
| Rolling Bank Transactions | |
| 500 Cards | |
| Find the Missing Number | |
| Employee Salaries | |
| Bagging vs Boosting | |
| Subscription Overlap | |
| Button AB Test | |
| Prime to N | |
| Comments Histogram | |
| Closest SAT Scores | |
| Size of Joins | |
| Top Three Salaries | |
| Total Spent on Products | |
| Monthly Customer Report | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Paired Products | |
| Top 3 Users | |
| Third Purchase | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Experiment Validity | |
| Minimum Change | |
| Over 100 Dollars | |
| Recurring Character | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial test, though its content varies. One describes quantitative reasoning, English and Excel, with results taking about ten to twelve days. Another reports a written test on derivatives, FX and the trade lifecycle. A third mentions an online test of basic technical knowledge.
Two candidates describe an HR round as conversational. One was asked to introduce themselves, walk through relevant experience, and discuss career goals and tool knowledge, and found it straightforward rather than deep. Another, in an HR final round, got behavioral questions about solving a problem creatively and where they saw themselves in five years, plus Excel experience.
Candidates describe a more technical round. One manager round dug into resume experience, SQL, ETL, Python and whether you can create an object of an abstract class. Another technical round covered inner versus outer joins, abstract classes and interfaces, and a major college project. A third candidate was asked about derivatives, corporate actions, the trade life cycle, portfolios and basic SQL functions.
One candidate describes a third round with another team member, sometimes based in the US office, covering similar behavioral and technical ground, with a decision about a week after the interviews finished. Another says the final round was with HR. Be ready to talk through project ownership, challenges you handled and how you approach business problems.
