Wells Fargo

The Wells Fargo campus process started with an online assessment. It had multiple sections, including verbal ability, business/data interpretation and coding. The coding part was time-bound, so I had to manage the aptitude sections carefully instead of spending too much time on any single question. Similar on-campus experiences report a combination of aptitude and coding, with coding questions around arrays, linked lists and greedy techniques. I cleared the initial screening and moved to the technical interviews. My first technical round was primarily DSA. The interviewer started with a discussion about my approach to problem solving and then gave me a binary-tree problem. I was asked to explain how I would find the top view of a binary tree and write the pseudocode. I discussed using level-order traversal with horizontal distance and explained why a map could be used to retain the first node encountered at each distance. A similar question has been reported in an on-campus Wells Fargo SWE Intern interview. After the coding discussion, the interviewer moved to core CS. We talked about OOP concepts, particularly abstraction, inheritance and encapsulation. I was also asked some questions around operating systems and DBMS. The questions weren't extremely theoretical, but the interviewer expected me to explain the concepts rather than just give definitions. The second technical round was different. Instead of another pure DSA interview, a large portion of it was based on my resume. I had to explain my projects, why I selected particular technologies, and what problems I had personally solved while building them. This kind of resume-focused second round is common in reported Wells Fargo internship interviews, where candidates have been questioned about projects and their technical decisions. I was also asked a few SQL and database questions and had to explain how some of my project components worked internally. The interviewer went deeper whenever I mentioned a technology, so simply knowing the name of a framework wasn't enough. I realized that every technology on the resume could become an interview question. The final interaction was a short HR discussion covering motivation, relocation and general background. After completing the process, I waited for the final result but eventually received a rejection. There wasn't detailed feedback explaining which round affected the decision. My main takeaway was that Wells Fargo's process wasn't only about solving DSA questions. The combination of aptitude, coding, core CS and detailed resume discussion meant I needed to be equally prepared to defend everything I had written on my resume.