Wells Fargo

My Wells Fargo interview was one of those interviews where knowing DSA alone was not enough. I had to be comfortable discussing my projects, SQL, OOP, DBMS, and even some practical engineering situations. The process started with an online assessment containing verbal ability, business/data interpretation, and coding. The business section had questions based on graphs and tables, while the coding section included array and string problems. The test was strictly timed, so I had to be careful not to spend too long on one question. I cleared the assessment and was shortlisted for the interviews. My first technical interview began casually with my introduction, but the discussion quickly became detailed. The interviewer picked projects from my resume and asked why I had selected particular technologies, what challenges I faced, and how I would improve the implementation. For DSA, I was asked to count the frequency of elements in an array and then explain how a HashMap works internally. Another problem involved comparing two dates given in `dd/mm/yyyy` format and determining which one came later. We also discussed the difference between an array and a linked list and practical situations where different data structures would be useful. SQL was another important part of the discussion. I was asked about joins, database keys, indexing, and how I would design tables for a particular scenario. I also had to write SQL queries rather than simply explain the theory. The final round was more conversational. Questions included why I wanted to join Wells Fargo, my strengths and weaknesses, teamwork situations, and what I knew about the company. I was also asked about relocation and my career goals. After completing the interviews, I received the confirmation that I had been selected for the Wells Fargo internship.