Merge Software Engineer Interview Experience — Data Class Design Then a 3-Level Org Chart Problem, Rejected

Merge·Software Engineer·Oct 2026
Technical ScreenRejectedmedium

The questions were quite different from the earlier interview reports. The difficulty isn't high, but you need to write code fast. The interview was split into two parts.

Part 1: I was first given a set of API return values and asked to design a common data class to store that data. This part took about 20-25 minutes, and they also asked a few simple questions about DB and system design.

Part 2: The remaining ~25 minutes was a 3-level problem. I was given a company's employee list: [(id, title, reports_to)], where the head of the company has reports_to = None.

Level 1: find how many orgs the company has.

Level 2: print the employees level by level.

Level 3: given two employees, find their first common report.

The problems aren't hard, but time is very tight. I got to level 3 and had a small bug that I didn't have time to fix before time ran out. A few days later I got the rejection email. Good luck everyone.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Merge
Role
Software Engineer
Rounds
Technical Screen
Outcome
Rejected
Difficulty
medium
Interview date
Oct 2026
Questions from this interview
2 questions

Real Merge interview experiences

First-hand reports from Merge candidates — the rounds, the questions they were asked, and how it went.

All 6 Merge interview experiences