After being contacted by the recruiter, I had two technical interviews. A phone interview with someone from the US asking about Java and SQL. The second technical interview was in person with a developer from the Dublin team and again a phone call with 2 people from US.
The in person was basically with random Java questions, very similar to Java certification questions. These types of questions do not prove whether a developer is good or not, it only shows if someone is good at memorizing the theory. And as a developer, I hate this kind of thing, a good developer is more than code theory.
I was asked the same questions twice, face to face and then by voice call. I didn't like it and told the interviewer. I understand that the company has to make sure about who its hiring, but I don't agree with that type of interview methodology.
Also, the company looks quite similar to my current company, an US financial company based on Dublin that reports everything to the team in US. Basically, the Dublin team has no decision-making autonomy, depending on US approval.
HashMap vs HashTable ArrayList vs LinkedList Interface vs Abstract class What is final keyword Synchronized vs Volatile Design patterns Java exceptions Java stream Spring framework SQL ... Memorize the answers of the Java certifications and you should be fine in the interview. Even though I have Java certifications, I don't agree with this kind of interview methodology.
The following metrics were computed from 1 interview experience for the Intercontinental Exchange Java Developer role in Dublin, Ireland.
Intercontinental Exchange's interview process for their Java Developer roles in Dublin, Ireland is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Intercontinental Exchange's Java Developer interview process in Dublin, Ireland.