What to expect in a GSK Software Engineer interview: recruiter or HR screens, a team conversation, a prepared presentation, and technical and behavioral questions that draw on your real project work.
$155K
Avg. Base Comp
$177K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe a GSK Software Engineer interview that leans on your own work more than on puzzle-style questions. Reports start with a recruiter or HR call about your background, and one candidate was also asked why GSK and why this role. Expect to explain your past projects clearly, because several candidates say the questions kept returning to what they built and which tools they used. One graduate was asked about databases, code repositories and languages from academic projects, and another was asked about a technical problem solved at university.
Two candidates mention a prepared presentation. One prepared a 15-minute statistical talk and another presented a technology achievement to a panel, so have a short walkthrough ready that you can deliver without notes. The technical content varies by team. One candidate reports a roughly two-hour HackerRank assessment with three to four coding problems, followed by questions on B+ trees, data lakes versus data warehouses and query optimization. Another candidate had a 45-minute virtual interview that was mostly broad and hypothetical, covering a time something went wrong and what was learned.
Behavioral and fit questions appear in most reports, including teamwork, leadership preferences and motivation for GSK. Outcomes in the reports are mixed. Three candidates report offers and one reports no offer. Only one candidate gives a total duration, about two months. With few reports, treat the stages as examples rather than a fixed sequence, and confirm the format with your recruiter.
Synthesized from 4 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 Gsk process.
The whole process stretched over two months, which gave me time to prepare but also meant a lot of back-and-forth. I started with an online application, then moved into a screening call where they asked about my background and experience with specific technologies like Spark and cloud platforms. They wanted to understand what I'd actually built and whether I'd worked with the tools they use.
After the initial screening, I had a HackerRank assessment that lasted about two hours. It consisted of three to four coding problems, which tested algorithmic thinking rather than anything domain-specific. The time pressure was real, but nothing I hadn't seen in typical technical interviews. Following that, I had a discussion with a team leader about my past projects, how I approach problem-solving, and what the day-to-day expectations would be for the role.
Then came the on-site day. I was asked to prepare a presentation beforehand on a technology achievement I'd worked on, and I presented it in front of the interview panel. This was followed by deeper dives into technical fundamentals—questions like how B+ trees work, the differences between a data lake and a data warehouse, and my approach to query optimization. Alongside the technical material, there were plenty of behavioral questions: how I work in teams, my management style, whether I'd prefer to lead or collaborate as an individual contributor, and what drew me to GSK specifically.
What stood out was how much they cared about cultural fit. The questions weren't trying to trip me up; they were genuinely trying to understand if I'd thrive on their team and in their environment. The whole experience felt collaborative rather than adversarial, which made it easier to show my actual thinking rather than just reciting textbook answers.
Prep tip from this candidate
Be ready to discuss specific technologies like Spark and cloud platforms in relation to your actual experience, and prepare a clear presentation on a technical achievement you can walk through under interview conditions. Study foundational database concepts like B+ trees, data lakes vs. data warehouses, and query optimization strategies—these came up repeatedly and seem to be core to what they assess.
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 Gsk
Design a data warehouse for a new online retailer
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Rider Discount | |
| Moving Window | |
| Image Classification Pipeline | |
| Marketing Workflow Optimization | |
| Why Do You Want to Work With Us | |
| SFTP Pipeline | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Weighted Keys | |
| Cumulative Distribution | |
| Total Spent on Products | |
| P-value to a Layman | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Last Transaction | |
| Brain Cancer Treatment Outcomes | |
| Always Excited Users | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| 85% vs 82% | |
| Cumulative Reset | |
| Digit Accumulator | |
| Multi-Reaction | |
| Time Difference | |
| Search Linked List | |
| Common Prefix |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a first call with a recruiter or HR contact about their background, courses or projects, and technologies such as Spark and cloud platforms. One was asked right-to-work details and why GSK and why the role. Prepare a concise summary of your experience and your reasons for applying.
One candidate reports a 30-minute, mostly conversational chat with the hiring manager. Another describes a discussion with a team leader about past projects, problem-solving approach and day-to-day expectations. This may not be a separate step for every candidate, so be ready to explain your work in plain terms.
One candidate reports a HackerRank assessment of about two hours with three to four algorithmic coding problems. Other candidates do not mention one, so it may depend on the team or role. If you are sent one, practice timed problems in a typical technical-interview style.
Two candidates report preparing a presentation in advance. One gave a 15-minute statistical presentation, and another presented a technology achievement to a panel. Build a clear walkthrough of a project you know deeply, including your decisions and results, and rehearse it to time.
Final interviews are reported in different formats, including a 1 hour 15 minute mixed interview, a 45-minute Teams skills interview and an onsite with small groups of interviewers. Topics reported include university projects, B+ trees, data lakes versus warehouses, query optimization, handling mistakes, teamwork and leadership preference. Expect broad questions and prepare structured answers.
