How many interview rounds does State Street have for a Cloud Engineer role?

State Street’s Cloud Engineer process includes multiple stages: Technical Screening, Live Problem-Solving, a Take-Home Component, and a Multi-Day Practical Assessment. The timeline in the guide moves from screening into progressively more intensive, hands-on evaluation, including work that you do independently.

What makes the State Street Cloud Engineer interview difficult?

For reported interviews for this role, the most common difficulty is average. The process is still described as rigorous, with live problem-solving and significant practical components that test how you work under real constraints.

What topics are tested in the State Street Cloud Engineer interview?

Preparation should focus on AWS and core cloud engineering skills, plus debugging and practical coding assignments. The listed top topics also include CSV parsing, distributed systems, command-line tool development, and operating systems fundamentals, with sample questions that cover managing cross-account permissions and consistency in distributed systems.

How does the interview loop work for a State Street Cloud Engineer, including the take-home and multi-day parts?

After an initial Technical Screening, candidates go into Live Problem-Solving, then complete a significant Take-Home Component to demonstrate independent work. The loop ends with a Multi-Day Practical Assessment focused on applying knowledge and skills in practical settings across multiple days.

What pay should Cloud Engineer candidates expect at State Street?

Candidate-reported compensation for this Cloud Engineer role shows base pay from $41.6k to an unspecified top base, with total pay up to $65k. Pay varies by level and location, so you should confirm the specific offer range during recruiting.

State StreetCloud Engineer

Updated Mar 3, 2023

State Street Cloud Engineer Interview Experiences 2026

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

Get your personalized State Street Cloud 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

> 1 year

Average Neutral Canada

I remember the process as a fairly intense stretch, with a couple real-time interviews and then a take-home that drained a lot of time. I had back-to-back interviews, both around 45 minutes. The first interview focused on small OS or distributed-systems style questions, and the second shifted toward my experience with technologies like AWS plus some brain-teaser style questions. It was a noticeable change of pace—more conceptual and systems-oriented upfront, then more about how I’d worked with cloud tools.

After that, I had a two-day open-ended coding assignment. I had to build my own command-line tool and also write a CSV parser to read, convert, and output price data. Honestly, that take-home was the hardest part—not because every question was impossible, but because it was tedious and required careful handling of the workflow and output. Overall, the journey felt demanding, but the structure was consistent: interview for systems + experience, then a hands-on project where you prove you can implement the pipeline end to end.

Share your interview experience

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