Myntra | Software Engineer - Backend (M1) | Bangalore | March-2022 [Accepted]
Question Details
Current Position: Program Associate at Wells Fargo Experience:- 8 months
Round 1 OA Round Total Questions : 31 No. of Sections: 8 Total Time: 60 mins Assessment Summary: Test Included 1 Programming Question along with MCQ...
Full Details
Current Position: Program Associate at Wells Fargo
Experience:- 8 months
**
Round 1 OA Round**
Total Questions : 31
No. of Sections: 8
Total Time: 60 mins
*
Assessment Summary:
Test Included 1 Programming Question along with MCQ type questions related to Java, HTML, JS, Data Structures, DBMS, etc.
*
Programming Question:
I don\'t remember exact question, but it was similar to "Connect N Ropes with Minimum Cost" - to be solved by Priority Queue.
**
Round 2 DS Algo Round**
There were 2 interviewers & asked 2 questions and asked to code on screenshare.
They asked for Time &
Space complexity for every approach discussed.
1. Merge K-Sorted Linked Lists ( had a healthy discussion over different approaches on this question)
2. Longest Increasing Subsequence ( there\'s a O(nLogn)
approach to this question )
**
Round 3 Hiring Manager Round**
This round started with the manager\'s intro, The kind of person he\'s looking for the role and What responsibilites he/she is expected to deliver once selected for the role, my introduction and discussion on my projects.
Few Questions on DBMS like what is indexing, why it is used, discussion about 3NF.
Few OOPS based questions.
Few situation based questions like what is I had a conflict with my manager, what if I could not meet deadline.
(Always try to give some kind of numbers to your work, like scaled application from a thousand users to lakhs of users, solved 80% of pending bugs in project, etc)
**
Round 4 HR Round**
This round was mostly like a conversation.
Started with my introduction and a brief about my projects and responsibilities in my current company.
Why I want to switch company, and why so early ( 8 months experience ).
And why Myntra ?
The interviewers in all the rounds were very friendly.
And special mention to HR who conducted the interviews, constantly kept updating me and conducted the process smoothly.
**
Verdict Selected & Accepted the offer**
About This Question
This is a reported interview question from a wells fargo interview for a backend role during the oa round reported in 2022.
It covers the following topics: Sql, Linked List, Queue, Dynamic Programming, Heap, Behavioral, Stack .
About Wells Fargo Interview Reports
This question was reported by a candidate who interviewed at Wells Fargo. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Wells Fargo are the higher-signal extractions to take from this report.
For broader preparation context, the Wells Fargo interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Wells Fargo reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Wells Fargo Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Wells Fargo reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.