2024–2026 Wells Fargo Technology / SWE Intern OA / Interviews: 18 Experiences

A practical roundup of firsthand Wells Fargo Technology and software engineering internship reports published from 2024 through June 2026.

Coverage: Technology Summer Internship – Early Careers, Technology Analyst (Software Engineering), SWE Intern, and Software Engineer Intern; OA, location-preference/HireVue steps, Superday, technical, and behavioral interviews. Explicit locations include Charlotte, New York, Plano, and the broader United States; several reports did not state a location. India campus hiring and Quant internships are separate processes and are not included here.

To a fren. Hope I am not too late..

The short version

The process has a recognizable spine, but the live interview is much less standardized than the OA.

1. HackerRank is the clearest recurring checkpoint. Several candidates received multiple-choice fundamentals plus two coding questions. Easy-to-medium LeetCode difficulty is the safest description, not a guaranteed ceiling.
2. The strongest recent OA pattern is 60 minutes, seven MCQs, and two coding questions. Two independent reports gave that exact structure, and a Reddit discussion described the same 7+2 split. Other candidates saw 90-minute or less clearly documented versions.
3. The “self-paced interview” may be nothing more than a location form. Several candidates opened HireVue expecting behavioral questions and found only first- and second-choice locations. Another candidate did receive a recorded behavioral step, so read your own invitation carefully.
4. A location form is not an interview invitation. One candidate completed every visible OA test, received the form immediately, and was still rejected. A clean OA matters, but it does not finish resume review or guarantee headcount.
5. The live round is often one hour split in half. Five reports explicitly described two roughly 30-minute blocks, usually behavioral and technical, sometimes with different interviewers.
6. “Technical” depends heavily on the interviewer. Candidates reported a small coding problem, OOP and CI/CD, a project deep dive, a practical design prompt, or almost no coding at all. The mildly annoying answer is that you need to prepare for all of those at a basic, explain-it-clearly level.
7. Projects and behavioral answers are not filler. Resume follow-ups, teamwork, leadership, learning, values, and “Why Wells Fargo?” showed up alongside technical work. A polished solution with a vague project story is not a complete preparation plan.
   A practical preparation formula: two timed coding problems + SQL/API/CS-fundamentals review + one small business-system design + a crisp project walkthrough + five honest STAR stories.

Online assessments (OA)

OA 01: The recurring 60-minute, nine-question version

Report period: July–October 2025 · Roles: Technology / SWE Intern · Platform: HackerRank

1. Two independent candidates reported exactly seven multiple-choice questions and two coding questions in 60 minutes.
2. A Reddit thread from the same recruiting season also described seven MCQs and two coding questions.
3. Reported MCQ areas included APIs, SQL, programming syntax, code tracing, and networking.
4. The two coding questions were described as easy to medium. Only one source preserved both prompts in full.
   This is the best-supported recent format in the evidence, but it is not a promise for every requisition or batch.

OA 02: The other versions did not line up perfectly

Report period: July 2024–June 2026 · Roles: SWE / Summer Intern

1. One candidate, across two posts from the same likely application cycle, described an 8–9 item assessment and a 90-minute HackerRank. The preserved items included a weighted-hash collision question and a recursive binary-search bug.
2. A July 2024 candidate saw MCQs plus two easy coding questions and finished in about 30 minutes.
3. Another 2025 candidate remembered a DSA coding question, an operating-systems question, stack and queue fundamentals, SQL, and a heap-sorting question.
4. One 2025 candidate described the OA only as general CS MCQs plus easy-to-medium HackerRank or LeetCode questions.
   Do not memorize one timer and call the OA solved. Practice the recurring material, then follow the invitation in front of you.

OA 03: Location preference is a separate checkpoint

One Summer 2026 applicant gave a clean timeline:

1. Applied online on July 21.
2. Completed HackerRank on July 23.
3. Received the self-paced step on July 23.
4. Opened it and found a location-preference form rather than a video interview.
   Other candidates reported the same surprise. A Plano candidate, however, described a longer path: OA, location form, recorded behavioral HireVue, then Superday. The safe takeaway is simple: “HireVue” is a delivery tool, not a reliable description of the questions inside.

OA 04: A strong score still leaves another screen

One candidate completed every visible test case, received the location form the same day, and was later rejected. Another commenter in that discussion reported the same result after missing the second coding problem.
The source does not reveal hidden-test scores or the hiring decision. What it does show is that OA completion and the location form are not equivalent to a live-interview invite.

Reported question bank

Coding tasks with useful detail

1. Faulty server replacements. Process logs in the form server_id success/error. After three consecutive errors for the same server, replace it, reset that server's consecutive-error history, and count total replacements. The matching FastPrep practice problem is Count Faulty Server Replacements.
2. Reduce an A/B string. Repeatedly delete either AB or BB, join the remaining pieces, and return the minimum possible final length. One reported example reduced BABBA to length 1. The matching practice problem is Minimum Length After AB and BB Deletions.
3. String manipulation. A New York candidate worked through a string problem in the live interview, but did not preserve the full prompt.
4. Heap reasoning. One OA report remembered being asked how to sort a heap, alongside DSA, OS, stack, queue, and SQL questions.
5. Easy-to-medium coding. Several candidates used this label without sharing the prompt. That supports the difficulty range, not a list of guaranteed topics.

SQL, APIs, and code reading

1. Choose the correct SQL IN syntax for filtering two priority values.
2. Choose the SQL command that removes duplicate rows from a result.
3. Trace a CASE expression over five student scores and count how many rows receive the middle label.
4. Distinguish a missing-resource 404 from a gateway timeout and identify which side of the request the status describes.
5. Match POST, collection GET, item GET, and item PUT calls to their job-application API behavior.
6. Trace 50 rounds of an integer Newton-style update starting from n = 841 and x = 1.
7. Read a recursive exponentiation-by-squaring function. The source image cut off the exponent, so the final return value cannot be reconstructed honestly.
8. Find the bad line in a recursive binary search where one branch updates the wrong boundary.
9. Apply a weighted string hash, sum((i + 1) * letterValue), and choose which listed string pairs collide.

Small design and software-delivery prompts

1. Explain how you would support online ordering for a grocery store.
2. Design a SaaS product for a flower shop.
3. Design a simple application at a high level.
4. Walk through a full-stack application for a business.
5. Explain how a data pipeline works from end to end.
6. Explain CI/CD, why it helps, and which tools you have used.
7. Discuss OOP fundamentals and the engineering choices in your own projects.
   These are small, conversational prompts. None of the admitted U.S. intern reports described a heavyweight distributed-systems interview.

Behavioral and resume questions

1. Tell me about yourself beyond the bullet points on your resume.
2. Why Wells Fargo, and how does the role fit what you want to learn?
3. Walk through a project, the part you owned, and the technical decision you would change now.
4. Tell me about teamwork, conflict, leadership, or a time you had to step up.
5. Describe a time you had to learn something new before you knew the next step.
6. Explain how your past choices line up with the company's goals or values.
   One candidate specifically warned against giving the stock “my teammates did nothing, so I did the whole class project” story without real reflection. The useful lesson is not to ban that example. It is to bring a story with an actual decision, conversation, and result.

18 candidate timelines, OAs, and interviews

01: Two OA posts from one Summer Intern candidate

Report dates: June 2026 · Role: Summer Intern · Location: Not stated · Result: Passed OA
The same author published two Wells Fargo Summer Intern OA posts eleven days apart, so this roundup conservatively counts them as one application experience.

1. One post said the OA arrived in February and contained roughly eight or nine medium-level items. It preserved a weighted-string hash collision question.
2. The other described a 90-minute HackerRank and preserved a recursive binary-search bug question.
   The posts do not establish whether these were two assessments or two pieces of the same assessment. Counting them once avoids inflating the title.

02: Cold application to Charlotte offer

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

1. Applied in August when applications opened.
2. Received a HackerRank about a week later with basic MCQs and two coding implementations.
3. Submitted location preferences.
4. Heard from a recruiter about a month later.
5. Completed a one-hour video interview: 30 minutes behavioral, then 30 minutes technical with a second interviewer.
6. Discussed projects, string manipulation, course fundamentals, and a case study about building a full-stack application for a business.
7. Received the offer call one or two days later.

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

Report date: October 20, 2025 · Role: SWE Intern · Location: Not stated · Result: Offer

1. Applied in August.
2. Completed HireVue.
3. Attended a mid-October Superday.
4. The Superday had a 30-minute technical block and a 30-minute behavioral block.
5. Technical discussion included online ordering for a grocery store, an easy LeetCode-style question, and resume follow-ups.
6. The candidate received the offer a few days later.
   This is one of the clearest examples of Wells Fargo mixing a small design prompt with light coding rather than running a pure algorithm round.

04: Same Superday shape, almost no coding

Report date: October 20, 2025 · Role: SWE Intern · Location: Not stated · Result: Not disclosed
A second candidate in the same discussion interviewed in mid-October and described the same overall split.

1. The first half was ordinary behavioral discussion.
2. The “technical” half asked for a high-level explanation of software development or how a data pipeline works.
3. The interviewer then returned to behavioral questions and talked about what interns can do.
   Same program, same week, noticeably different technical depth.

05: The exact 7+2 HackerRank

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

1. The OA arrived one day after the application.
2. The candidate had 60 minutes.
3. Seven MCQs covered APIs, SQL, and programming syntax.
4. Two LeetCode-style coding questions completed the assessment.
   This independently matches the nine-question format preserved in the July 2025 1Point3Acres report.

06: A short Charlotte interview built around the resume

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

1. A phone call was followed by a 30-minute Zoom interview.
2. The candidate said the interview was light on technical questions.
3. The interviewer asked for an introduction and a detailed resume walkthrough, including projects and technologies.
   The page records an offer. The underlying URL suggests the candidate later declined it, so the safest result label is simply “offer.”

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

Report date: August 7, 2025 · Role: SWE Intern · Location: United States · Result: No offer
The candidate described a broader HackerRank than most:

1. One DSA coding question.
2. One operating-systems question.
3. Questions about stacks and queues.
4. SQL material.
5. A prompt asking how to sort a heap.
   The full coding prompt and SQL query were not disclosed.

08: Perfect visible tests, then rejection

Report date: August 6, 2025 · Role: SWE Intern · Location: Not stated · Result: Rejected

1. Applied the day applications opened.
2. Took the OA the same day it arrived and passed every visible test case.
3. Received the self-paced location-preference step that day.
4. Was rejected before a live interview.
   The candidate could not see hidden-test scoring, and the source gives no rejection reason. The only honest conclusion is that visible OA completion and a location form did not guarantee advancement.

09: Networking MCQ and a coding problem that took a second pass

Report date: July 27, 2025 · Role: Technology Analyst Intern (Software Engineering) · Location: Not stated · Result: Not disclosed
A second candidate in a Summer 2026 OA discussion said:

1. Most MCQs were manageable, except one networking question outside their coursework.
2. The first coding task initially stopped them.
3. They returned to it and got it passing.
   The source does not name the network topic or coding prompt.

10: Application, HackerRank, then a location-only step in two days

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

1. Applied July 21 without a referral.
2. Completed HackerRank July 23.
3. Received the self-paced step the same day.
4. The OA had MCQs and coding, took about an hour, and involved implementing functions rather than an unusually hard algorithm.
5. The self-paced step only asked for two preferred locations.
   This is the cleanest evidence that the “on-demand interview” label can overstate what the step actually contains.

11: Nine preserved questions in 60 minutes

Report date: July 23, 2025 · Role: Technology Summer Internship – Early Careers · Location: Not stated · Result: Not disclosed
The candidate shared a 60-minute HackerRank with nine questions:

1. Integer Newton-style code tracing.
2. Recursive exponentiation code tracing, with the exponent cut off in the source image.
3. SQL IN syntax.
4. SQL duplicate removal.
5. A SQL CASE count over five rows.
6. REST 404 classification.
7. HTTP-method interpretation for a job-application API.
8. Faulty server replacement after three consecutive errors.
9. Minimum length after deleting AB or BB.
   Seven were knowledge or code-reading questions; two were full coding problems.

12: System design and OOP in one live round

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

1. The candidate called the HackerRank very easy.
2. There was one later interview round.
3. It contained two behavioral questions and two technical questions.
4. The technical questions covered system design and OOP.
   The source does not preserve the exact design or OOP prompts.

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

Report date: July 1, 2025 · Role: SWE Intern · Location: Plano · Result: No offer
The candidate's sequence was:

1. OA.
2. Location-preference form.
3. Recorded behavioral HireVue focused on personality and values.
4. Superday with a Wells Fargo interviewer.
   This is the fullest version of the pipeline in the admitted evidence. Other candidates skipped or compressed at least one of these steps.

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

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

1. One 30-minute technical interview and one 30-minute behavioral interview.
2. Breakout rooms included other interns and employees.
3. The preserved technical question was: explain CI/CD and your thinking about it.
4. The candidate felt leadership and teamwork mattered in the behavioral half.

15: Design SaaS for a flower shop

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

1. HackerRank came first and was described as manageable.
2. A one-hour live interview followed, split between behavioral and technical discussion.
3. Behavioral questions asked about alignment with company goals and values.
4. The concrete technical prompt was to describe a SaaS product for a flower shop.
   The report does not state how deep the interviewer expected the architecture to go.

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

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

1. HackerRank followed application review.
2. Final-round news arrived about two weeks later.
3. Technical discussion included a string-manipulation problem, basic system design, CI/CD, and front-end tools.
4. Behavioral questions covered interest in Wells Fargo, strengths, and learning when the next step was unclear.
   This candidate reported one of the broadest live technical mixes in the corpus.

17: Explain one easy coding problem; do not write it

Report date: October 2024 · Role: Technology / SWE Intern · Location: Not stated · Result: Offer

1. Behavioral preparation centered on STAR stories.
2. Technical discussion included one easy LeetCode-style problem, but the candidate only had to explain the solution rather than code it.
3. The remaining technical questions were theoretical.
   The candidate did not share the coding prompt or the theory topics.

18: Two easy coding questions and MCQs in about 30 minutes

Report period: July 2024 · Role: Technology / SWE Intern · Location: Not stated · Result: Not disclosed

1. The candidate applied July 17 and later received HackerRank.
2. The OA contained multiple-choice questions and two coding questions.
3. They described both coding questions as easy and finished the assessment in roughly 30 minutes.
   This older report is consistent with the later two-coding-question pattern, but it does not establish the exact time limit or MCQ subjects.