IT applicants have rated the interview process at USAA with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 82% positive. To compare, the company-average is 65.9% positive. This is according to Glassdoor user ratings.
Candidates applying for IT roles take an average of 22 days to get hired, when considering 49 user submitted interviews for this role. To compare, the hiring process at USAA overall takes an average of 29 days.
Common stages of the interview process at USAA as a IT according to 49 Glassdoor interviews include:
One on one interview: 24%
Group panel interview: 18%
Skills test: 12%
Drug test: 10%
Phone interview: 9%
Background check: 8%
Presentation: 7%
Personality test: 6%
IQ intelligence test: 6%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 2 days. I interviewed at USAA
Interview
Mostly behavioral questions just getting to know who you are and if you fit in with their workplace. A few critical thinking questions that are not based on your answers but on your approach to the problem and your thought process to solve them. Overall good experience and nice people.
Interview questions [1]
Question 1
How can we get the younger generation to get more involved with their financial future sooner in life?
I applied through other source. The process took 2 months. I interviewed at USAA (San Antonio, TX) in Nov 2021
Interview
Starts with a phone call for general background questions regarding your experience. They share information about the internship. Following this I had a short coding challenge on hackerrank consisting of 3 easy leetcode questions with a 30 minute time limit. Finally I had a zoom interview with two senior engineering personnel where they shared their experience both in and out of USAA. The interview then lead to a few behavioral questions and 3 basic technical programming questions. One question was describing a time I failed in a job setting and the steps I took to fix this error, another was how I would go about working with a difficult team member, use the STAR method and you are set. Programming questions consisted of basic easy leetcodes such as checking if an array of bracket chars is balanced and another was counting the amount of some char in an array, these questions are given in word form without actual code so you should clarify with your interviewer the actual data structures you will be assuming for input and output, your answer can be in pseudocode. They asked about personnel projects and extracurricular activities and my roles in them and at the end gave me a chance to ask about any questions or concerns I had with the internship.
Interview questions [1]
Question 1
Write a psuedocode program to check if an string of brackets chars is balanced.
I applied online. The process took 4 weeks. I interviewed at USAA
Interview
The process starts with a phone screen with a recruiter. At first thought I got ghosted because recruiter called towards the end of the scheduled window.
If I remember correctly, there was a coding assessment. Nothing crazy if there was because I completely forgot whether there was or not.
Finally, as expected, is the final interview. Mine was not the best. It was half behavioral and half technical. They asked super easy coding questions, where you just need to talk about how you would solve it (NO CODING). My interviewers had difficulty with Zoom so they couldn't figure out how to display question prompts at first and then they hung up prematurely.
One half of my interviewers made this a less than ideal interview. From the beginning of the interview to the end, they were shaking their head at nearly everything I said (including me simply stating my name and about me.) Honestly felt disrespectful and not a company I'm going to give attention to again.
Interview questions [1]
Question 1
Why did you make a web application over a mobile one?
The first part was mostly behavioral questions to see how you would fit in the company. The second part was describing how you would code a function. You just need to. describe it.