GoDaddy Interview Questions
& Process

My interview experience at GoDaddy for the Email Copywriter role involved five stages. It started with a 30-minute chat with the Talent Acquisition Specialist, followed by a 45-minute interview with the Hiring Manager. Then, there was a 45-minute interview with the Lead Writer, another 45-minute one with the Senior Art Director, and finally, a 45-minute interview with the Associate Creative Director. Overall, the conversations were good, though five rounds felt like a lot for this type of position. Each person I spoke with gave off a positive vibe, and it seemed like I fit their needs for the role. During the last interview, the Associate Creative Director said I'd be a 'great fit,' which felt a bit strange since no decision had been made. After the final interview on Monday, the recruiter emailed Tuesday evening to say they needed a few more days to decide and asked me to follow GoDaddy on social media to 'experience the #GoDaddyLife,' which I found odd. A week later, still no word, so I followed up, and the recruiter had no update. I wish the decision-making process was faster and that I'd been kept informed about the delay. It took two weeks for a response, which came as a phone call from the recruiter. I think it's better to call successful candidates and email unsuccessful ones, especially in the UK where a phone call usually means a job offer. I was disappointed and confused, especially with no feedback after being told I was a 'great fit' by the Creative Director.

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.

The process was recruiter to team screen with 2 technical interviews and an interview with the hiring manager, oddly, it came last. One bit of feedback - this hiring team does "exercises". In my experience, the exercises are unstructured, not particularly collaborative, and are not defined before the interview occurs. One of the two technical interviews was literally the worst interview that I have ever had in my 20+ years as a security engineer. I recommend that GoDaddy take a good look at the methods used to interview. If the interviewer does not have a structured exercise to share, or is not a good communicator, then do something different please. At the VERY least, you should provide an example exercise before the interview so that the candidate has expectations set. Given GoDaddy's recent exposure in the news, you would think that they would want all of their security processes, including hiring, to be clear, concise, and beyond reproach.

The process starts with resume shortlisting, followed by two technical interview rounds. These interviews aim to check your understanding of the domain, how well you can think analytically, and your past project experience. Senior Analysts, Data Scientists, or Product Managers will conduct these. Expect to talk about your previous work, particularly in data or product analytics. You might get scenario questions like figuring out how to measure a new feature's success, spotting fraud in transactions, or how you'd handle cleaning raw data. They'll also likely ask about statistics and probability concepts such as mean, median, variance, A/B testing, and correlation versus causation. Familiarity with tools like SQL, Python, Tableau, Excel, and Google Analytics is also important.