Real, anonymous reports from people who interviewed for Software Engineer at GoDaddy, newest first and distilled into what to expect across the loop.
My interview journey felt very DSA-heavy and tightly focused on algorithm fundamentals. After an initial recruiter interaction, I was pulled into a technical sequence where the questions were resume-based, but the actual problem-solving was very much the center of gravity. I ended up getting grilled on topics like graphs, binary search, and even a question tied to generating or reasoning about a LinkedIn-style list.
My experience felt a bit off-target from the start. I had an interview path that included an OA, then a technical interview, and finally an HR conversation. The technical round was surprisingly informal and didn’t really test what I was expecting for a software engineering role.
Candidates can expect a strong emphasis on data structures and algorithms (DSA) during the technical coding interviews, often including live coding sessions where they must articulate their thought processes. The difficulty level is generally high, with a mix of algorithmic questions and practical coding tasks.
Several reports indicate that SQL questions are a significant part of the interview process, with candidates needing to demonstrate their understanding of database concepts and practical SQL skills, sometimes under pressure during technical rounds.
The interview process typically includes a behavioral round focused on leadership, decision-making, and teamwork, where candidates are expected to provide concrete examples from their past experiences rather than theoretical answers.
The overall interview process is described as structured, often starting with a recruiter call followed by multiple technical rounds, but candidates have noted that the pacing can vary, leading to long waits for feedback and decisions.
Candidates report a high level of difficulty throughout the interview process, with many expressing frustration over unclear expectations and the lack of feedback after interviews, which can lead to a feeling of uncertainty regarding their performance.
Some candidates reflected on the need for better preparation in specific areas such as SQL and system design, as well as clearer communication about role expectations and requirements early in the process to avoid misalignment.
