Real, anonymous reports from people who interviewed for Software Engineer at ING, newest first and distilled into what to expect across the loop.
I went through a pretty smooth two-interview flow that felt friendly from the start. After an initial recruiter conversation, a short time later I had a Java-and-relational-database focused technical session. The pace wasn’t stressful; the atmosphere was relaxed, and I did a small live coding exercise while we talked through the Java and database pieces. That interview mostly felt like a check on how I think and how I write code, rather than trying to trip me up.
After an initial HR call, I went into a technical interview that was much more intense than I expected. The format was a three-person panel, and it quickly turned into a deep dive on Java fundamentals and how I reason about code. We covered things like OOP, Java 8+ topics, functional programming concepts, and the Spring and persistence side, including JPA/Hibernate. There was also live problem solving: one coding question without an IDE, and we shifted into a more interactive, pair-programming style.
The interview process typically begins with an HR screening followed by a technical interview, which may include coding assessments and behavioral questions. Candidates noted variations in the flow, with some experiencing a more structured approach while others found it disjointed and slow.
Technical interviews often emphasize Java fundamentals, including OOP principles, Java 8+ features, and frameworks like Spring and Hibernate. Candidates should be prepared for live coding exercises, often in a pair-programming format, and questions related to their specific tech stack.
Many interviews include behavioral questions aimed at assessing cultural fit and soft skills, such as teamwork, conflict resolution, and Agile methodologies. Candidates should prepare to discuss their past experiences and how they relate to the role.
Candidates frequently reported issues with communication and follow-up after interviews, including delays in receiving feedback or updates on their application status. This lack of clarity can lead to frustration and uncertainty about the outcome.
The difficulty level of interviews varies, with some candidates finding the technical assessments challenging, particularly under time constraints. Others felt the process was manageable but noted that the pressure of the format could impact performance.
Some candidates experienced take-home assignments or coding tasks that required significant effort and attention to detail. Feedback on these assignments was often brief, leaving candidates unclear about areas for improvement.