Intercontinental Exchange logo
Intercontinental ExchangeQA Automation Engineer
Updated Dec 6, 2025

Intercontinental Exchange QA Automation Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for QA Automation Engineer at Intercontinental Exchange, newest first and distilled into what to expect across the loop.

Get your personalized Intercontinental Exchange QA Automation Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
11 months ago
Difficult Negative Pune

I went through a long, confusing interview run that started with a full-day hiring drive. It kicked off early in the day and stretched all the way to late afternoon, with multiple stages stacked back-to-back. First I did a coding round with a set of programming problems and had to pick one to solve. After that, I moved into a technical discussion that touched Core Java, Selenium, Git, and CI/CD. The next segment varied in depth—some focus areas leaned into day-to-day QA and Agile, while mine also covered heavier territory like API testing and coding concepts. There was an HR discussion afterward, then a VP conversation that centered on role expectations, motivation to join, and whether I could comfortably work from the office five days a week.

What threw me off was how little clarity there was as the day went on. I completed several rounds in the same day, but nobody gave a clear view of where I stood or what the next step would be. I was only later contacted for follow-up technical discussions tied to specific projects—one that lasted close to an hour and another around 45 minutes. Even after those, there was still no real feedback or decision communicated to me, just repeated requests to re-demonstrate technical fit.
11 months ago
Average Positive Hyderābād

My interview at ICE felt surprisingly smooth and easy to navigate. I didn’t get the sense of a “gotcha” environment; instead, the conversation came across collaborative and the people I spoke with sounded genuinely knowledgeable. The whole vibe was more like a technical discussion than a stressful exam.

I remember the tone being polite and comfortable, with the interviewer openly discussing the kinds of frameworks and tools they worked with. We covered testing at a level that felt practical, not overly theatrical, and it didn’t feel like the process was trying to trick me. Even though I didn’t end up selected, the interaction itself left me with a generally positive impression.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.