U.S. Bank software engineer interviews reported here range from a straightforward junior screening and technical discussion to a senior-level conversation with unexpected CICS emphasis.
$115K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
1-3 weeks
Process Length
For U.S. Bank software engineer applicants, the available reports point to two notably different interview experiences rather than one uniform format. One junior candidate described a standard screening followed by a technical discussion that emphasized explaining reasoning, core fundamentals, and clear communication. That candidate found the pace steady and the technical depth manageable, with no emphasis on obscure puzzles or an extended algorithm grind.
A senior candidate, however, reported that the interview concentrated heavily on CICS and legacy mainframe material, despite that topic not appearing in the job description. Prepare to explain your technical reasoning clearly, while also checking whether the particular team works with legacy systems. For a senior or enterprise-facing opening, review the role description closely and be ready to connect your background to the technologies named by the interviewer; if CICS is relevant to the team, describe any direct exposure accurately rather than trying to overstate it.
The reports also differ in tone: the junior conversation was described as clear and non-adversarial, while the senior candidate experienced a more one-sided exchange. Thin evidence means the precise format and technical focus may vary by level and team.
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 | |
| Maximum Profit | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Size of Joins | |
| Rectangle Overlap | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
One junior candidate reported a standard screening before the technical discussion. No timing, format, or specific screening questions were provided, so candidates should expect the initial conversation to vary by team and opening.
A junior candidate described a technical conversation focused on solid basics and explaining their reasoning clearly. The report characterized the discussion as straightforward rather than trick-heavy, but it did not identify a coding exercise or named technical questions.
One senior candidate reported extensive questioning about CICS and legacy mainframe topics, even though CICS was not listed in the job description. This is a single report, so it may reflect that role or team rather than every U.S. Bank software engineering interview.
