cswork / libraryOpen practice workspace

Interview guides · Flagstar Bank

Flagstar Bank Software Engineer Interview Guide

Flagstar Bank Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Flagstar Bank, you will play a critical role in designing, developing, and maintaining the financial technology infrastructure that powers one of the nation's largest mortgage originators and full-service banks. This position is not just about writing code; it is about building secure, scalable, and highly reliable systems that handle millions of transactions, manage sensitive customer data, and streamline complex financial workflows. The work you do directly impacts retail banking customers, mortgage borrowers, and internal operations teams. From optimizing high-throughput loan origination systems to crafting seamless digital banking interfaces, Software Engineers at Flagstar Bank solve complex technical challenges at the intersection of traditional finance and modern technology.

This guide is scoped to a Software Engineer candidate at Flagstar Bank.

Focus areas

  • Time Complexity Analysis
  • Array Operations
  • Runtime Reasoning for Insert Operations

The Flagstar Bank interview process

Flagstar Bank candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Phone Screen

Initial discussion about your background, career goals, and alignment with the role.

What to demonstrate

  • Initial discussion about your background, career goals, and alignment with the role
  • Depth in Time Complexity Analysis

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.

Technical Phone Interview

A technical interview focusing on core software engineering principles and practical questions.

What to demonstrate

  • A technical interview focusing on core software engineering principles and practical questions
  • Depth in Time Complexity Analysis

How to prepare

  • Answer aloud and timed: Explain the concept of polymorphism and provide a real-world coding scenario where you would implement it.
  • Answer aloud and timed: What is the difference between an abstract class and an interface, and when would you choose one over the other?

Panel Interview

In-depth in-person or virtual panel interview assessing system design and past project architecture.

What to demonstrate

  • In-depth in-person or virtual panel interview assessing system design and past project architecture
  • Depth in Time Complexity Analysis

How to prepare

  • Answer aloud and timed: How do you handle memory management and prevent memory leaks in your preferred programming language?
  • Answer aloud and timed: Describe a time when you had to work with a difficult stakeholder or team member. How did you resolve the conflict to deliver the project?

Where candidates lose points

Master the fundamentals

Do not spend all your time memorizing complex algorithmic tricks. Instead, ensure you can clearly explain OOP concepts, database normalization, and basic data structure performance.

Be proactive with follow-ups

Due to the structured nature of corporate banking HR departments, communication can sometimes be slow. Do not hesitate to send polite, professional follow-up emails to your recruiter if you do not hear back within the expected timeframe.

Be prepared for potential communication delays during the post-interview feedback phase

Proactive, polite follow-up is highly recommended to keep your candidacy moving forward.

Questions & practice

Explain the runtime complexity (Big O notation) of inserting a new value into an array at the very beginning (

Medium · Technical & Core Programming Fundamental

Explain the runtime complexity (Big O notation) of inserting a new value into an array at the very beginning (array[0]). What happens to the existing elements?

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. 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 handle memory management and prevent memory leaks in your preferred programming language?

Medium · Technical & Core Programming Fundamental

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

Canonicalise a request body into a stable idempotency fingerprint

Medium · parsing · canonicalisation · hashing

idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.

Approach

  1. Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
  2. Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
  3. Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
  4. Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.

Follow-up

  • A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
  • Where does the fingerprint get computed relative to request decompression and the body-size limit?

Replace offset paging on the resource feed with keyset

Easy · keyset pagination · composite index · sort order

resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.

Approach

  1. Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
  2. Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
  3. Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
  4. Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.

Follow-up

  • The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
  • Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?

Explain why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.

Approach

  1. Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
  2. For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
  3. Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
  4. Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.

Follow-up

  • 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
  • A dashboard runs this for 40 owners in one page load. What changes about the design?

Why is it important to create classes in object-oriented programming? What benefits do they bring to software

Medium · Technical & Core Programming Fundamental

Why is it important to create classes in object-oriented programming? What benefits do they bring to software design?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 concept of polymorphism and provide a real-world coding scenario where you would implement it.

Medium · Technical & Core Programming Fundamental

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. 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 the difference between an abstract class and an interface, and when would you choose one over the othe

Medium · Technical & Core Programming Fundamental

What is the difference between an abstract class and an interface, and when would you choose one over the other?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Walk me through a complex technical problem you solved in a past role. How did you identify the root cause and

Medium · Behavioral & Team Collaboration

Walk me through a complex technical problem you solved in a past role. How did you identify the root cause and implement the solution?

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Flagstar Bank candidates report.

Day 1 — Map the Flagstar Bank loop

  • Write out the reported sequence: Recruiter Phone Screen, Technical Phone Interview, Panel Interview.
  • 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.

Day 2 — Work Time Complexity Analysis

  • Spend the session on Time Complexity Analysis, which Flagstar Bank candidates report being tested on.
  • Write one worked example in Time Complexity Analysis and time yourself on it.

Deliverable: One timed worked example in Time Complexity Analysis.

Day 3 — Work Array Operations

  • Spend the session on Array Operations, which Flagstar Bank candidates report being tested on.
  • Write one worked example in Array Operations and time yourself on it.

Deliverable: One timed worked example in Array Operations.

Day 4 — Work Runtime Reasoning for Insert Operations

  • Spend the session on Runtime Reasoning for Insert Operations, which Flagstar Bank candidates report being tested on.
  • Write one worked example in Runtime Reasoning for Insert Operations and time yourself on it.

Deliverable: One timed worked example in Runtime Reasoning for Insert Operations.

Day 5 — Answer out loud: Technical & Core Programming Fundamentals

  • Answer aloud, timed: Explain the runtime complexity (Big O notation) of inserting a new value into an array at the very beginning (array[0]). What happens to the existing elements?
  • Answer aloud, timed: Why is it important to create classes in object-oriented programming? What benefits do they bring to software design?

Deliverable: Spoken answers to 2 reported Technical & Core Programming Fundamentals question(s), under time.

Day 6 — Answer out loud: Behavioral & Team Collaboration

  • Answer aloud, timed: Describe a time when you had to work with a difficult stakeholder or team member. How did you resolve the conflict to deliver the project?
  • Answer aloud, timed: Walk me through a complex technical problem you solved in a past role. How did you identify the root cause and implement the solution?

Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration question(s), under time.

Day 7 — Dry run for Flagstar Bank

  • Run one full mock under time, then write down the two questions you most want to ask your interviewers.

Deliverable: A completed timed mock and two questions to ask.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time when you had to work with a difficult stakeholder or team member. How did you resolve the conf

Medium · Behavioral & Team Collaboration

Describe a time when you had to work with a difficult stakeholder or team member. How did you resolve the conflict to deliver the project?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?

How do you handle situations where project requirements change mid-way through a development cycle?

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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 a time you had to learn a new technology quickly to meet a project deadline.

Medium · Behavioral & Team Collaboration

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. 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?