
BNY Mellon Software Engineer candidates report three rounds that combine project depth, coding, system-design tradeoffs, and a manager or HR conversation. Prepare to explain decisions clearly as well as solve problems.
$88K
Avg. Base Comp
$130K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
BNY Mellon Software Engineer candidates report a three-round process with a mix of technical evaluation and a final people-focused conversation, although the order can vary. One candidate described two technical interviews followed by HR; another began with a hiring-manager chat, then completed live coding and system design. Treat that variation as a reason to prepare both your technical narrative and your behavioral examples early.
Coding preparation should cover more than one familiar pattern. Reported topics include trees, arrays and greedy approaches, graphs, dynamic programming, a topological-sort variation, and merging overlapping appointment intervals while finding free gaps. In a live setting, explain why a simple sorted pass fits the input before reaching for a more complex data structure. Candidates also report questions that start with CS fundamentals and move into detailed discussion of projects or internship work, including the infrastructure or system-design choices behind them.
The design portion may emphasize tradeoffs rather than a single ideal answer. One candidate was asked to design a multi-tenant scheduling system that prevents double bookings under simultaneous requests; another report described practical infrastructure judgment. Be ready to state assumptions, explain consistency and locking choices when relevant, and connect each decision to a constraint. The evidence is limited to a small set of candidate accounts, so specific sequencing may differ.
Synthesized from 4 candidate 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.
Honestly the whole thing was three rounds and I was way more nervous for the system design one than I expected. First round was a quick chat with the hiring manager, mostly vibes, felt fine. Second round was a live coding thing and I completely blanked on a basic edge case for like two minutes, just sat there staring at the screen while the interviewer waited. Recovered eventually but my heart was going. Third round was system design and that's where I actually felt good, probably because it overlapped with stuff I'd already built at work. The surprising part was how much they cared about how I talked through tradeoffs rather than landing on the "right" answer. I left convinced I'd bombed it because of the coding round, then got the offer two days later and just sat there confused for a bit before telling anyone.
Questions asked: Okay so round two, the coding one, the actual question was something like "given a list of time intervals representing booked appointment slots, write a function that merges overlapping ones and tells you the free gaps in a day." Sounds simple written out like that but I started overengineering it with a heap when a sorted list and a single pass would've done it, that's where I lost the two minutes just staring. Interviewer eventually nudged me with "do you need that structure for this input size" and I felt my face go red over a video call, which is a special kind of humiliating. Round three, system design, they asked me to design a multi tenant scheduling system that takes booking requests from multiple channels at once and guarantees no double bookings even if two requests hit at the exact same time. I basically just talked through the same overlap and locking logic I'd built for real, which is probably why it felt comfortable instead of stressful. There was also a take home before any of this, not technical exactly, just a written prompt asking me to describe a time I disagreed with a decision and what I did about it, no word limit given which threw me more than any code question did.
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
How would you design a transaction to prevent overselling in a concurrent ticket booking system?
| Question | |
|---|---|
| Minimum Days for Scheduling All Meetings | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Over-Budget Projects | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a technical conversation that can begin with CS fundamentals, projects, and internship experience. Be prepared to move past a high-level project summary and explain what you built, the choices you made, and relevant infrastructure or design details.
Candidates report coding questions involving trees, arrays or greedy approaches, graphs, dynamic programming, a topological-sort variation, and merging overlapping booking intervals. One report described a HackerRank-style environment, while another described live coding; practice communicating a simple approach and edge cases.
Candidates report a system-design discussion focused on concurrent booking requests and avoiding double bookings, as well as a manager or HR-style conversation. Expect to explain tradeoffs and discuss your resume, perspective, or behavioral scenarios; the exact order may vary.