Bentley Systems software engineer candidates describe a recruiter screen, an online coding assessment, and technical interviews that stress OOP fundamentals, data structures, and project walkthroughs. Stack questions vary by team.
$95K
Avg. Base Comp
$110K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Bentley Systems software engineering roles describe a process built around object-oriented fundamentals and being able to explain your own work. OOP comes up directly. One candidate was asked about the key points of object-oriented programming, its advantages and when it is useful. Another faced core OOP questions alongside data structures in a panel. Several candidates were also asked to walk through past projects, the approach they took and the languages they used, so be ready to justify your design decisions out loud.
The coding assessment is where several candidates report friction. One candidate had two hours for two custom medium-to-hard problems and solved only one. Another described a 2-hour take-home test followed by coding challenges similar to LeetCode. Data structure questions reported in interviews include:
The technical focus seems to depend on the team. One candidate was asked about React hooks, the JavaScript event loop, caching and REST API security, plus a surprising C++ round. Another, coming from a C++ background, was pressed on C# and .NET. A third applied for a C++ role and found that both the HR prep material and the design-pattern discussion felt disconnected from what they expected. Check the job description for the stack and prepare fundamentals that carry across languages.
Communication is the other recurring theme. One candidate describes a screening handled entirely by email, with questions on salary expectations, notice period and work authorization, slow replies and a generic rejection. Others describe the process as long and drawn out. Keep your answers concise and have a clear reason for wanting Bentley.
Synthesized from 13 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 Bentley Systems process.
The process started with the recruiter clearly laying out what to expect, which I appreciated. There were multiple technical rounds, and I was grilled on graph and tree problems that felt above the typical level for the role — not impossible, but definitely challenging. The questions themselves were solid and tested real algorithmic thinking rather than trivia.
Beyond the technical side, there were behavioral and HR rounds mixed in. Interviewers asked standard motivational questions, probed on why Bentley specifically, and dug into my relevant experience in the field. The format was a mix of virtual interviews and at least one in-person component, which helped me get a better sense of the team and culture. One round included an assignment or presentation component that happened on site, which was different from the typical phone-screen-to-coding format I'd done before.
What surprised me most was the inconsistency in difficulty. Some rounds felt very easy and basic — problems I breezed through — while others were genuinely demanding. That mismatch made it hard to gauge where I actually stood in the pipeline. I made it far enough to be in contention, but didn't ultimately land an offer. Looking back, I wish I'd spent more time on graph traversals and tree manipulation before going in, since those showed up in multiple forms across the interviews.
Prep tip from this candidate
Focus heavily on graph and tree problems — they came up repeatedly and at varying difficulty levels. Practice not just basic traversals, but more complex graph algorithms and tree manipulations, as the bar seemed higher than typical coding interviews for this role.
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 Bentley Systems
How would you diagnose and speed up a slow SQL query when system metrics look healthy?
| Question | |
|---|---|
| Text Editor With OOP | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Raining in Seattle | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Bagging vs Boosting | |
| Upsell Transactions | |
| Real-Time Transaction Streaming | |
| Daily Retention Summary | |
| P-value to a Layman | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Job Recommendation | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call or email exchange first. Questions covered why they were looking for a new job, what they liked about Bentley, salary expectations, notice period and work authorization. One candidate says this stage was handled entirely by email and ended in a generic rejection, so respond clearly and concisely.
Several candidates report a timed coding test before technical interviews. One describes a two-hour test with two custom medium-to-hard problems and solved only one. Another mentions a 2-hour take-home test. Practice unfamiliar problems under time pressure rather than relying only on familiar LeetCode questions.
Candidates report interviewers asking them to walk through past projects, the approach they took to solve them and the languages they used. One described a general interview of 30 minutes to an hour focused on their background and a project related to the role.
Technical rounds reportedly cover OOP concepts, linked lists and trees. Depending on the team, candidates also report React and JavaScript topics, caching, REST API design, C# and .NET, design patterns or a C++ round. One candidate describes two hour-long interviews with lead team members, and another a panel of three people.
One candidate mentions a managerial round as part of the broader process, though they did not reach it. Not every candidate reached later stages, so treat it as possible rather than guaranteed.
