HR phone screening -> 1 hour with a hiring GL -> design interview (failed) -> e2e feature interview -> coding interview -> management interview -> HR interview
It took a week for HR to schedule a tech interview after the interview with a GL which also was postponed a few days so the process took a lot of time though failed early.
Failed on design interview, got feedback that I had the wrong focus on smaller details rather than creating a system though I rechecked if I got the scope and meaning of every question they asked (which were pretty low-level btw)
Given the main Monday.com boards product (similar to JIRA) working in prod, you'd like to add Automations part (similar to Automations in JIRA). Which interface will you use for those parts to communicate and why? What will you take into consideration from scale perspective? How will you choose a DB? How will you manage and handle exceptions? Which metrics/ KPIs will you look onto when deploying to prod?
The following metrics were computed from 1 interview experience for the Monday.com Backend Foundations Team Lead role in Tel Aviv-Yafo, Israel.
Monday.com's interview process for their Backend Foundations Team Lead roles in Tel Aviv-Yafo, Israel is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Monday.com's Backend Foundations Team Lead interview process in Tel Aviv-Yafo, Israel.