Meltwater Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Meltwater.
Meltwater
Software Engineer
Senior Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding
The experience was quite bad. I was initially told it would be an introductory chat about past projects, but it ended up being a DSA technical round. HR should have clarified this. The interview felt uncollaborative, with the interviewer being unapproachable and dismissive of questions, just saying 'you have to think.' While I get testing problem-solving, some basic guidance would make it more constructive and less discouraging. Two questions were asked, and although I answered them, the interviewer wasn't satisfied and didn't explain what was wrong or provide failing test cases.
Confirmed questions2 questions
- An array-based question
- A follow-up array-based question
Meltwater
Software Engineer
Mid Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral
The interview process involved two rounds via Google Meet, suitable for a backend role focused on Java/Spring. The first interview was with the tech lead, conducted in Hungarian, covering technical aspects. The second interview was the 'HR' part, focusing on interpersonal elements rather than just programming. This part was in English because the team is international, a detail I was informed about beforehand. I also had the opportunity to ask questions.
Confirmed questions6 questions
- Could you discuss the advantages and disadvantages of using @Autowired?
- What distinguishes an interface from a class?
- Can you elaborate on Spring authentication mechanisms?
Meltwater
Programmer
Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Group Presentation
Interview formats
Presentation Group Behavioral
I started with a meet and greet at their Shoreditch office, basically to network and get noticed. They did a short presentation about Meltwater, then we talked to staff. They let us know the next day if we moved on. The next step was a group interview with about 12 others. The area director gave a more in-depth presentation about the company. Then, each of us had to give a quick three-minute intro about ourselves and something we're proud of. After everyone went, we had a coffee break, another networking chance. When we got back, we had to do a group presentation and a group debate. Finally, we had to give a short elevator pitch on something we're passionate about. The next stage was individual interviews, but I didn't make it that far.
Confirmed questions1 question
- Could you take three minutes to tell us about something you're proud of?
Meltwater Software Engineer Interview Questions
Quoted word for word from Meltwater interview reports.
“What distinguishes an interface from a class?”
Read reports →“How are configuration values managed within Spring?”
Read reports →“Can you explain linked lists?”
Read reports →“Can you elaborate on Spring authentication mechanisms?”
Read reports →“What are basic programming concepts?”
Read report →“What are the main data structures and algorithms?”
Read report →“What about search algorithms?”
Read report →“Could you discuss the advantages and disadvantages of using @Autowired?”
Read report →“How would you design a website for a fictional car rental company?”
Read report →Formats, difficulty and experience
Across all 11 Meltwater interview reports.