Candidates describe USAA's Software Engineer interviews as starting with a timed online coding assessment of easy-to-medium array and string problems. A conversational technical and behavioral interview follows. Many reports are from internship or early-career candidates.
$105K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
2-4 weeks
Process Length
Most candidates describe the USAA Software Engineer interview as beginning with an online coding assessment of easy-to-medium problems, usually three. Reported topics center on string and array work, such as finding a median, mean, or mode, returning elements that sum to a target value, and a sliding window problem. Time limits vary by report, from about 30 minutes to a window of a day or two. One candidate found the assessment platform finicky, so check your setup well before you start.
After the assessment, candidates report a conversational interview, by phone, Zoom, or on-site, that mixes technical and behavioral questions. Several describe being asked to explain their approach out loud or in pseudocode rather than writing polished code. One candidate was asked about the four pillars of object-oriented programming and about the languages on their résumé. Another was asked to write a function to sort an array. An internship candidate met on-site with a Software Engineer and the Director of IT and solved two more easy problems while justifying their choices.
Behavioral questions come up in nearly every report. They include presenting to a group, handling conflict or a difficult teammate, strengths and weaknesses, and adjusting to a new environment. One candidate said mission and values fit carried real weight, so prepare a specific answer about why USAA rather than a generic one.
Many of these reports come from interns and early-career applicants, so expectations may differ for experienced hires. One experienced candidate was screened out in a recruiter call over a missing degree, so confirm the education requirements before you apply.
Synthesized from 8 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 Usaa process.
The process started with an online coding assessment—three questions covering easy to medium difficulty, focusing on string and array manipulation. I had 24 hours to complete it, and I'd recommend checking your setup well in advance, since the platform itself could be finicky. Once I got past that, the OA itself was straightforward, comparable to three easy coding problems.
After passing the OA, I moved into a Zoom interview with behavioral and technical components. The behavioral side included questions like describing a time I presented information to a group and how I handled any issues that arose. For the technical portion, they asked me to explain my approach in pseudocode rather than write fully executable code—a much lower bar than the OA and a good sign the interview was conversational. They also asked deeper technical questions, like the four pillars of object-oriented programming, and wanted evidence that I truly understood the languages on my résumé.
The process felt fairly standard overall—nothing exotic—but the OA platform's reliability seemed like a real pain point, so I'd go in with patience and a backup way to contact support if things go sideways.
Prep tip from this candidate
Master string and array manipulation problems at the easy-to-medium LeetCode level before the OA. For the behavioral round, have a clear story ready about presenting to a group and handling setbacks. Be prepared to discuss the four pillars of OOP and be able to speak authoritatively about the languages you list—they will probe depth, not breadth.
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 Usaa
How would you answer when an Interviewer asks why you applied to their company?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Bagging vs Boosting | |
| Random SQL Sample | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Type-ahead Search | |
| Cyclic Detection | |
| Three Zebras | |
| Precision and Recall | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| Modifying a Billion Rows | |
| Type I and II Errors | |
| Same Characters | |
| Swap Variables | |
| Integer String Addition | |
| The Longest Journey | |
| Employee Benefits Outreach | |
| Triangle as Binary Array | |
| Blob Indexing | |
| Drink Production Allocation | |
| International e-Commerce Warehouse | |
| Shortest Path Algorithms |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment of about three LeetCode-style questions, mostly string and array problems such as finding a median, mean, or mode or returning elements that sum to a target. Reported time limits range from about 30 minutes to a window of a day or two. One candidate found the platform unreliable, so check your setup in advance.
Some candidates report a phone or recruiter screen. One internship candidate said theirs combined coding and conflict-handling questions. One Software Engineer candidate said the call centered on educational background and ended after they mentioned not having a degree. It does not appear in every report.
Candidates describe conversational interviews over Zoom or on-site. Reports include explaining an approach in pseudocode or out loud and sorting or median-style problems. One candidate was asked about object-oriented programming basics. Behavioral questions covered presenting to a group, conflict, and mission fit. Interviewers were described as two managers in one report, and as a Software Engineer and the Director of IT in another.
An internship candidate who received an offer mentioned a drug screening near the end of hiring. Reported timelines run from about two weeks to close to a month.
