Bentley Systems Software Engineer Interview Guide

Our candidates report a process that can feel surprisingly uneven, but one theme shows up clearly: Bentley seems to care less about polished interviewing theater and more about whether you can handle a very specific filter quickly. In the strongest technical signal we saw, the coding assessment was custom, time-compressed, and harder than expected, with medium-to-hard problems that demanded careful edge-case handling rather than rote familiarity. That tells us the bar is not just correctness, but how fast you can orient yourself when the problem doesn’t look like a textbook prompt.

We also saw a mismatch between what candidates expected and what interviewers actually emphasized. One candidate applied for C++ but found the conversation centered on design patterns, while another was told to expect React JS and some C# in the coding stage, which suggests the team values practical breadth over a single-language identity. The non-obvious risk here is not lack of experience, but misalignment with the interviewer’s mental model. When that happens, even solid answers can land awkwardly if you don’t connect your examples to the patterns or systems the panel is actually using.

The early screening experience also matters more than it might at other companies. Multiple candidates described a very administrative front end — salary expectations, notice period, work authorization, and motivation — with limited human warmth. That means Bentley is likely looking for candidates who are clear, direct, and low-friction to evaluate. In our view, the candidates who do best here are the ones who can stay precise under pressure and translate their experience into the company’s language, even when the process itself feels impersonal.