cswork / libraryOpen practice workspace

Interview guides · Frost Bank

Frost Bank Software Engineer Interview Guide

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

The 60-second brief

At Frost Bank, technology is the backbone of the award-winning customer service and financial integrity that the institution has delivered for over a century. As a Software Engineer, you will not just write code; you will design, optimize, and maintain the critical infrastructure that powers retail banking, commercial lending, and database systems. Your work directly impacts millions of transactions daily, ensuring that financial services remain secure, reliable, and highly available for customers across Texas and beyond. The engineering team at Frost Bank operates in a highly collaborative environment where stability, security, and scalability are prioritized.

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

Focus areas

  • Object-Oriented Programming (OOP)
  • Java
  • OOP principles (encapsulation, inheritance, polymorphism)

The Frost Bank interview process

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

HR Screening

Initial screening conducted by HR to assess candidate qualifications and fit.

What to demonstrate

  • Initial screening conducted by HR to assess candidate qualifications and fit
  • Depth in Object-Oriented Programming (OOP)

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 Panel Interview

Rigorous technical interview conducted via video conference focusing on practical scenarios.

What to demonstrate

  • Rigorous technical interview conducted via video conference focusing on practical scenarios
  • Depth in Object-Oriented Programming (OOP)

How to prepare

  • Answer aloud and timed: How does memory management and garbage collection work in Java?
  • Answer aloud and timed: Explain the concept of method overloading versus method overriding.

Cultural Alignment

Final stage focusing on leadership, team dynamics, and overall fit within the company.

What to demonstrate

  • Final stage focusing on leadership, team dynamics, and overall fit within the company
  • Depth in Object-Oriented Programming (OOP)

How to prepare

  • Answer aloud and timed: How do you ensure thread safety when working with shared resources in a multi-threaded Java application?
  • Answer aloud and timed: What are the differences between SQL and NoSQL databases, and how do you decide which to use for a financial transaction ledger?

Where candidates lose points

Master the OOP basics

Do not spend all your time practicing highly advanced algorithmic puzzles. Instead, ensure you can flawlessly explain and implement core Java and OOP design patterns, as these are heavily tested.

Align with the bank's values

Take time to research Frost Bank's history, community involvement, and corporate culture. Incorporating these values into your behavioral answers shows genuine interest and enthusiasm.

Be ready for interactive technical discussions

During the technical panel round, treat the interviewers as future colleagues. Talk through your thoughts out loud, ask clarifying questions, and be open to feedback if they suggest an alternative approach.

Prepare detailed project stories

Have 2 or 3 solid examples of past projects ready. Be prepared to discuss the architecture, the technical challenges you faced, how you overcame them, and what you would do differently in hindsight.

Questions & practice

How does memory management and garbage collection work in Java?

Medium · Object-Oriented Programming & Java

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?

How do you ensure thread safety when working with shared resources in a multi-threaded Java application?

Medium · Object-Oriented Programming & Java

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?

Collapse a redelivered event batch into per-aggregate high-water marks

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

  1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
  2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
  3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
  4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

  • The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
  • How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

What are the differences between SQL and NoSQL databases, and how do you decide which to use for a financial t

Medium · Database & Systems Engineering

What are the differences between SQL and NoSQL databases, and how do you decide which to use for a financial transaction ledger?

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

Explain the concept of database normalization and describe a scenario where you would intentionally denormaliz

Medium · Database & Systems Engineering

Explain the concept of database normalization and describe a scenario where you would intentionally denormalize a schema.

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

Describe how you would troubleshoot a slow-running SQL query in a production environment.

Medium · Database & Systems Engineering

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. 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?

Explain the four main principles of Object-Oriented Programming and provide a real-world example of how you ha

Medium · Object-Oriented Programming & Java

Explain the four main principles of Object-Oriented Programming and provide a real-world example of how you have applied them.

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 in Java, and when would you choose one over

Medium · Object-Oriented Programming & Java

What is the difference between an abstract class and an interface in Java, 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?

Explain the concept of method overloading versus method overriding.

Medium · Object-Oriented Programming & Java

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?

How do database indexes work, and what are the trade-offs of over-indexing a high-write table?

Medium · Database & Systems Engineering

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 are ACID properties, and why are they critical for banking application databases?

Medium · Database & Systems Engineering

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?

Edge instances grow 400 MB per hour until the nightly restart

Hard · memory leak · heap analysis · metric cardinality

Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.

Approach

  1. Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
  2. Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
  3. Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
  4. The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.

Follow-up

  • Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
  • How would you have detected this before an OOM, given the nightly restart masked the trend?

Suggested practice checklist

Built from the rounds and topics Frost Bank candidates report.

Day 1 — Map the Frost Bank loop

  • Write out the reported sequence: HR Screening, Technical Panel Interview, Cultural Alignment.
  • 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 Object-Oriented Programming (OOP)

  • Spend the session on Object-Oriented Programming (OOP), which Frost Bank candidates report being tested on.
  • Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.

Deliverable: One timed worked example in Object-Oriented Programming (OOP).

Day 3 — Work Java

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

Deliverable: One timed worked example in Java.

Day 4 — Work OOP principles (encapsulation, inheritance, polymorphism)

  • Spend the session on OOP principles (encapsulation, inheritance, polymorphism), which Frost Bank candidates report being tested on.
  • Write one worked example in OOP principles (encapsulation, inheritance, polymorphism) and time yourself on it.

Deliverable: One timed worked example in OOP principles (encapsulation, inheritance, polymorphism).

Day 5 — Answer out loud: Object-Oriented Programming & Java

  • Answer aloud, timed: Explain the four main principles of Object-Oriented Programming and provide a real-world example of how you have applied them.
  • Answer aloud, timed: What is the difference between an abstract class and an interface in Java, and when would you choose one over the other?

Deliverable: Spoken answers to 2 reported Object-Oriented Programming & Java question(s), under time.

Day 6 — Answer out loud: Database & Systems Engineering

  • Answer aloud, timed: What are the differences between SQL and NoSQL databases, and how do you decide which to use for a financial transaction ledger?
  • Answer aloud, timed: Explain the concept of database normalization and describe a scenario where you would intentionally denormalize a schema.

Deliverable: Spoken answers to 2 reported Database & Systems Engineering question(s), under time.

Day 7 — Answer out loud: Behavioral & Culture Fit

  • Answer aloud, timed: Why are you interested in working for Frost Bank specifically, and how do you align with our corporate values?
  • Answer aloud, timed: Describe a time when you had a technical disagreement with a teammate. How did you resolve it and move the project forward?

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

Behavioural preparation

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

Why are you interested in working for Frost Bank specifically, and how do you align with our corporate values?

Medium · Behavioral & Culture Fit

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?

Describe a time when you had a technical disagreement with a teammate. How did you resolve it and move the pro

Medium · Behavioral & Culture Fit

Describe a time when you had a technical disagreement with a teammate. How did you resolve it and move the project forward?

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 challenging software bug or system failure you encountered in a past role. How did you diagnos

Medium · Behavioral & Culture Fit

Tell me about a challenging software bug or system failure you encountered in a past role. How did you diagnose and fix it?

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 balance the need to deliver features quickly with the responsibility of maintaining high code quali

Medium · Behavioral & Culture Fit

How do you balance the need to deliver features quickly with the responsibility of maintaining high code quality and security standards?

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?

Describe a past project where you had to quickly learn a new programming language or technology. What was your

Medium · Behavioral & Culture Fit

Describe a past project where you had to quickly learn a new programming language or technology. What was your approach?

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?