The process began with registration on both the campus placement portal and Wells Fargo’s careers portal. The Online Assessment was conducted offline at the Training and Placement (T&P) cell. It was a comprehensive test structured into four sections, designed to evaluate a mix of technical and analytical skills. Section 1: Coding (DSA): This section focused on Data Structures and Algorithms, primarily touching on Graphs and Dynamic Programming. The difficulty ranged from Easy to Medium. My specific question was a variation of Dijkstra's Algorithm. Section 2: English: Standard verbal ability questions largely focused on vocabulary and grammar. Section 3: Quantitative Aptitude: This section required solid data analysis and interpretation skills to answer the given questions. Section 4: Basic Coding: A final, shorter section containing two very easy foundational programming questions. Key Takeaway for the OA: Interestingly, core computer science subjects like Object-Oriented Programming (OOPs) and Database Management Systems (DBMS) were not explicitly tested in the OA. However, do not skip them! Having a strong grasp of them is highly necessary for the interview rounds. The Interview Day All of the interview rounds were conducted on a single day, making it a fast-paced but exciting experience. Round 1: Technical Interview (Basic Problem Solving) This was a foundational round designed to test basic logic and coding fluency. The Experience: The interviewer focused on simple problem-solving questions. For example, a classic question I was asked was to swap two numbers without using a temporary variable. The Result: The results were announced very quickly. This was a heavy elimination round, with approximately half of the candidates being rejected. Fortunately, I was selected to move forward. Round 2: Technical Interview (Projects and Design) This round was noticeably more challenging and dove deeper into practical application and system design. Project Discussion: The interviewer began by asking questions about my personal projects. Since my projects were in the AI/ML domain, this part was straightforward and a great opportunity to showcase my interests. API Design Challenge: The core challenge was to design an API. The twist? The interviewer specifically requested the design to be implemented in Java—which was not the backend language I had primarily used. Adaptation: I communicated this clearly and successfully negotiated to focus on writing the necessary functionality and core logic instead of a full, syntax-perfect Java API structure. This approach satisfied the interviewer. The Result: My interview was actually cut slightly short due to a technical glitch. Despite this unexpected hiccup, my logic held up, and I was selected for the final round. Round 3: HR Interview (Cultural Fit) After the technical gauntlets, the final round was a very relaxed and friendly HR conversation. The focus shifted entirely to getting to know me as a person and assessing cultural fit. Topics Discussed: We talked about my family background, had general conversations about Wells Fargo's work domain, and discussed various non-technical topics. The Result: The interview ended on an incredibly positive note, with the HR representative stating, "I will see you next summer."