GoDaddy Software Engineer Interview Questions
& Process

Overall, the interviewers were great, but the process was super long and I didn't get an offer, so it took a lot of my time. The first round was with a recruiter who asked about salary expectations and gave a basic intro to the role, which felt more like they were trying to sell the job to me than an actual interview. Then there were two rounds with engineers. The second round involved a technical and coding task where we did a 25-minute coding question on Hackerrank (simple DSA) and a 35-minute interview. The third round was similar, with 35 minutes of coding and a 25-minute technical interview, also on Hackerrank (React question involving creating a form with basic validation). The fourth round was a 1-hour technical and behavioral interview with the manager I would be working with, mostly behavioral. Even though I thought I did really well, they didn't accept my application. They offered feedback if I wanted it, but they never sent it even after I emailed them. The people I interviewed with were professional and made the interviews comfortable, but I wish it didn't take so much of my time and was more reflective of the actual job. The behavioral part focused on decision-making and leadership, and I think I might have answered those questions too theoretically instead of how they wanted, emphasizing what I *would* do rather than what I *do*. I also think my extensive experience in smaller companies wasn't considered, which felt unfair. While I get they expect strong candidates, some things can be learned on the job. People from smaller companies often have a lot of experience and skills, but not having worked in larger teams shouldn't disqualify them, especially since working in smaller companies means developers usually communicate with all parts of the business.

I applied for a Software Engineering Internship at GoDaddy on their website. The interview process had three stages. First, there was an online coding test with two questions focused on data structures and logic. After that, I had a technical interview where they asked about Java, OOP, and some basic system design concepts. The final stage was with HR, discussing my resume, career aspirations, and availability. Everyone was nice and professional. The whole thing felt smooth and well-organized. I'd say it was moderately challenging.

Worst interview ever. First, there were 3 engineers for the technical interview, which felt excessive and like a red flag. The hiring manager initially mentioned an experience discussion, a coding part, and a system design part. However, the experience part had no questions or discussion. Instead, there were surprise, irrelevant, low-level Java questions about concepts like array lists and sets. They even asked how sets identify duplicates, and when I answered correctly, they didn't know the answer themselves and kept repeating the question. The system design interview didn't happen because I decided I didn't want to work with them. It was a horrible experience, and I don't recommend applying here.