
YouGov Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at YouGov.
Software Engineer
I applied for a Python role with the Polish team. The process involved two interviews and a GitHub challenge. First, I spoke with a recruiter who gave me the lowdown on the company and the position, and answered my questions. They said they'd be in touch in two days, but I actually got a take-home challenge the very next day, with a week to complete it. After that, I had a discussion about the challenge with the tech team. The people I met were all really professional and friendly, and the recruiter was top-notch. I didn't end up getting an offer, but I'm planning to try again next year.
- Can you discuss your Python background?
- What's your total years of experience in software engineering?
- Walk me through your previous projects.
Software Engineer
I had an HR interview and then a code challenge. After the first interview, they sent me a GitHub repo to collaborate on. Once I finished the tasks there, they ghosted me for a month. In the end, I got a generic rejection email with no feedback.
- Could you perform a code review within GitHub?
- Please implement the suggested changes.
- Additionally, could you add a new feature?
Software Developer
I really liked the interview process. A UK-based HR person reached out on LinkedIn. They asked about my total experience, tech skills, current and expected salary increase, and why I was looking to switch jobs. The very next day, I got an email for a Skype interview with a Development Manager and a Director. It was a long interview, about 1.5 to 2 hours. It felt like they were testing my patience and interest. The manager focused on my past projects and asked technical questions. The director was more interested in my managerial skills, how I approach work, and my experience leading and mentoring teams. Honestly, those were the hardest managerial questions I've encountered, and the technical ones were tough but good. They alternated between technical and managerial questions, roughly 15 minutes each. It was more of a conversation than an interrogation, so it wasn't too draining. Afterward, HR said they'd be in touch. A few days later, HR emailed about my availability to join and offered me the role. I requested a week off after leaving my previous job before starting at YouGov because I was stressed, and they were understanding and agreed. Heads up: My interviews were all in one day, but I'm not sure if that's standard for everyone; it probably varies.
- Can you tell me about your overall years of experience?
- What are your technical skills?
- What is your current salary expectation and the hike you are looking for?
YouGov Software Engineer Interview Questions
Quoted word for word from YouGov interview reports.
“Could you describe closure and the call stack in JS?”
Read reports →“Can you explain what scope means in JavaScript?”
Read reports →“Additionally, could you add a new feature?”
Read reports →“Could you perform a code review within GitHub?”
Read reports →“What about databases?”
Read report →“How would you add features to a dummy project (without frameworks) adhering to clean code and SOLID principles?”
Read report →“Can you explain core Javascript concepts?”
Read report →“Can you discuss Node JS?”
Read report →“What makes you interested in YouGov?”
Read report →Formats, difficulty and experience
Across all 9 YouGov interview reports.