Candidates describe a Wells Fargo Software Engineer process built around an online assessment, one or two technical interviews, a manager or behavioral conversation and an HR call, often drawing on resume projects.
$119K
Avg. Base Comp
$134K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Wells Fargo Software Engineer interview as a test of how well you can explain your own work and reason through practical systems, more than a test of hard algorithms.
Most processes open with an online assessment. One candidate took a HackerRank test, and another described fairly standard, mostly language-agnostic coding questions. Campus candidates describe longer, broader tests that added English, aptitude or finance sections. Two of them also faced a harder graph or dynamic-programming problem, such as a Dijkstra variation or a two-dimensional knapsack question.
The interviews that follow often lean on your resume. Candidates were asked to discuss personal projects, and one said most of the technical round came directly from their resume. Design prompts differ from person to person. Reported examples include:
Interviewers seemed more interested in clear tradeoffs and communication than in perfect answers.
Technical scope depends on the interviewer. Reported topics include:
One candidate expected a behavioral hiring-manager talk and got a technical one, so prepare for both.
Behavioral questions are a real part of the loop. Reported themes include making decisions without full information, handling situational work scenarios and general team fit. Timing is uneven. One candidate waited about four months between the assessment and the next step. Another describes repeated delays and no response after the final HR round.
Synthesized from 62 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 Wells Fargo 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 Wells Fargo
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Justify a Neural Network | |
| Hurdles In Data Projects | |
| Client Solution Pushback | |
| Safe Deployments | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Simple Explanations | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Size of Joins | |
| Total Spent on Products | |
| Maximum Profit | |
| Get Top N Frequent Words | |
| Top 3 Users | |
| Google Maps Improvement | |
| String Shift | |
| Prime to N | |
| Scrambled Tickets | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates describe an online assessment first, ranging from a HackerRank test to standard, mostly language-agnostic coding questions. Campus candidates describe longer tests that added English, aptitude or finance sections, and two mention a harder graph or dynamic-programming problem.
Technical conversations often start from resume projects. Candidates also report OOP, DBMS, Java fundamentals and concurrency questions, easy-to-medium DSA problems, and design prompts such as a flower-shop backend or a Java API. Some candidates had two technical rounds, and the scope varied by interviewer.
Candidates describe a behavioral, managerial or hiring-manager conversation covering decisions under uncertainty, situational work scenarios and team fit. In one report it was split with a technical half in a single sitting. One candidate found the hiring-manager round entirely technical despite being told it would be behavioral.
Several candidates report a short HR conversation covering background, Wells Fargo's work domain, relocation or salary details. Follow-up varies: one candidate got a positive signal at the end of the HR round, while another describes unclear communication and no response for weeks.
