A Software Engineer at State Street plays a critical role in maintaining, modernizing, and securing the digital core of one of the world's largest asset management and financial services companies. Software engineers here are tasked with building high-throughput, low-latency transaction engines, developing robust cloud-native data pipelines, and creating intuitive user interfaces for institutional clients. The impact of this position is immense, as the code you write directly influences the movement and custody of trillions of dollars in global assets. Engineers work on a wide array of problem spaces, ranging from migration of legacy systems to modern AWS infrastructure, to building real-time event-driven architectures using Kafka, to designing client-facing web portals. Working at State Street offers a unique blend of enterprise-scale challenges and modern technical implementation. Whether you are joining an application support team, a core platform development unit, or a specialized security team, your work will ensure the operational resilience and technological advancement of global financial systems. ##### Tip While State Street utilizes modern technologies like Spring Boot and React, some teams maintain legacy infrastructure. Be sure to ask your interviewer about the specific stack of the team you are interviewing for to align expectations early.
Online Assessment
reportedCandidates complete an online aptitude and technical assessment testing logical reasoning, quantitative skills, and basic coding.
What to demonstrate
- Candidates complete an online aptitude and technical assessment testing logical reasoning, quantitative skills, and basic coding
- Depth in Java
How to prepare
- Answer aloud and timed: Explain the difference between Python and Java memory management.
- Answer aloud and timed: How do you implement the
equalsandhashCodecontract in a Java POJO?
Technical Screening Call
reportedExperienced candidates begin with a technical screening call or a vendor-led evaluation.
What to demonstrate
- Experienced candidates begin with a technical screening call or a vendor-led evaluation
- Depth in Java
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Panel Interviews
reportedOne or more panel interviews with State Street engineering managers to evaluate technical skills.
What to demonstrate
- One or more panel interviews with State Street engineering managers to evaluate technical skills
- Depth in Java
How to prepare
- Answer aloud and timed: How do you design and secure a RESTful API?
- Answer aloud and timed: Explain the difference between functional and class-based components in React.
PracHub editorial advice for the preparation topics above.
Prepare for Java trivia
Even if you are a generalist or Python developer, review core Java concepts like memory management, collections, and garbage collection, as interviewers frequently default to Java-based questions.
Clarify the team's tech stack
State Street has a vast portfolio of applications. Ask early on if the team works on legacy platforms (such as old ETL tools like Kettle) or modern cloud-native architectures so you can tailor your answers.
The recruitment process at State Street can occasionally experience administrative delays
Do not hesitate to follow up with your HR coordinator if you do not hear back within 10 to 15 business days.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain the difference between Python and Java memory management.
Explain the difference between Python and Java memory management.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Solve the Two Sum problem using an optimized map-based approach.
Solve the Two Sum problem using an optimized map-based approach.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Write a program to validate matching parentheses in a string using a stack.
Write a program to validate matching parentheses in a string using a stack.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Implement a binary search algorithm to find an element in a sorted array.
Implement a binary search algorithm to find an element in a sorted array.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How do you detect a cycle in a linked list?
How do you detect a cycle in a linked list?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Solve a scenario-based problem involving tree or graph traversal (for senior or specialized roles).
Solve a scenario-based problem involving tree or graph traversal (for senior or specialized roles).
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
What is the difference between a process and a thread in an operating system?
What is the difference between a process and a thread in an operating system?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Write a SQL query involving multiple joins and aggregations to retrieve transaction history.
Write a SQL query involving multiple joins and aggregations to retrieve transaction history.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
How do you implement the `equals` and `hashCode` contract in a Java POJO?
How do you implement the equals and hashCode contract in a Java POJO?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Explain the core components of Spring Boot and how dependency injection works.
Explain the core components of Spring Boot and how dependency injection works.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is Kafka, and how does it handle high-throughput event streaming?
What is Kafka, and how does it handle high-throughput event streaming?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you design and secure a RESTful API?
How do you design and secure a RESTful API?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Explain the difference between functional and class-based components in React.
Explain the difference between functional and class-based components in React.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How does the React Context API differ from Redux for state management?
How does the React Context API differ from Redux for state management?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What are React hooks, and how do you use `useEffect` and `useMemo`?
What are React hooks, and how do you use useEffect and useMemo?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Write a script to fetch data from a public API and render it dynamically in a list format.
Write a script to fetch data from a public API and render it dynamically in a list format.
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What is the difference between semantic and non-semantic HTML?
What is the difference between semantic and non-semantic HTML?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Explain the ACID properties of a database and how they relate to financial transactions.
Explain the ACID properties of a database and how they relate to financial transactions.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Every query on one table stalls for forty seconds mid-deploy
During a release on PostgreSQL, every query touching resource times out for about 40 seconds and then recovers with no intervention. The release ran one migration, ALTER TABLE resource ADD COLUMN archived_reason TEXT, and the migration log shows it completing in 6 ms. Unrelated tables showed no change in error rate. Explain how a 6 ms statement caused a 40-second stall, give the ordered checks you would run on a live system to confirm it, and give the migration procedure that prevents a repeat.
Approach
- Separate the statement's duration from the lock's duration. ADD COLUMN with no default is a catalogue-only change and genuinely runs in milliseconds, but it requires ACCESS EXCLUSIVE, and it cannot acquire that until every transaction already touching the table has finished.
- Account for the queueing, which is the part that surprises people. A lock request that is waiting blocks later requests for conflicting modes behind it rather than letting them overtake, so one long-open transaction holds the DDL and the DDL holds all the traffic. The stall length is set by the longest open transaction, not by the size of the change.
- Confirm on a live system in this order: pg_stat_activity for that table ordered by xact_start, looking for the oldest transaction and specifically for state = idle in transaction; then pg_locks where granted = false to find the waiter; then join them on pid to name blocker and blocked. pg_blocking_pids() does that join for you and is the fastest single call.
- Prevent rather than merely time it better. Set lock_timeout to a second or two on the migration session so the DDL abandons the queue after a bounded wait and is retried, instead of holding it for as long as the oldest transaction lives. Be exact about what that buys: queries arriving during the wait still queue behind the pending ACCESS EXCLUSIVE request, so each attempt costs them up to one lock_timeout of added latency. The outage goes from 40 seconds to about one second per attempt, not to zero. Also run migrations away from deploy-time peaks, and put a statement timeout and an idle-in-transaction timeout on the analytics role that opens the long transactions.
Follow-up
- The same release also wants NOT NULL on that column. What is the sequence that gets there without a long lock?
- Your lock_timeout retry fails ten times in a row because the analytics transaction is always open. What do you change?
Built from the rounds and topics State Street candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the State Street loop
- Write out the reported sequence: Online Assessment, Technical Screening Call, Panel Interviews.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.
02Work Java
- Spend the session on Java, which State Street candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work Spring Boot
- Spend the session on Spring Boot, which State Street candidates report being tested on.
- Write one worked example in Spring Boot and time yourself on it.
Deliverable: One timed worked example in Spring Boot.
04Work Data Structures & Algorithms (DSA)
- Spend the session on Data Structures & Algorithms (DSA), which State Street candidates report being tested on.
- Write one worked example in Data Structures & Algorithms (DSA) and time yourself on it.
Deliverable: One timed worked example in Data Structures & Algorithms (DSA).
05Answer out loud: Java & Backend Engineering
- Answer aloud, timed: Explain the difference between Python and Java memory management.
- Answer aloud, timed: How do you implement the `equals` and `hashCode` contract in a Java POJO?
Deliverable: Spoken answers to 2 reported Java & Backend Engineering question(s), under time.
06Answer out loud: Frontend & Web Development
- Answer aloud, timed: Explain the difference between functional and class-based components in React.
- Answer aloud, timed: How does the React Context API differ from Redux for state management?
Deliverable: Spoken answers to 2 reported Frontend & Web Development question(s), under time.
07Answer out loud: Data Structures & Algorithms
- Answer aloud, timed: Solve the Two Sum problem using an optimized map-based approach.
- Answer aloud, timed: Write a program to validate matching parentheses in a string using a stack.
Deliverable: Spoken answers to 2 reported Data Structures & Algorithms question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
How do you handle database connection pooling in a high-concurrency environment?
How do you handle database connection pooling in a high-concurrency environment?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about yourself and your background.
Tell me about yourself and your background.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What are your short-term and long-term professional goals?
What are your short-term and long-term professional goals?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time when you experienced stress or conflict in a team. How did you resolve it?
Describe a time when you experienced stress or conflict in a team. How did you resolve it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work at a financial institution like State Street?
Why do you want to work at a financial institution like State Street?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Walk me through a challenging project on your resume. What was your individual contribution?
Walk me through a challenging project on your resume. What was your individual contribution?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
How do you handle database connection pooling in a high-concurrency environment?
- 02
Tell me about yourself and your background.
- 03
What are your short-term and long-term professional goals?
- 04
Describe a time when you experienced stress or conflict in a team. How did you resolve it?
How difficult is the Software Engineer interview at State Street?
Most candidates describe the difficulty as average to easy, provided you have brushed up on core programming concepts, basic data structures, and SQL. The questions tend to focus on foundational knowledge rather than highly complex algorithmic puzzles.
State Street Software Engineer candidate reports ↗What is the typical timeline for the hiring process?
The timeline can vary significantly. While some candidates receive offers within a few days of a single round, others report a process stretching over several weeks or even months due to administrative scheduling across global teams.
State Street Software Engineer candidate reports ↗Is prior financial services experience required?
No, prior financial experience is not mandatory for most engineering roles. However, showing an interest in fintech, banking systems, or financial data structures will help you stand out during behavioral and managerial rounds.
State Street Software Engineer candidate reports ↗Are there take-home assignments?
Yes, some teams utilize take-home projects, such as building a full-stack application (frontend to backend) or creating a command-line tool, which you will then present and explain in subsequent rounds.
State Street Software Engineer candidate reports ↗What topics does State Street test in interviews?
State Street interviews most often cover Java, SQL, Python, Statistics, and Problem Solving. The exact emphasis depends on the specific role you apply for.
State Street Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01State Street Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
ValueMomentum Software Engineer Interview Guide
What ValueMomentum asks Software Engineer candidates, from reported rounds and questions.
Tech Tammina Software Engineer Interview Guide
What Tech Tammina asks Software Engineer candidates, from reported rounds and questions.
TEKsystems Software Engineer Interview Guide
What TEKsystems asks Software Engineer candidates, from reported rounds and questions.
Raytheon Technologies Corporate Headquarters Software Engineer Interview Guide
What Raytheon Technologies Corporate Headquarters asks Software Engineer candidates, from reported rounds and questions.