Wells Fargo interview experiences from intern superdays and India drives

Wells Fargo’s interview process for software engineer interns in 2025 ran through a HackerRank test (basic multiple choice plus two coding problems), a recruiter call and a one-hour video superday. The first 30 minutes were behavioral: tell me about yourself, why Wells Fargo and STAR questions about projects. The second 30 were technical: string manipulation, OOP and, for one candidate, a case on building a full-stack app for a business. All four 2025 intern reports on Taro ended in an offer.

Wells Fargo’s 2025 Technology Analyst Development Program posting listed $48.08 an hour (about $100,000 a year) in Charlotte, Minneapolis and Phoenix. Interns get a location preference email after the assessment, and Wells Fargo says interns may be considered for a full-time analyst role the following year in the same market.

Wells Fargo interview process by round

Wells Fargo software engineer intern interview experiences in the US (2025)

All four reports are from 2025 software engineer intern candidates on Taro, and all four got an offer (one declined it).

• Charlotte intern, November 2025, offer. Applied cold in August. A HackerRank assessment with basic multiple-choice questions and two coding problems came about a week later, then a location preference email and, a month after that, a recruiter call. The one-hour video interview was 30 minutes of behavioral project questions and 30 minutes of technical questions on string manipulation, plus a case on building a full-stack application for a business. The offer call came 1-2 days later.
• Charlotte intern, July 2025, offer. Called the HackerRank test and the single interview very easy: two behavioral questions and two technical ones on system design and OOP. Their advice was to talk with the interviewer during behavioral questions instead of sounding rehearsed.
• US intern, October 2025, offer. After the online assessment, heard nothing for about two months, then got a phone call to schedule a one-hour superday with behavioral and technical parts and many STAR-style questions.
• US intern, October 2025, accepted offer. HackerRank assessment, then a superday of two recruiter interviews: a behavioral one (tell me about yourself, why are you interested) and a technical assessment.

Wells Fargo superday questions reported in 2025

Behavioral half

1. Tell me about yourself
2. Why are you interested in Wells Fargo?
3. STAR questions about a project on your resume (what you built, your part, the result)

Technical half

1. A string manipulation problem, coded live
2. OOP concepts in your main language
3. Short definitions such as CI/CD and what a hash map is
4. How you would build a full-stack application for a business (case question, Charlotte 2025)
5. System design and OOP questions, kept at intern level (Charlotte, July 2025)

The July 2025 Charlotte intern’s advice was to talk with the interviewer during the behavioral questions instead of sounding rehearsed.

Wells Fargo interview questions with sample answers

Q. When would you choose SQL over NoSQL for a banking system?
A. Choose a relational database when you need ACID transactions across multiple rows and tables, a fixed schema the business depends on, and rich ad-hoc joins - which describes a core banking ledger, where a debit and a matching credit must commit or fail together and auditors need referential integrity. Choose NoSQL when the access pattern is a known key lookup at very high volume, the shape of the data varies, and horizontal write scaling matters more than joins - session stores, clickstream telemetry, or a fraud-scoring feature cache. Document stores also fit semi-structured payloads that would otherwise need dozens of nullable columns. In practice a bank runs both: the relational system of record for money movement, and NoSQL stores for high-volume derived and read-optimized data.

Q. What are ACID properties and why do they matter in a transaction?
A. Atomicity means a transaction is all-or-nothing, so a transfer never debits one account without crediting the other. Consistency means the database moves from one valid state to another, honouring constraints such as a non-negative balance check. Isolation means concurrent transactions do not see each other’s partial work, preventing dirty reads, non-repeatable reads, and phantom reads depending on the isolation level. Durability means once the commit is acknowledged, the change survives a crash, which engines guarantee by writing to a write-ahead log before the data pages. Higher isolation levels cost concurrency, which is why most systems run READ COMMITTED and escalate to SERIALIZABLE only where correctness demands it.

Q. How do you print a pyramid pattern, and how do you reason about it in an interview?
A. Treat it as two nested loops: the outer loop runs over rows 1 to n, and each row prints n - i spaces followed by 2*i - 1 stars. Deriving those two formulas out loud - spaces decrease linearly, stars increase by two per row - is what the interviewer is actually grading, not the syntax. Complexity is O(n^2) since you emit roughly n^2 characters. For an inverted pyramid you simply run the outer loop from n down to 1, and for a diamond you print the pyramid then the inverted one skipping the repeated middle row. Build the formula from the first two or three rows on paper before writing any code.

Q. How do you reverse the words in a sentence in place?
A. The standard trick is reverse-twice: first reverse the entire character array, which puts the words in the right order but with each word’s characters backwards, then walk the array and reverse each individual word between its space boundaries. That is O(n) time and O(1) extra space, and it beats the split-and-rejoin approach which needs O(n) auxiliary space for the token list. The edge cases to state up front are leading, trailing, and repeated spaces - clarify whether they should be collapsed or preserved. Wells Fargo interviewers commonly follow up by asking you to handle multiple spaces correctly, so decide the rule before coding.

Q. What is the difference between a primary key, a unique key, and a foreign key?
A. A primary key uniquely identifies each row, cannot be NULL, and there is exactly one per table; it usually carries the clustered index. A unique key also enforces uniqueness but permits NULLs (how many depends on the engine) and a table can have several - an email column is the classic example. A foreign key is a column that references another table’s primary or unique key, enforcing referential integrity so you cannot insert a transaction for a customer ID that does not exist. Foreign keys also govern delete behavior through ON DELETE CASCADE, SET NULL, or RESTRICT, and in banking schemas RESTRICT is usually the safe default because silently cascading away financial records is unacceptable.

Superday tips from Wells Fargo interns

Wells Fargo intern interview FAQ

Wells Fargo India: campus drives, SHL test and interview experiences

India Analyst and Program Associate hiring is decided mostly at the SHL online test, where one 2025 drive went from 150 candidates to 15 before the technical, managerial and HR rounds.

Wells Fargo interview process by round (India campus)

Typical India loop (candidate-reported): Online Assessment (verbal + business interpretation + coding + logic) → Technical → Managerial → HR. Duration often 2-3 weeks from application to offer.

What candidates report from India

Student write-ups of Wells Fargo India campus and off-campus hiring for Analyst / Program Associate roles (2022-2025) describe a short process - one online assessment and two interviews - but the assessment is unusually structured, and it is where most people are cut.

Eligibility and funnel. A 2025 on-campus account reports a 7.5 CGPA cutoff for CS/ENTC and gives concrete funnel numbers for that drive: 150 candidates → 15 after the OA → 8 after the technical round → 4 after the managerial round, with all 4 receiving offers. The pattern most people describe is the same shape: the OA is brutal, the interviews are humane.

Online assessment (SHL / AMCAT, proctored). Reported as four distinct sections, each separately timed, with no backward navigation between questions:

• Verbal - roughly 12 questions in 15 minutes: comprehension, vocabulary, sentence/paragraph completion. Moderate.
• Business interpretation - roughly 15 questions in 25 minutes. This is the section people flag as different: business data in graphs and charts, including candlestick and pie charts, needing both reading and calculation.
• Coding - 2 questions, ~40 minutes. Easy-to-medium array and string manipulation; some accounts report a greedy problem as the second one.
• A single logic / “fitness” question - ~10 minutes. Described as a maths or puzzle problem that does not need a specific data structure, delivered in a coding-question wrapper.

Technical interview (~30 minutes). Resume-led rather than DSA-marathon. Reported asks span simple programming (factorial, swapping two numbers), maths word problems, SQL queries, and - where the resume mentions them - web-stack questions like React and Node, how a React app runs, and state vs props. If it is on your resume, expect to be taken into it.

Managerial round (~45-50 minutes). A deep resume and project pass: why you chose that technology, what edge cases you handled, SQL vs NoSQL, then behavioral ground - motivation for banking technology and career goals.

What the accounts suggest actually matters

• Practice data interpretation from charts specifically. It is the section least covered by generic DSA prep and it is a gate.
• No going back in the OA, so do not park questions “for later”.
• Know your own resume stack cold - this is the most consistent theme across Wells Fargo reports.
• Have a clear SQL story. It surfaces in both interview rounds.

Wells Fargo India campus interview experiences

Campus interview experience 1 - On-campus September 2025 (internship)

Source: GeeksforGeeks, Wells Fargo On-Campus September 2025

• SHL aptitude test (16 August 2025): verbal ability, business/data interpretation, coding, and a Wells Fargo fitness section on logic and algorithms (one candidate had to implement Floyd-Warshall in 10 minutes). About 160 appeared and 21 were shortlisted.
• Technical 1 (virtual, about 1 hour, 18 September): an AI/ML project (model choice, preprocessing, metrics); Kth largest element in an array with a heap, then a QuickSelect-style approach for less space; routing algorithms, TCP vs UDP, process vs thread, zombie and orphan processes, deadlocks and OOP. 16 of 21 cleared.
• Technical 2 (virtual, about 1 hour, same day): deeper DSA, suggested improvements to the project, open problem statements, core CS and academics, with many cross-questions. 11 of 16 moved on.
• HR (15-20 min, same day): family background, strengths and weaknesses, why CSE and why this college, why hire you, why Wells Fargo, other interviews in progress, and Wells Fargo’s operations and competitors.
• Outcome: All 11 who reached HR got internship offers.

Takeaways

• What decided it: Clearing the SHL test into a small shortlist (21 of about 160), then holding up across two same-day technicals on DSA, core CS and one project.
• How to practice: Two back-to-back 60-minute project and DSA mocks; read up on Wells Fargo’s business and competitors for HR.

Experienced hire interview experience 2 - SDE I (Java + DSA + SQL)

Source: DevBrainiac, Wells Fargo SDE I

A first-person account from a working engineer who applied through a job portal for a remote SDE I role; the process took 1-2 weeks.

• Recruiter screen (20-25 min): current role and stack, reason for switching, notice period.
• Java and resume (about 30 min technical plus 10-15 min on the role): OOP pillars with real use cases, checked vs unchecked exceptions, List/Set/Map, ArrayList vs LinkedList, HashMap hashing and collisions, and resume questions.
• Advanced Java, DSA and SQL: multithreading, exception handling in production, collection behavior; maximum subarray from brute force to Kadane; SEND + MORE = MONEY as a backtracking approach without full code; SQL for minimum salary per department with a subquery and a GROUP BY alternative.
• Outcome: Selected. The author credits clear communication and structure over perfect code.

Takeaways

• What decided it: Explaining Java concepts through real use cases, then talking through approach on Kadane, the puzzle and the SQL query.
• How to practice: Narrate OOP and exception handling from production examples; Kadane aloud; one GROUP BY salary query.

India HR questions that come up often

1. Why banking technology?
2. Comfort with background verification timelines
3. Location preference (Bengaluru or Hyderabad)
4. Strengths and weaknesses

India tips: the SHL test has no backward navigation, so answer or skip each question for good; the business interpretation section uses candlestick and pie charts, so time yourself reading them; the 45-50 minute managerial round questions anything on your resume (React, Node, SQL).

Sources

• US reports: Taro intern reports from Charlotte, November 2025, Charlotte, July 2025, October 14, 2025 and October 27, 2025, and the 2025 Technology Analyst Development Program posting.
• Wells Fargo behavioral-based interview guidance (official)
• Wells Fargo Interview Experience (On-Campus) - September 2025 - GeeksforGeeks (student write-up)
• Wells Fargo SDE I Interview Experience - DevBrainiac (candidate blog)
• Wells Fargo Interview Experience 2025 (On-Campus, Full-Time) - GeeksforGeeks (student write-up)
• Wells Fargo Interview Experience (On-Campus, August 2024) - GeeksforGeeks (student write-up)
• Wells Fargo Interview Experience for Analyst - GeeksforGeeks (student write-up)
• Wells Fargo Interview Experience for Program Associate 2022 - GeeksforGeeks (student write-up)

Cutoffs, section timings, and funnel sizes differ by campus and year. The Wells Fargo hub covers the full process, pay and teller interviews.

Similar companies

Bank of America · JP Morgan · Goldman Sachs · Capital One · HSBC · Barclays