State Street · Primly Community

State Street software engineer interview process, full loop: what I went through in 2026

qa_quinn · 6 replies

Went through the full State Street software engineer interview process earlier this year for a backend role on their Charles River Development side. Posting a breakdown because I couldn't find anything recent.

Total timeline was about 5 weeks from application to offer.

Stage 1: recruiter phone screen Standard 30 minutes, mostly resume walkthrough and a few "tell me about a time" behavioral questions. Nothing technical. The recruiter was internal, pretty professional, asked about visa status and timeline upfront.

Stage 2: online assessment (HackerRank) Two coding problems, 90 minutes. One medium-level array/hash map problem, one that involved string parsing with some edge cases. Both felt like standard prep material, nothing exotic. I think the pass rate here is pretty high, they use it as a filter not a gut check.

Stage 3: technical phone screen One hour with a senior engineer. First 20 minutes was a live coding problem (similar difficulty to the OA). Then they pivoted to a design question: "how would you build a notification system for trade confirmations?" Not full system design, more of a discussion. Last 15 minutes was behavioral, specifically about working with ambiguous requirements.

Stage 4: virtual onsite This was four back-to-back 45-minute sessions: System design (deeper, more like a real senior design round) Coding (one medium, one closer to hard, both data structures) Behavioral/competency with an engineering manager Cross-functional chat with someone from the product side of Charles River

Overall: the difficulty is honest. Not Google-hard but not easy either. The behavioral rounds carry real weight here. State Street is a financial institution with a compliance culture, so they probe specifically for ownership, escalation behavior, and how you handle disagreements. Worth prepping those as seriously as the coding.

Happy to answer specifics. Role was backend Java/Spring, Boston hybrid.

6 replies

frontend_fran

This is exactly what I needed. I have a recruiter screen next week for a similar role. The fact that the technical phone screen goes into a light system design makes me want to brush up more on that. Did they give you any heads-up before the onsite about what to focus on?

remote_swe_42

The recruiter sent a prep email that said basically "expect coding, system design, and behavioral" which is not exactly insider info. No real specifics. I just asked the recruiter directly what the system design scope would be and she said senior-level candidates should be comfortable designing distributed systems at a conceptual level, not production-ready depth. That was more useful.

ops_omar

The behavioral rounds at State Street are genuinely evaluated, not just checkbox items. Custody and fund admin work has a lot of regulatory exposure and they've gotten burned before by engineers who escalated too slowly or didn't document decisions. If you have stories about catching a prod issue before it blew up, or pushing back on something for compliance reasons, use them.

quietquit_quincy

Did the onsite feel like actual evaluation or more like a formality after the phone screen? Sometimes once you pass the tech screen the onsite is basically cultural fit theater.

remote_swe_42

Not a formality. I knew someone who got all the way to the onsite and didn't pass the system design round. They extend the onsite because they genuinely calibrate level there, especially for senior vs. staff. They're not just checking boxes.

alex_design

The Charles River Development side vs. core State Street custody/reporting can have pretty different cultures and tech stacks. CRD feels more like a fintech product company, core State Street feels more like a bank. Worth clarifying which group you'd be in before you sign anything.