How many rounds does State Street use for Full Stack Engineer interviews, and what is the typical flow?

State Street’s Full Stack Engineer process includes an initial screening, one or more technical rounds, panel interviews, and a final assessment. The technical rounds can include live coding or problem-solving exercises across front end, back end, and database domains. Panels may include both local and international team members during the technical evaluations.

How hard is it to get hired for a Full Stack Engineer role at State Street?

Across reported interviews for this role, the most common reported difficulty is average. With only a small number of reported interviews, you should still expect a multi-stage process with technical evaluation that spans the full stack.

What topics does State Street test for Full Stack Engineer interviews?

Interview expectations for a State Street Full Stack Engineer center on full-stack development, database engineering, and data modeling. Common focus areas include designing relational databases, implementing query logic, and explaining how you optimize database queries for high-volume retrieval. You may also be tested on frontend state management and how backend framework trade-offs affect high-concurrency systems.

What coding or system design tasks should I prioritize for State Street Full Stack Engineer interviews?

You should be ready to design a database schema, including for a social media-style comment and threading system. The process also emphasizes building cohesive features by connecting backend APIs to frontend components, plus implementing logic for fetching and displaying nested threads or comment structures. Questions can also cover optimizing queries and handling state management on the front end for performance.

What compensation range do candidates report for State Street Full Stack Engineer roles?

Candidate and job-posting reports show base pay starting around $233.5k and total compensation reaching up to about $871.2k. Reported pay varies by level and location, so exact numbers can differ depending on the specific role tier.

What types of past experience questions does State Street ask a Full Stack Engineer?

You may be asked to walk through a complex project you led and the technical hurdles you overcame. There are also prompts about pivoting under changing requirements and how you applied prior research or academic work to real-world engineering problems. Preparation should emphasize explaining your decisions clearly, not just producing working code.

State StreetFull Stack Engineer

Updated Nov 20, 2025

State Street Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at State Street, newest first and distilled into what to expect across the loop.

Get your personalized State Street Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

11 months ago

Average Negative India

I had a two-round setup with a panel split across geographies—one interviewer group labeled as an India panel, followed by a second panel that was supposed to be “US,” though most of the people in that later round weren’t actually based in the US. The format itself was straightforward, but what really changed the whole experience was how the conversations felt.

The second round got rescheduled at the last minute, and when I joined, the interviewer’s tone felt dismissive and unprofessional. Instead of constructive feedback, I was told something along the lines of needing to “learn the language first,” which landed as undermining considering my experience from established product environments. I kept waiting for a more normal evaluation—clarifying questions, technical discussion, anything that would feel fair—but the tone made it hard to stay confident in the process.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.