RepostedWells Fargo logo

Wells Fargo · Phone screen → Onsite

In process

Wells Fargo SWE Intern OA and Interview Questions: 18 Experiences

Software engineer · InternshipBachelor's degreeOct 2026
Shared by

Wells Fargo technology and SWE intern reports, 2024–2026: a 60-minute HackerRank with 7 MCQs and 2 coding tasks, then one hour of behavioral and technical.

At a glance

  • Process: apply, a HackerRank OA within days, a "self-paced" step that is often only a location-preference form, then one live hour split into two 30-minute halves, behavioral and technical, sometimes with different interviewers (02, 10, 14, 15). Offers came one to a few days after the live round (02, 03).
  • Asked recently: OA MCQs on SQL, APIs, syntax, code tracing and networking (05, 09, 11); two coding tasks such as server replacements after three errors and deleting AB or BB (11). Live: small design prompts (grocery ordering, a flower-shop SaaS), CI/CD, OOP and résumé projects (03, 14, 15, 16).
  • Difficulty: OA coding was easy to medium (05, 18); live technical depth varied from one easy problem to almost no coding (03, 04, 17). A clean OA did not guarantee an interview (08).
  • Practise first: Count Server Replacements and Minimum Remaining Length.

Coverage: Wells Fargo Technology Summer Internship (Early Careers), Technology Analyst (Software Engineering), SWE Intern and Software Engineer Intern in the U.S. Charlotte, New York and Plano where stated. Eighteen reports from July 2024 to June 2026. India campus hiring and quant internships are separate processes and are not included.

What came up

The OA is the most predictable step: a short HackerRank of MCQs plus two coding tasks. The live round is a conversation whose technical half changes with the interviewer.

Topic Reports Last seen
OA MCQs (SQL, APIs, syntax, code tracing, networking) 8 of 18 Jun 2026 (report date)
OA coding (easy to medium) 7 of 18 Jun 2026 (report date)
Résumé and project walkthrough 3 of 18 Oct 2025 (report date)
Small system or product design 6 of 18 Oct 2025 (report date)
Behavioral and values questions 9 of 18 Oct 2025 (report date)
CI/CD and software delivery 2 of 18 Jun 2025 (report date)
Live coding (easy, sometimes explain only) 4 of 18 Oct 2025 (report date)

A candidate can appear in more than one row.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Count server replacements after three consecutive errors 1 Jul 2025 (report date)
Minimum length after deleting AB or BB 1 Jul 2025 (report date)
String manipulation (live) 2 Nov 2025 (report date)
How do you sort a heap? 1 Aug 2025 (report date)

OA knowledge and code-reading items

Question Reports Last seen
Weighted string hash sum((i + 1) * letterValue): which pairs collide? 1 Jun 2026 (report date)
Find the wrong boundary update in a recursive binary search 1 Jun 2026 (report date)
SQL: IN syntax, removing duplicates, counting a CASE label over five rows 1 Jul 2025 (report date)
REST: a 404 vs a gateway timeout; HTTP methods for a job-application API 1 Jul 2025 (report date)
Trace a Newton-style integer update from n = 841, x = 1 1 Jul 2025 (report date)
Trace a recursive exponentiation-by-squaring function 1 Jul 2025 (report date)

System Design (small, conversational)

Question Reports Last seen
Build a full-stack application for a business 1 Nov 2025 (report date)
Support online ordering for a grocery store 1 Oct 2025 (report date)
Explain how a data pipeline works end to end 1 Oct 2025 (report date)
System design plus OOP 1 Jul 2025 (report date)
Describe a SaaS product for a flower shop 1 Jun 2025 (report date)
Basic system design, CI/CD and front-end tools 1 Nov 2024 (report date)

Behavioral (BQ)

Question Reports Last seen
Explain CI/CD and how you think about it 1 Jun 2025 (report date)
How do your choices align with the company's goals and values? 1 Jun 2025 (report date)
Why Wells Fargo? Strengths; learning when the next step is unclear (practice) 1 Nov 2024 (report date)

18 detailed candidate timelines, loops, and screens

01: Two OA posts from one Summer Intern candidate

Report date: Jun 2026 · Role: Summer Intern · Result: Passed OA

  1. One post: an OA in February with about eight or nine medium items, including a weighted string-hash collision question.
  2. The other, eleven days later: a 90-minute HackerRank with a recursive binary-search bug to find. Counted once, as one application.

02: Cold application to a Charlotte offer

Report date: Nov 17, 2025 · Role: Software Engineer Intern · Location: Charlotte · Result: Offer

  1. Applied in August; HackerRank a week later (basic MCQs and two coding implementations); location preferences.
  2. A recruiter about a month later, then a one-hour video interview: 30 minutes behavioral, 30 minutes technical with a second interviewer, covering projects, string manipulation, course basics and a case on building a full-stack application for a business.
  3. The offer call came a day or two later.

03: Grocery ordering, one easy problem, then an offer

Report date: Oct 20, 2025 · Role: SWE Intern · Result: Offer

  1. Applied in August, then HireVue, then a mid-October Superday: 30 minutes technical, 30 minutes behavioral.
  2. Technical: how to support online ordering for a grocery store, one easy LeetCode-style question and résumé follow-ups. The offer came a few days later.

04: Same Superday, almost no coding

Report date: Oct 20, 2025 · Role: SWE Intern · Result: Not shared

  1. Same week, same split: a behavioral half, then a "technical" half asking for a high-level explanation of software development or how a data pipeline works.
  2. The interviewer went back to behavioral questions and talked about what interns do.

05: The 7 + 2 HackerRank

Report date: Oct 14, 2025 · Role: SWE Intern · Location: United States · Result: No offer reported

  1. The OA came a day after applying: 60 minutes, seven MCQs on APIs, SQL and syntax, and two LeetCode-style coding questions.

06: A short Charlotte interview built on the résumé

Report date: Sep 1, 2025 · Role: SWE Intern · Location: Charlotte · Result: Offer

  1. A phone call, then a 30-minute Zoom interview light on technical questions: an introduction and a detailed walk through projects and technologies on the résumé.

07: DSA, OS, stacks, SQL and a heap

Report date: Aug 7, 2025 · Role: SWE Intern · Location: United States · Result: No offer

  1. A broader HackerRank: one DSA coding question, an operating-systems question, stacks and queues, SQL, and how to sort a heap.

08: Perfect visible tests, then a rejection

Report date: Aug 6, 2025 · Role: SWE Intern · Result: Rejected

  1. Applied the day applications opened, took the OA the day it arrived and passed every visible test, got the location form that day, and was still rejected before any interview. No reason was given.

09: A networking MCQ and a coding task on the second try

Report date: Jul 27, 2025 · Role: Technology Analyst Intern (Software Engineering)

  1. Most MCQs were fine except one networking question outside their coursework.
  2. The first coding task stopped them at first; they came back and got it passing.

10: Application to location form in two days

Report date: Jul 23, 2025 · Role: Technology Analyst Intern (Software Engineering), Summer 2026 · Result: In process

  1. Applied July 21 with no referral; HackerRank July 23, about an hour of MCQs and coding that meant implementing functions rather than hard algorithms.
  2. The self-paced step the same day only asked for two preferred locations.

11: Nine questions in 60 minutes

Report date: Jul 23, 2025 · Role: Technology Summer Internship – Early Careers

  1. Seven knowledge or code-reading items: a Newton-style integer trace from n = 841, x = 1; a recursive exponentiation-by-squaring trace (the exponent was cut off in their screenshot); SQL IN syntax; SQL duplicate removal; a SQL CASE count over five rows; a 404 vs a gateway timeout; and HTTP methods for a job-application API.
  2. Two coding problems: replace a server after three consecutive errors and count replacements, and delete AB or BB repeatedly to minimize length (BABBA reduces to length 1).

12: System design and OOP in one live round

Report date: Jul 15, 2025 · Role: Software Engineer Intern · Location: Charlotte · Result: Offer

  1. A very easy HackerRank, then one round with two behavioral and two technical questions, on system design and OOP.

13: OA, location form, recorded HireVue, then Superday

Report date: Jul 1, 2025 · Role: SWE Intern · Location: Plano · Result: No offer

  1. The fullest pipeline reported: OA, location form, a recorded behavioral HireVue on personality and values, then a Superday.

14: CI/CD and leadership in a 30 + 30 interview

Report date: Jun 9, 2025 · Role: Software Engineer Intern · Location: Charlotte · Result: Offer

  1. Thirty minutes technical, thirty behavioral, with breakout rooms of other interns and employees.
  2. The technical question: explain CI/CD and how you think about it. Leadership and teamwork mattered in the behavioral half.

15: A SaaS product for a flower shop

Report date: Jun 3, 2025 · Role: Software Engineer Intern · Location: United States · Result: Offer

  1. A manageable HackerRank, then one live hour: behavioral questions on aligning with the company's goals and values, and a technical prompt to describe a SaaS product for a flower shop.

16: Strings, CI/CD, front-end tools and simple design

Report date: Nov 18, 2024 · Role: Software Engineer Intern · Location: New York · Result: Offer

  1. HackerRank after application review; final-round news about two weeks later.
  2. Technical: a string problem, basic system design, CI/CD and front-end tools. Behavioral: why Wells Fargo (practice), strengths, and learning when the next step was unclear.

17: Explain an easy problem, don't code it

Report date: Oct 2024 · Role: Technology / SWE Intern · Result: Offer

  1. Behavioral questions answered with STAR stories.
  2. One easy LeetCode-style problem that they only had to explain, plus theory questions.

18: Two easy coding questions in about 30 minutes

Report date: Jul 2024 · Role: Technology / SWE Intern

  1. Applied July 17, then a HackerRank with MCQs and two easy coding questions, finished in about 30 minutes.

Patterns across the reports

  1. The "self-paced interview" is often a location form. It was only location preferences in 08 and 10; 13 did get a recorded behavioral HireVue.
  2. One hour, split in two. 02, 03, 04, 14 and 15 described two halves of about 30 minutes, behavioral and technical.
  3. Small design prompts, not big systems. Grocery ordering (03), a flower-shop SaaS (15), a full-stack business app (02) and basic design (12, 16).

Common questions

What is on the Wells Fargo intern HackerRank?

Usually seven MCQs (SQL, APIs, syntax, code tracing) and two easy-to-medium coding tasks in 60 minutes (05, 11); one candidate had a 90-minute version (01).

What is the Wells Fargo self-paced interview?

Often just a form for two preferred locations (08, 10); one candidate got a recorded behavioral HireVue (13).

Does the Wells Fargo intern interview have coding?

Sometimes one easy problem (03, 17) or a string task (02, 16); some technical halves had almost none (04, 06).

How fast does Wells Fargo send intern offers?

A day or two (02) to a few days (03) after the final interview.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.