Gsk Software Engineer interview typically runs 3 rounds: HR screening, hiring manager chat, technical/behavioral interview. Timeline is about 2-4 weeks, and the process is formal and structured.
$158K
Avg. Base Comp
$177K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
We've seen GSK lean toward a highly controlled, almost formal evaluation style, and that matters more than candidates expect. Multiple candidates described the experience as structured and somewhat robotic, with less room for natural back-and-forth than in many software interviews. That means the signal here is not charisma or improvisation; it’s whether you can present your work in a way that feels organized, credible, and easy to follow, even when the interviewer is steering the conversation tightly.
A recurring theme is that GSK wants evidence of real project ownership, not just abstract technical fluency. One candidate was asked to walk through a technical problem from university, while another had to explain how they handled a project issue and what they learned from it. We also saw broad, hypothetical questions about mistakes, conflict, and problem-solving, which suggests they care about how you reason through ambiguity and communicate under pressure. In practice, the strongest candidates are the ones who can make their experience legible without relying on the interviewer to connect the dots for them.
The other non-obvious pattern is the emphasis on presentation quality. One candidate had to prepare a statistical presentation in advance, and that format appears to carry real weight. For GSK, we’d treat clear structure and confident explanation as part of the technical bar itself, especially in a company where cross-functional communication is likely as important as engineering depth. Candidates who can connect their past work to business context, explain tradeoffs plainly, and stay composed in a formal setting tend to come through best.
Synthetized from 2 candidates 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 process felt more formal and a bit robotic than I expected, especially in the later stages. It started with a pre-interview screening where they asked about right-to-work details and the usual why GSK and why this role questions. After that, I had a 30-minute chat with the hiring manager, which was mostly conversational and felt like the easiest part of the process. The next round was much more structured: I had to prepare a 15-minute statistical presentation in advance, and then I went into a 1 hour 15 minute interview that mixed technical and behavioural questions.
What stood out most was how automated the whole thing felt. It wasn’t really a back-and-forth conversation, so I felt like the interview was judged more on what I said than on how naturally I could present myself. The technical part included a question about a technical problem I had worked on during university, so they did want to hear about real project experience rather than just theory. Overall it was a fairly standard but very controlled process, and I’d say the biggest thing to prepare for is being able to explain your past work clearly and confidently, especially in a presentation format.
Prep tip from this candidate
Be ready to give a polished 15-minute statistical presentation and to talk through a technical problem you worked on during university. Also prepare concise answers for why GSK and why this role, since those came up early in screening.
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
Describing a data project and its challenges
| Question | |
|---|---|
| Rider Discount | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Weighted Keys | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Last Transaction | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Brain Cancer Treatment Outcomes | |
| Always Excited Users | |
| Sum to Zero | |
| Total Spent on Products | |
| Flatten JSON | |
| Valid Anagram | |
| Cumulative Reset | |
| Digit Accumulator | |
| Search Linked List | |
| Time Difference | |
| Common Prefix | |
| Greatest Common Denominator | |
| Count Transactions | |
| Subscription Retention | |
| Possible Triangles | |
| Concurrent LLM Serving | |
| String Palindromes | |
| DDoS Attack Response |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with a pre-interview or short HR screening to confirm basic eligibility details such as right-to-work status and to cover standard motivation questions like why GSK and why this role. This stage is also used to get a high-level sense of your background before moving forward.
Next is a conversational 30-minute chat with the hiring manager. This round is described as the easiest part of the process and focuses on your background, interest in the role, and general fit.
Candidates then complete a structured virtual interview on Teams that is broad and scenario-based rather than deeply technical. Questions often cover self-introduction, handling mistakes or conflict, and reflecting on lessons learned from project challenges.
In the later stage, candidates prepare a 15-minute statistical presentation in advance and then discuss it in a longer interview that combines technical and behavioural questions. The technical portion may include explaining a real technical problem from university or past project work, with an emphasis on clear communication and structured answers.