What to expect interviewing for a Unilever software engineer role: a recruiter phone screen, an in-person technical round with SQL and React questions, and slow post-interview communication, per one candidate report.
$110K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one candidate who reported a Unilever Software Engineer interview describes a short process. It began with a recruiter phone screen, followed by an in-person technical interview at a Unilever office. The candidate was asked to travel about an hour for it, so confirm the location and format with your recruiter early.
The technical questions were SQL and React. The candidate called them average, neither especially tricky nor easy. A sensible way to prepare is to refresh query writing and the fundamentals of building React components, and to be ready to talk through your reasoning.
The larger frustration was communication. The candidate found the recruiter unprofessional, followed up a couple of times without a reply, and learned about three months later through a Workday notification that the role had been filled. The outcome was no offer. If you are in a similar position, keep your own record of dates and contacts, and ask at the end of each stage what the next step and timeline are.
A report from a Unilever internship, a different program, adds some context. That candidate described behavioral questions such as why Unilever and what they knew about its products, asked in a scenario format. They also reported questions on automation and technology contributions rather than algorithm puzzles. It is reasonable to prepare a clear "why Unilever" answer alongside your technical review.
Evidence for this exact role is limited to a single report, so use it as a starting point and not as a fixed format.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Unilever process.
I started with an online HR screening that was pretty straightforward — they sent me the link ahead of time, which gave me a chance to prepare. The preliminary round felt well-organized and I went through the questions about why I wanted to join Unilever without too much friction. But then things shifted. The subsequent rounds felt rushed and impersonal. The interviewers seemed more focused on getting through their candidate checklist than actually understanding who I was or what I could bring to the role. They asked the standard strength-and-weakness questions, but there was no real depth to the conversation. Job responsibilities and the actual profile of the role weren't discussed thoroughly — I had a lot of questions that never got answered. It was clear they weren't being particularly thoughtful in their approach. The whole process had this checklist vibe that made it feel less like they were seriously evaluating me and more like they were just trying to fill slots. I wasn't surprised when I didn't move forward.
Prep tip from this candidate
Come prepared with specific research on Unilever's marketing brands and sectors — interviewers expect you to know what the company actually does. Also, push back thoughtfully if the conversation feels surface-level; ask clarifying questions about the role and team to show genuine interest and force more substantive dialogue.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Unilever
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| Simple Explanations | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Monthly Customer Report | |
| Customer Orders | |
| Random SQL Sample | |
| Top 3 Users | |
| Over-Budget Projects | |
| Bagging vs Boosting | |
| Cumulative Distribution | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Average Order Value | |
| Normalize Grades | |
| Rolling Average Steps | |
| Precision and Recall | |
| Cumulative Sales Since Last Restocking | |
| Valid Anagram | |
| Monthly Product Sales | |
| Cumulative Reset | |
| Black Friday Shopping Spree | |
| Max Quantity | |
| Total Transactions | |
| Common Prefix | |
| KNN From Scratch | |
| ATM Robbery | |
| Loan Model |
Synthesized from candidate reports. Individual experiences may vary.
The candidate who interviewed for the Software Engineer role reports the process opening with a recruiter phone screen, which they described as straightforward. Applicants may want to prepare a short background summary and clarify the role, location and next steps on this call.
The same candidate was invited to an in-person technical interview at a Unilever office, roughly an hour's drive away. They report SQL questions and a few React questions that were neither especially hard nor easy. Reviewing both areas and rehearsing explanations of your approach is a reasonable way to prepare.
After the interview, this candidate followed up a couple of times and heard nothing back. About three months later a Workday notification said the position had been filled, and the outcome was no offer. Applicants may want to ask about timing at the end of the interview and keep records of their communications.
