Real, anonymous reports from people who interviewed for Software Engineer at ClickUp, newest first and distilled into what to expect across the loop.
I went through a pretty structured sequence that started with an HR conversation, then moved into a hiring-manager screen that combined live coding. After that first technical loop, I had a separate live coding exercise, followed by a system design session where the focus was on taking a new service and fitting it alongside existing systems. The system design part specifically emphasized how to decouple services when they had very different performance needs, and I remember being able to talk through tradeoffs rather than just “get the right answer.”
I had a pretty pleasant process overall, and it really started with how the company handled my time. First I talked with an internal recruiter, and then I moved to a second round with the Director of QA. Communication felt seamless throughout, and I got the sense that they appreciated the fact that I’d carved out time for them.
The interview process typically starts with a recruiter call, followed by a series of technical and behavioral interviews, often culminating in a system design discussion. The overall timeline can range from a few days to several weeks, with some candidates noting clear communication about the next steps throughout.
Candidates can expect multiple coding rounds, often including live coding exercises and practical problem-solving tasks that reflect real-world scenarios, such as data streaming or component design. The technical depth can vary, with some candidates feeling the bar was set high for both implementation and system-level tradeoffs.
System design interviews are a significant part of the process, emphasizing the ability to decouple services and discuss trade-offs in design decisions. Candidates noted that these sessions often require a collaborative approach and a clear understanding of existing systems.
Interviews often include discussions focused on cultural fit and values, where candidates are assessed on their alignment with the company's mission and work environment. The tone of these conversations tends to be constructive and friendly, aiming to gauge mutual fit rather than just technical skills.
Candidates generally reported a respectful and organized communication style throughout the process, with many appreciating timely updates and clarity on outcomes. However, some experienced abrupt or impersonal rejections, leading to frustration over the lack of detailed feedback.
Experiences varied widely among candidates, with some describing the process as supportive and engaging, while others felt it was chaotic or unwelcoming. This variability often hinged on the interviewers' attitudes and the clarity of expectations during technical assessments.
