Real, anonymous reports from people who interviewed for Software Engineer at Intercontinental Exchange, newest first and distilled into what to expect across the loop.
After the initial recruiter call, my process progressed to a technical screen and then interview stages that built toward a hiring manager conversation and additional rounds. The overall difficulty was average for me, and the vibe was welcoming—everyone I interacted with sounded friendly and approachable.
After a general phone screening, I took an online HackerRank test that felt like the main gate for the role. The coding portion ran about 1.5 hours and paired problem solving with Java basics: I had two coding questions plus a chunk of multiple-choice questions covering fundamentals like Java knowledge. It was structured enough that I knew exactly what I was walking into, but the time pressure still made it feel intense.
The interview process typically starts with a recruiter call, followed by a technical screen, and then progresses through multiple back-to-back technical rounds, often culminating in a managerial discussion. Candidates should expect a structured timeline with clear stages, but the overall experience can feel intense due to the volume of interviews.
Candidates will face a mix of coding questions, often focused on Java fundamentals and practical problem-solving, with some interviews including live coding or HackerRank tests. The emphasis is on both coding ability and reasoning, so candidates should prepare for a variety of technical prompts and discussions.
Behavioral interviews are integrated into the process, often focusing on past experiences, design decisions, and how candidates approach problem-solving. Candidates should be ready to discuss their work history and how it aligns with the company's needs, as managerial rounds can delve into both technical and interpersonal skills.
Some interviews may include discussions about AI-enabled coding and the responsible use of technology, reflecting the company's interest in modern development practices. Candidates should be prepared to articulate their views on integrating AI into workflows and the importance of human oversight.
The overall difficulty of the interviews is generally described as average to high, with candidates noting a mix of supportive and challenging environments. While the process is often well-structured, some candidates reported feeling overwhelmed by the pace and volume of questions, which can lead to a sense of pressure.
Candidates have reported varied experiences with feedback and communication throughout the process, with some expressing frustration over delayed responses or unclear expectations. It's important for candidates to seek clarity on next steps and to be proactive in following up if they feel uncertain.