Bank of America Video Interview: Explain Your Code

The code is finished, but the evaluation is not

The Bank of America 2027 Coding & Video Interview asks you to explain the reasoning behind work you have already completed. A line-by-line replay wastes the response. The interviewer needs a compact account of the problem, the decisions that shaped your solution, and the evidence that your approach works.

The real question

Keep both instructions in view. The alternatives are part of the question:

Describe how you solved the second coding challenge. Walk us through your logic and describe alternatives that you considered but did not use.

How candidates lose points

• Reading the code aloud. Syntax does not explain the reasoning that selected it.
• Skipping the problem definition. The listener cannot judge a solution without knowing the required input, output, and constraints.
• Claiming the first idea was obvious. That removes the comparison the prompt explicitly requests.
• Naming alternatives without trade-offs. A list of techniques is not a decision.
• Ignoring proof. No tests, edge cases, or complexity discussion leaves correctness unsupported.

Build a decision-led walkthrough

Start with one sentence that defines the task. State the key constraint that controlled your design. Then explain the solution in logical stages, not source-code order. Finish by comparing one or two credible alternatives and showing why your chosen approach was the better fit.

A hypothetical example could involve finding the intersection of two sorted integer lists. The candidate might describe using two pointers because the sorted input supports a single pass. They could reject repeated membership searches because that repeats work, and reject an extra set because it uses additional memory without exploiting the ordering.

1. Define the input, required output, and decisive constraint.
2. Name the data structure or invariant that organizes the solution.
3. Walk through one representative case and one edge case.
4. Compare alternatives using time, memory, clarity, or failure risk.
5. Close with the tests that increased confidence in correctness.

A strong explanation makes the design feel inevitable only after the trade-offs are visible.

Prepare beyond one coding prompt

This is one verified question from the Bank of America assessment. OpenInterview has the complete questions for Bank of America so you can prepare for the wider Coding & Video Interview rather than one isolated explanation.