U.S. Bank Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 64 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at U.S. Bank.
U.S. Bank
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical
The interview process at U.S. Bank is pretty structured and everyone works together. You start with a recruiter call, then usually talk to some team members about technical stuff or behavior, and then there's a final chat with the hiring managers to talk about your skills, how you solve problems, and if you'd fit in.
Confirmed questions1 question
- Tell me about yourself.
U.S. Bank
Senior Software Engineer
Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical
I got invited for a recruiter call and scheduled it using their calendar. The meeting was canceled the next day, and I was told they'd reschedule. I had to reach out the following day to follow up and got a new invite. When the interview finally happened, the interviewer was rushed, didn't introduce themselves or discuss the role/company. They mentioned other candidates were ahead of me and that they wouldn't be meeting the hiring manager for several days but would pass my info along if they needed more people. Unfortunately, a scheduling error put me out of the running.
Confirmed questions1 question
- Can you introduce yourself and walk me through your career journey?
U.S. Bank
Software Engineer
Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Other
Got an email to set up an initial interview, and I was like, sure, for tomorrow. The interviewer ghosted me, so I hit them up to see if they were still around. Later that day, they explained the scheduling system messed up and sent too many invites. They asked if I could do it the next day, and I told them my availability. Then, overnight, I got the standard rejection email: "After carefully reviewing your application we've decided to go with other applicants." Didn't hear from the recruiter at all during the expected timeframe. It was a pretty unprofessional way to handle it, but luckily this was just a backup option anyway.
Confirmed questions1 question
- Would you be available to reschedule for tomorrow?
U.S. Bank Software Engineer Interview Questions
Quoted word for word from U.S. Bank interview reports.
“Can you reverse a string while ignoring a specific special character?”
Read reports →“Is it possible to use a finally block without a catch statement?”
Read reports →“What is the distinction between an inner join and an outer join?”
Read reports →“Can you explain what a Dictionary is and how it differs from a hashmap?”
Read reports →“Could you write the logic to find the median value from an ArrayList?”
Read report →“Can you build a list that supports various sorting methods?”
Read report →“If you could be any animal, which one would you choose?”
Read report →“What would be your approach to designing a system that estimates the number of people inside a US Bank at any given moment?”
Read report →“What action would you take if you suspected a team developer was hindering team objectives?”
Read report →Formats, difficulty and experience
Across all 64 U.S. Bank interview reports.