U.S. Bank software engineer interviews, per six candidate reports, often start with a recruiter or HR screen, then move to hiring-manager and light technical talks. Expect behavioral focus, SQL, and project discussion.
$104K
Avg. Base Comp
$132K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidate reports on U.S. Bank software engineering interviews point to a process that leans on conversation more than heavy coding. The reports cover different levels, from intern to lead, so treat them as separate experiences, not one fixed format.
The most detailed software engineer report, which ended in an offer, describes a Teams recruiter screen about background and salary expectations, then an on-site with a hiring manager and the team. The technical portion included a SQL coding challenge and questions about prior projects, including an automation framework and a testing problem the candidate had solved. A lead-level candidate likewise described project discussion and a few easy LeetCode-style problems, while a junior candidate who received an offer described a fundamentals-focused, conversational process.
The early screen can matter. One candidate says an HR call probed years of experience with specific technologies from the job description and ended their process before any technical round. Another, interviewing for a senior role, reports being pressed on CICS and legacy mainframe topics that the posting did not mention. An intern candidate reports only behavioral interviews.
To prepare, know your project history with concrete years and examples, rehearse a few collaboration and problem-solving stories, and refresh SQL and basic algorithms. Two candidates also describe scheduling and communication problems, so confirm next steps in writing and follow up.
Synthesized from 6 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.
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 | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening call with a recruiter or HR contact covering background, interest in U.S. Bank, and salary expectations. One candidate was pressed on years of experience with technologies from the job description, so come with concrete examples. That candidate's process ended at this stage.
Candidates describe a conversation with a hiring manager about prior experience, day-to-day work, and fit. One offer recipient says the manager explained what the role needed. A lead-level candidate reports the manager call was cut short by a scheduling mix-up, so confirm the time and invitees.
Reports of the technical portion are light and vary by level. One software engineer describes a SQL coding challenge plus questions on an automation framework and a testing problem. A lead-level candidate mentions project discussion and a few easy LeetCode-style problems. A junior candidate describes a fundamentals check.
Behavioral questions appear throughout the reports. An intern candidate reports two interviews that were entirely behavioral, covering motivation and collaboration. Other candidates say communication style and team fit were weighed alongside technical skill. Prepare clear stories with structured, direct answers.
Outcomes in the reports are mixed: two offers and four rejections or no-offers across different levels. One lead-level candidate describes weeks of silence followed by last-minute scheduling, and an intern says they got no feedback after following up. Ask about next steps and keep recruiter contacts in writing.
