Senior Software Developer applicants have rated the interview process at Wells Fargo with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 62.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Developer roles take an average of 10 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Wells Fargo overall takes an average of 30 days.
Common stages of the interview process at Wells Fargo as a Senior Software Developer according to 2 Glassdoor interviews include:
One on one interview: 33%
Phone interview: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
There were 2 rounds of interview, They have asked basic of Java, Javascript and Json. If you are Full stack developer you have been asked with some questions in microservice, Kafka and Redis
Interview questions [1]
Question 1
They just asked about race condition, dead lock in java and IIFE, Basic question on Json, Basic question in microservice
I applied online. The process took 2 weeks. I interviewed at Wells Fargo in Apr 2026
Interview
The interview had 4 rounds
1. Online Assessment
2. Online Interview
3. Managerial Interview
4. Inperson interview as per their policy
5. Online HR round (compensation discussion)
Their compensation team did not consider RSU though it is part of CTC and HR tried to lowball. They were not ready to negotiate the compensation at all and were giving 50% hike on the base.
Even though I was earning more than what they offered me.
I declined as I did not like the behaviour of HR.
I would suggest them ask the expectations earlier and if they dont have the budget dont proceed with interview and waste candidates time.
I applied through a recruiter. I interviewed at Wells Fargo (Bengaluru) in Mar 2026
Interview
Round 1: Hackerrank with two mid-level algorithms
Round 2: Interviewer asks mostly about multi-threading, how to use collections, and how collisions work in the case of a custom class key. How equals and hashCode work