U.S. Bank Software Engineer interview typically runs 2 rounds: screening and technical discussion. It usually takes about 1-2 weeks and can include unexpected legacy mainframe focus.
$99K
Avg. Base Comp
$200K
Avg. Total Comp
3
Typical Rounds
1-3 weeks
Process Length
We’ve seen a split pattern in U.S. Bank interviews: one candidate described a calm, straightforward conversation centered on fundamentals and clear reasoning, while another was caught off guard by a deep dive into CICS that never appeared in the job posting. That contrast tells us the company may present a polished, baseline software-engineering experience on the surface, but the actual evaluation can still pull from legacy banking systems in ways that aren’t obvious from the role description.
A recurring theme is that U.S. Bank seems to care less about flashy problem-solving and more about whether candidates can stay composed, explain their thinking cleanly, and handle a conversation that may shift into older enterprise technology. The offer-winning candidate emphasized that the interview felt readable and normal, with an emphasis on basics and communication. The no-offer candidate, by contrast, felt the process was one-sided and elimination-oriented once the discussion moved into CICS. Our read is that success here depends on showing solid engineering judgment while also being prepared for unexpected mainframe or banking-infrastructure questions that can surface even in a modern software engineer process.
Synthesized from 2 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the U.S. Bank process.
The interview itself was a genuinely good one. The hiring manager was knowledgeable, engaged, and the conversation flowed naturally. The focus was heavily on Kafka — consumer groups, offset management, exactly-once semantics, dead letter topics, KEDA autoscaling — and on my past experience in fintech, particularly my work on the GetActions corporate actions pipeline at Bloomberg and the CBDC platform at R3. It felt less like an interrogation and more like a conversation between engineers who care about the same problems.
Questions asked: The bulk of it was Kafka. That was the clear focus. He went deep — not surface level stuff. He asked about how consumer groups work, how partitions get assigned, what happens during a rebalance, and how you guarantee exactly-once processing end to end. He wanted to know the difference between committing offsets manually versus automatically and why you would choose one over the other. Dead letter topics came up — specifically what conditions trigger them, how you decide what gets retried versus what goes straight to DLT, and what information you attach to the DLT message so engineers can actually investigate it later.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at U.S. Bank
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Total Spent on Products | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
The process appears to begin with a standard screening conversation focused on background, fit, and baseline qualifications for the software engineer role. Candidates described this stage as calm and straightforward, with the interviewer setting a steady pace and checking whether the applicant matched an early-career or junior profile.
The main technical stage is a conversational interview rather than a high-pressure coding marathon. Interviewers ask broad fundamentals questions, expect candidates to explain their thinking clearly, and may also probe legacy mainframe topics such as CICS even when those skills are not obvious from the job description.
Across the interview, there is a noticeable emphasis on whether the candidate can stay grounded in the basics and communicate reasoning in a simple, structured way. The experience suggests they are evaluating how well you explain your approach and whether you would fit a junior software engineering team.