BNY Mellon Software Engineer interview typically runs 3 rounds: resume screening, two technical rounds, and a final manager or HR round. It usually takes about 2-4 weeks and is fairly standard but can be uneven, with some rounds going deeper than expected.
$125K
Avg. Base Comp
$230K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
Our candidates consistently describe BNY Mellon as a process that looks straightforward on paper but gets more demanding once the conversation starts. The recurring theme is depth over breadth: interviewers keep pushing past surface-level explanations of projects, internships, and resume bullets until they can tell whether you actually built the thing or just know the headline. One candidate said a round felt like a detailed walkthrough of the infrastructure behind their work, and another noted that even a broad opening quickly turned into specifics about what they had done and why.
We also see a clear preference for practical engineering judgment, not just textbook answers. The technical mix spans coding, data structures, and more applied infrastructure thinking, with questions ranging from linked-list implementation to estimating RAM for an EC2 instance. That combination tells us BNY Mellon is looking for people who can move between algorithmic correctness and production reality. The non-obvious trap here is assuming the interview will stay in one lane; multiple candidates reported a wider spread of topics than expected, including combinatorics and graph variations, which rewards candidates who can stay calm when the problem shifts.
What tends to separate strong candidates is how concretely they explain their decisions. Our candidates report that the best conversations were the ones where they could defend tradeoffs, walk through implementation details, and show they understood the systems they had touched. In other words, BNY Mellon seems to value credible engineering judgment as much as clean code, and the candidates who do best are the ones who can make their experience feel real, specific, and technically grounded.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Bny Mellon process.
The process was for an on-campus hiring drive, and it started with an online assessment that was medium difficulty. The OA had three coding questions, and the themes were pretty standard but still required solid practice: binary search, graphs, and dynamic programming. What stood out to me was that partially correct solutions seemed to be considered, so even if you didn’t fully finish everything, there was still a chance to move forward.
After the OA, I went through two interview rounds. The first interview was fairly smooth and felt easier than the assessment. It was mostly technical, with questions around data structures, Python-specific concepts, and a few simple follow-ups on my projects. The interviewers were kind and kept the conversation comfortable, so it felt more like a discussion than a grilling. The second round was also technical, but it had some HR-style behavioral questions mixed in. I was asked scenario-based questions like what I would do if no one on my team was addressing a problem, so it wasn’t just coding. Later, they also touched on topics like IP queries, graphs, sliding window, and even OSI model from computer networks, which made the interview feel broad rather than narrowly algorithmic.
Overall, the difficulty was manageable if you had done LeetCode medium-level problems and were comfortable explaining your projects clearly. The technical rounds leaned more toward practical fundamentals and language familiarity than hard algorithmic depth. I ended up getting the offer, and the whole process felt organized and fair. My main takeaway would be to prepare a few solid graph and DP problems, review your language basics well, and be ready for project discussion plus a few behavioral scenarios.
Prep tip from this candidate
Focus on graph and DP problems from the OA, then review Python basics, sliding window, and LRU cache-style questions for the interviews. Also be ready to discuss your projects and answer scenario-based behavioral questions about team dynamics.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Bny Mellon
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Find the Missing Number | |
| Maximum Profit | |
| Prime to N | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| String Shift | |
| Employee Salaries | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Hurdles In Data Projects | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Slacking Employees Salaries | |
| P-value to a Layman | |
| Size of Joins | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Cumulative Distribution | |
| Level Of Rain Water In 2D Terrain | |
| Sum to N | |
| Append Frequency | |
| Google Maps Improvement | |
| Sort Strings |
Synthesized from candidate reports. Individual experiences may vary.
The process may begin with a resume screening call to review your background and fit for the Software Engineer role. This stage is typically used to confirm your experience, projects, and overall alignment before moving into technical interviews.
The first technical round is broad and often starts with CS fundamentals, your projects, and internship experience. Interviewers dig deeply into what you actually built, and may include a medium-level combinatorics question or a coding task such as reversing a linked list in a HackerRank-style environment.
The second technical round is more DSA-heavy and can include LeetCode-style problems across trees, arrays/greedy, graphs, and dynamic programming. Candidates also reported system design and practical infrastructure questions, such as estimating RAM requirements for an EC2 instance or discussing graph variations like topological sort.
The final round is with HR or a hiring manager and focuses on resume review, general discussion, and behavioral fit. Expect questions about your experience and broader perspective, such as how you think the tech industry will change in the next five years.