BNY Mellon Technology runs large engineering centres in Pune and Chennai, and its software engineer loop leans toward core Java, Spring Boot, and SQL rather than heavy competitive coding.
Expect questions grounded in custody, payments, and settlement systems: idempotent transaction processing, multithreading, and data consistency across services. The bar is solid CS fundamentals plus the ability to reason about correctness in money-moving systems, and the culture round weighs stability and clarity over flash.
About BNY Mellon Technology
BNY Mellon Technology India is the fintech GCC of Bank of New York Mellon, the world's largest custody bank with $47T in assets under custody. Engineering hubs in Pune and Chennai build trading infrastructure, fund accounting, and payments platforms.
Application or referral through the BNY Mellon careers portal or campus drive
Online or hands-on coding assessment covering Java, SQL, and data structures
One or two technical interviews on core Java, Spring, concurrency, and databases
Managerial and HR round covering behaviour, projects, and compensation
Coding Assessment (60 to 90 min)
Java or language of choice, SQL queries, and one or two data-structure problems of easy to medium difficulty.
Technical Round 1 (45 to 60 min)
Core Java, OOP, collections, multithreading, Spring Boot, and REST design tied to your projects.
Technical Round 2 (45 to 60 min)
SQL and database design, system-level reasoning about transactions and consistency, and a light design discussion.
Managerial and HR Round (30 to 45 min)
Behavioural questions, team fit, notice period, and salary expectations.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical BNY Mellon Technology recruitment process has 4 stages: Application or referral through the BNY Mellon careers portal or campus drive → Online or hands-on coding assessment covering Java, SQL, and data structures → One or two technical interviews on core Java, Spring, concurrency, and databases → Managerial and HR round covering behaviour, projects, and compensation.
BNY Mellon Technology typically conducts 4 interview rounds: Coding Assessment (60 to 90 min): Java or language of choice, SQL queries, and one or two data-structure problems of easy to medium difficulty.; Technical Round 1 (45 to 60 min): Core Java, OOP, collections, multithreading, Spring Boot, and REST design tied to your projects.; Technical Round 2 (45 to 60 min): SQL and database design, system-level reasoning about transactions and consistency, and a light design discussion.; Managerial and HR Round (30 to 45 min): Behavioural questions, team fit, notice period, and salary expectations..
HireStepX recommends the Correctness-first framework for this type of interview: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs.
To answer this question well, HireStepX recommends the Correctness-first approach: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Correctness-first approach: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Correctness-first approach: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Correctness-first approach: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Correctness-first approach: Requirements, then data model, then concurrency and failure handling, then a clean testable API, then trade-offs. Ground your answer in a specific real example from your own experience.