Real, anonymous reports from people who interviewed for Software Engineer at Bentley Systems, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role with a long, difficult sequence centered on an unusually hard take-home/coding test and two technical lead interviews across roughly 2–4 weeks.
I interviewed for a Software Engineer role with a long, difficult sequence centered on an unusually hard take-home/coding test and two technical lead interviews across roughly 2–4 weeks.
The interview process typically begins with a recruiter or HR screening that lasts about 30-60 minutes, focusing on the candidate's background, fit for the role, and sometimes includes basic technical or logical questions.
Candidates are required to complete a coding assessment, usually online, consisting of LeetCode-style problems that are often medium to hard in difficulty, with a strong emphasis on correctness and efficiency.
The technical interview rounds involve deep discussions with team leads or managers, focusing on object-oriented programming, system design, and specific technologies relevant to the role, often requiring candidates to explain their thought process.
There is variability in the assessment process, with some candidates experiencing a more structured approach while others find the focus on technical fit misaligned with their backgrounds, leading to unpredictable outcomes.
Candidates report mixed experiences with post-interview communication, with some facing long waits or lack of feedback after interviews, which can lead to frustration regardless of performance.
The overall difficulty of the interview process is perceived as high, with candidates often feeling that the expectations for technical knowledge and problem-solving skills are rigorous and can catch them off guard.
