BNP Paribas software engineer candidates report HR screening, technical assessment or interview, and in some cases a later technical or managerial discussion. Preparation centers on project experience, Java or web fundamentals, backend problem-solving, and clear communication.
$140K
Avg. Base Comp
$168K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
BNP Paribas software engineer interviews reported here vary, but candidates commonly describe an HR conversation followed by a technical assessment or interview. One candidate explicitly described three stages: HR screening, a technical assessment, and a final technical interview; another reported an assessment, technical interview, and managerial discussion. Treat that as a useful pattern rather than a fixed sequence.
For the technical portion, prepare to explain work you have actually done. Candidates report project walkthroughs covering their contribution and challenges, plus foundational Java and Angular questions. Other reports describe a medium coding problem involving grouping anagrams, practical questions on JWTs, Apigee security, SSL, SQL performance, concurrency, thread safety, and debugging an asynchronous race condition. The reported scope ranges from fundamentals to hands-on backend reasoning, so clear explanations matter as much as a finished answer.
An online assessment may be part of the process. One candidate reported a one-hour, AI- and webcam-monitored test in their chosen technology, with tab switching treated as disqualifying. In HR or managerial conversations, be ready to summarize your background, motivation, and how you approach scenario-based or stressful situations. Candidate reports are limited, so the exact format and emphasis may differ by team.
Synthesized from 5 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 Bnp Paribas process.
I got through the first two calls HR and the core technical round—and now I’m just stuck in candidate limbo waiting to hear back on the third. The HR screen was quick, but they really pressed on whether my engineering style could handle a strict, highly regulated banking environment instead of just breaking things fast. The technical interview surprised me because they skipped abstract LeetCode brainteasers and went straight for real-world pain points: heavy backend concurrency, SQL indexing, and thread safety. I felt totally in control walking through API optimizations, but my hands definitely started sweating when they poked a hole in my async code and forced me to debug a edge-case race condition mid-execution on the spot. Now every phone notification is giving me a mini heart attack while I wait to see if I make it to the final manager round.
Questions asked: After clearing the HR call—which focused on my background, notice period, and motivation to work in a regulated banking environment—I moved to the technical round, where severe time pressure turned a standard Java live-coding prompt into a real test. They asked me to solve the Sliding Window Maximum problem (“Given an array of transaction amounts and a window size $k$, find the maximum transaction in every sliding window in $O(n)$ time using a Monotonic Deque”) while simultaneously firing quick-theory questions on Java 8+ HashMap treeification, Stream laziness, and atomic operations with ConcurrentHashMap.putIfAbsent(). Writing clean, compilable code in a shared editor while explaining my logic out loud was intense, but I managed to finish it, and now I'm just waiting to hear if I made it to the third and final manager round.
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 Bnp Paribas
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Client Solution Pushback | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Branch Sales Pivot | |
| Call Center Resource Management | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Random SQL Sample | |
| P-value to a Layman | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Cyclic Detection | |
| Type-ahead Search | |
| Three Zebras | |
| Precision and Recall | |
| Success Measurement | |
| Target Indices | |
| RAG Strict Source Control | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| Modifying a Billion Rows | |
| Type I and II Errors | |
| Same Characters | |
| Swap Variables | |
| Integer String Addition | |
| The Longest Journey | |
| Employee Benefits Outreach | |
| Triangle as Binary Array | |
| Drink Production Allocation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial HR conversation or quick screen. Topics may include your background, motivation, notice period, and whether your working style fits a regulated banking environment; prepare a concise account of your experience and interest in the role.
Candidates report either an online assessment or a technical discussion. Reported topics include Java and Angular fundamentals, a medium grouping-anagrams problem, SQL performance, JWTs, SSL, API security, concurrency, thread safety, and debugging. The exact technical scope appears to vary.
Some candidates report a final technical interview or managerial discussion after the technical stage. Candidates describe being asked to walk through past engineering experience, technologies used, project challenges, technical strengths, and scenario-based questions.
