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 a recruiter screen, I moved into a pretty classic cadence of technical checkpoints. I had an online coding assessment on HackerRank, then followed that with time with the hiring manager. From there the process expanded into multiple panels where I ended up speaking with engineers and then higher-level leadership, including director and VP-level rounds. Overall it took a bit of time, but the difficulty felt fairly balanced—coding was average and the overall interview pace matched what I expected from a software engineering process.
My process started with a lot of coordination and then moved fast. I first spoke with a VP-level contact on the phone, then had a screening call with HR, and after that I joined a Zoom call with the hiring manager. The final stage felt like a true super-day, where I met multiple team members in sequence—so I went through several conversations back-to-back instead of one or two big sessions.
The interview process typically begins with a recruiter call, followed by a series of technical assessments and interviews that can include both phone and onsite rounds. Candidates reported a mix of panel interviews and back-to-back sessions, with some experiencing a quick decision timeline while others faced delays in feedback.
Candidates faced a variety of technical evaluations, including HackerRank coding assessments and live coding interviews that emphasized Java fundamentals, algorithms, and data structures. The difficulty level varied, with some candidates finding the assessments tightly timed and challenging, while others felt they were reasonable.
Interviews often included behavioral components where candidates discussed past experiences and project work, alongside managerial interviews that assessed fit within the team. The focus was on communication and alignment with the company's values, with some candidates noting a lack of professionalism in certain interactions.
Candidates reported that interviewers sought depth in technical discussions, often probing into performance, correctness, and security considerations during coding tasks. The emphasis was on not just solving problems but explaining thought processes and design decisions clearly.
The communication style varied, with some candidates appreciating the directness and professionalism during interviews, while others experienced frustration due to delayed feedback and unclear expectations. Regular updates were noted as a positive aspect by some candidates.
Candidates had mixed feelings about their overall experience, with some feeling validated and others frustrated by the process. While many appreciated the structured approach, the lack of offers for some led to reflections on the alignment between their skills and the company's expectations.