Merkle Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 29 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Merkle.
Merkle
Software Engineer
Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Behavioral Technical
1st with recruiter, 2nd given a home-test, 3rd with final with team mostly behavioral. Bad thing I made the test through a 3rd party company and they never received that. I spend 3-4 days fixing very bad code, I did very good job and none checked it or talk about it.
Confirmed questions1 question
- What are your biggest weaknesses?
Merkle
Senior Software Developer
Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation Onsite Background check Offer
Interview formats
Technical Behavioral Presentation
The whole process makes you realize the fact that they know what they want and take their time to see if you fit the bill. The interview process is very rigorous. Had three phone interviews and one in person interview. Had to make one in person presentation. Technical Peers and seniors interviewed first and then the boss and his boss (I think). Very professional process and very organized prescheduled interviews with timeslots and conference setups. Everybody that interviewed me was there either in person or through a conference for the presentation. Got the feedback within a week.
Confirmed questions3 questions
- Technical folks asked technical questions, in relation to the platform you used and your level of experience.
- Was presented a problem and asked to solve it.
- Managers asked personality assessment questions.
Merkle
Software Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Behavioral Technical Coding
It was a 4 step process. First, a phone screen with HR/Talent. They asked basic personality questions and if I met the basic qualifications. Second, I had to do a code assessment in any language I wanted. Third, an in-person technical interview with two people, likely team leads for the project. They reviewed my resume and experience, and I had 2-4 whiteboard questions. Fourth, another in-person technical interview with two senior-level people, associate director level in engineering. It was similar to the first in-person, just with different whiteboard questions. If everything went well, I would get an offer. The whole process took about 3 weeks. No flexibility on start date; due to the company merge, all start dates are on Mondays.
Confirmed questions2 questions
- Can you write a method to divide two numbers without using division or modulus?
- What's your experience with the Agile process?
Merkle Software Engineer Interview Questions
Quoted word for word from Merkle interview reports.
“Can you write a method to divide two numbers without using division or modulus?”
Read reports →“Could you describe the differences between Java and JavaScript?”
Read reports →“Can you describe a method to divide two numbers without utilizing the division operator?”
Read reports →“Regarding academic projects on Algorithms, what is the need for graph algorithms?”
Read reports →“Could you explain the React lifecycle concerning hooks?”
Read report →“How would you forecast sales for the month, and what elements should be taken into account?”
Read report →“What tools do you use for testing?”
Read report →“What's your understanding of general testing concepts and tools like coverage, Mockito, JUnit, Testcontainers, Jenkins, and Selenium automation?”
Read report →“Can you answer some advanced questions about data structures and algorithms?”
Read report →Formats, difficulty and experience
Across all 29 Merkle interview reports.