
monday.com Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 92 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at monday.com.
Software Engineer
Shoutout to Selam for being proactive and keeping everything smooth and friendly. The interview process was well-structured and professionally managed. It included: initial recruiter screening, technical coding interviews, a system design round, and hiring manager/team discussions. The process was smooth overall, with clear communication at each stage. I had a very positive experience. The interviewers were friendly, professional, and knowledgeable. They created a comfortable environment and were open to discussions, making it feel collaborative. Visiting the office and meeting the team in person was a highlight, giving a great sense of the company culture. The recruiter was responsive and transparent, and the team was supportive. The offer process was smooth, flexible, and open to discussion; they were willing to revisit and improve the offer. Overall, a very strong interview experience with a great team and culture. The process was well-organized, and I felt respected.
- Were there questions related to monday.com features and product orientation?
Software Engineer
I interviewed for this job on Monday in Tel Aviv Nov 24, and the whole process took about 3 weeks. It was a really good and chill experience overall! I liked that the HR actually called me after each interview to give me feedback instead of just sending a generic email. It started with a quick HR call, then a coding interview where I got a question about their product. A few days later, HR called and said the interviewer liked my problem-solving but my coding skills were just okay, so they had me do another coding question in a programming language I'm more comfortable with, and I nailed that one. After that, we had a "feature design" interview, which I didn't pass, but it was still a positive experience. The HR and interviewers were all super nice and made me feel like they were rooting for me to get the job.
- How would you implement the notification system for user/team mentions in posts, given a set of blackbox functions? The task involves organizing user and team data and efficiently retrieving it for sending notifications.
- Could you implement the "boards" feature for their system?
- Can you design the "drag and drop" functionality for a board, specifically how dragging and dropping a line would rearrange the board?
Software Engineering Team Lead
The interview process involved a phone interview with a recruiter, followed by an end-to-end interview via zoom, a system design interview via zoom, a management interview via zoom, and finally an HR interview on site. All interviews for the technical roles on Monday are identical except for the coding interview, which was not part of my process. I'm sharing this because I noticed a lot of confusion about which questions are asked in which interview phase at Monday.com. I'm assuming you've seen some interview questions here and noticed that about 3-4 questions are asked in all interviews, so let me clarify. First, I recommend creating an account, playing with the app, and understanding the concept of tasks and boards.
- Regarding the 'Coding' interview, it's about the mentions notification system, ensuring exactly one notification is sent without duplicates for each mentioned user. I wasn't asked this, but I know it matches this interview phase.
- For the 'End2End' interview, you'll be asked about implementing task sorting in a list. Imagine a list of tasks sorted by creation date, displayed on Monday.com (like a kanban list). How would you handle changing a task's position in the order? This means being able to move a task between others, changing the order, and having it saved. You don't need to worry about the UI part (this was for a backend role, so it might be different for a UI role).
- The 'System design and architecture' interview involves designing Monday.com's 'automations' feature. This means devising a system for users to set up automatic rules based on board events. For instance, if a task is completed, send an email to the creator. Their system includes a trigger (what caused the event, e.g., task completion), a condition (rules for tasks meeting specific criteria), and an action (e.g., sending an email).
monday.com Software Engineer Interview Questions
Quoted word for word from monday.com interview reports.
“Given the User database schema and a function to extract mentions from messages, implement the notifyUsersFromUpdate function to process an update message, identify mentions, and send notifications to relevant users.”
Read reports →“Given a dictionary of users and their group IDs, write a code function to tag distinct users and users within specified input groups based on a list of user IDs and group IDs.”
Read reports →“Given a list of users and their group participations, and a list of groups to notify, implement a system to notify all users only once for each group they are in.”
Read reports →“Given a list of groups and users belonging to those groups, write code to send notifications to the specified users and groups, ensuring no duplicate notifications are sent even if a user is in multiple groups.”
Read reports →“Could you build a crawler that recursively fetches all links starting from a specific HTML? This means if the HTML links to www.test.com, you should grab that link and also all links found on www.test.com.”
Read report →“If a message is sent to a consumer that fails to acknowledge it, what are the implications for subsequent interactions, specifically concerning duplicate processing?”
Read report →“Can you write a program, in any language, to scrape a given link up to [n] levels deep? Output is not required.”
Read report →“How can you send an email to a group of people and users, ensuring no duplicate emails are sent?”
Read report →“Given a data structure for users and teams, and black-box functions like getUsers(), implement notifyUsers(userId, msg) and notification(msg) to send messages to all relevant recipients, ensuring efficiency for millions of users and teams, avoiding duplicate notifications.”
Read report →Formats, difficulty and experience
Across all 92 monday.com interview reports.