Gsk Data Engineer Interview Guide

Our candidates report that GSK is looking for someone who can hold the whole data stack in their head, not just one slice of it. The strongest signal in the experience we saw was the system design discussion around an end-to-end unstructured data pipeline from FTP sources: that’s the kind of prompt where they seem to care less about buzzwords and more about whether you can reason through ingestion, processing, and operational tradeoffs in a healthcare context. The repeated appearance of image, PDF, and SFTP pipeline questions suggests they want engineers who are comfortable with messy, real-world data rather than tidy textbook examples.

A recurring theme is that the interviewers may change the problem midstream, and candidates who stayed rigid seemed to struggle. In one round, the discussion moved from images to PDFs, then to Hadoop-to-cloud migration, then into fact and dimension tables, and finally into Python debugging. That tells us GSK is probably testing adaptability as much as technical depth. We’ve also seen Spark behavior questions tied to uneven file sizes, which hints that they care about practical performance awareness, not just architecture diagrams.

What makes or breaks candidates here is the ability to connect domains quickly: storage, modeling, migration, and code-level reasoning. The people who do best are the ones who can keep their answer coherent even when the interviewer pivots, and who can explain why a design choice still holds when the data shape changes. In other words, GSK seems to value broad, composable engineering judgment over a narrow specialty.