Candidates report Java-heavy Intercontinental Exchange software engineer interviews: collections, threading, Spring Boot, and security, plus project walkthroughs. Formats and pacing vary widely between reports.
$135K
Avg. Base Comp
$160K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Intercontinental Exchange software engineer interview as Java fundamentals first, algorithm puzzles second. Reported Java topics include collections, lambda expressions, stack versus heap, CompletableFuture and thread safety. One candidate describes implementing an LRU cache and justifying the design choices aloud. One recent candidate says the questions leaned toward practical backend knowledge. Topics included Spring Boot auto-configuration and dependency injection, OAuth2 and JWT validation, SQL injection and XSS, Kafka partition keys and dead-letter queues, SQL versus NoSQL, and Angular fundamentals.
Coding problems are usually described as easy to medium. Reports mention the longest palindromic substring, concatenating arrays, and Java functional-interface tasks on HackerRank. Examples include a distinct-character mapper and a prefix predicate. One candidate interviewing for a Java backend role faced a single demanding round on algorithms and performance. That round placed heavy emphasis on input validation and defensive coding.
Project discussion also comes up. One candidate was asked to walk through a past project in a second round with a team lead and a project leader. Prepare a concise story for each project on your resume. Another candidate felt an interviewer had not read their resume and was working through a checklist.
Experiences differ a lot. Some describe patient, collaborative interviewers. Others describe a hostile on-site, an unconfirmed phone screen or a month-long wait for feedback. Confirm logistics with your recruiter in writing and treat any single report as one data point.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Intercontinental Exchange process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Intercontinental Exchange
Listing Bookings Aggregation
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Bagging vs Boosting | |
| Over-Budget Projects | |
| String Shift | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Random SQL Sample | |
| Google Maps Improvement | |
| Weighted Keys | |
| Find the Missing Number | |
| Total Spent on Products | |
| Sum to N | |
| Prime to N | |
| P-value to a Layman | |
| Top 3 Users | |
| Size of Joins | |
| Slacking Employees Salaries | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates report starting with an HR or recruiter call. One candidate received a next-day phone interview request, suggested an alternative time and never got a confirmation. Confirm times in writing.
One candidate describes a HackerRank test with starter code and two Java functional-interface problems. One was a mapper that counts distinct characters and the other a prefix-matching predicate. Practice Java streams and functional interfaces.
Candidates describe live technical conversations with a team lead or engineers. Reported topics include Java collections and concurrency, an LRU cache, string and array problems, Spring Boot, security, and Kafka. One candidate reports practical questions instead of heavy DSA. Another reports a demanding single round on algorithms and secure coding.
One candidate had a second round with the team lead and a project leader. It covered a project walkthrough and two more LeetCode-style coding questions. Another candidate reports an on-site after two earlier rounds on work experience and Java. Prepare to explain what you built and why.
Follow-up varies. One candidate waited about a month for a rejection after interviews that went well. Another describes a process that stretched over about two months before an offer they declined. Plan for variable communication.
