Astrazeneca Software Engineer interview typically runs 6 rounds: HR screening, hiring manager screening, three technical interviews, and a final values-based round. It usually takes about eight weeks and is organized and conversational.
$108K
Avg. Base Comp
$150K
Avg. Total Comp
5-6
Typical Rounds
8 weeks
Process Length
We've seen AstraZeneca lean toward candidates who can talk credibly about real systems, not just solve puzzles on a whiteboard. In the experience we reviewed, the strongest signal was hands-on familiarity with the stack they care about: Kubernetes, backend fundamentals, and the ability to explain why a design choice was made. The technical conversations were described as conversational and grounded in prior work, which tells us the bar is less about memorized algorithms and more about whether you can reason through engineering tradeoffs in a regulated, applied environment.
A recurring theme is that AstraZeneca seems to value breadth across adjacent domains. One candidate moved through Cheminformatics, Software Engineering, and DevOps topics, and even a presentation round that turned into a deeper engineering discussion. That pattern suggests they’re looking for people who can connect the dots between systems, infrastructure, and the business context of scientific software. We also noticed that the behavioral side wasn’t generic; questions about obstacles with a group and how they were resolved point to an emphasis on collaboration under pressure and clear ownership when things get messy.
The non-obvious make-or-break factor here is communication quality. Our candidates report that being able to defend past decisions, walk through project details cleanly, and answer follow-up questions without drifting mattered a lot. Even the lighter coding questions were framed in a practical way, so the real test was whether you could stay precise while discussing your own work. For candidates with relevant experience, that makes the process very manageable; for everyone else, it can feel broad and unforgiving if your examples are thin.
Synthetized from 1 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 Astrazeneca process.
The process was fairly long and stretched over about eight weeks. It started with two screening conversations, first with HR and then with the hiring manager, both over Microsoft Teams. After that I went through three technical interviews and then a final values-based round. The technical interviews were split across Cheminformatics, Software Engineering, and DevOps, which made the process feel broader than a typical pure coding interview.
What stood out to me was that the technical rounds were conversational rather than leetcode-heavy. There was sometimes a bit of code or other material to comment on, but it was more about how I think through software engineering problems and how I’ve handled real work before. In the principal engineer conversation, we talked through my previous experience, Kubernetes, and general backend knowledge. I also got standard behavioral questions, including one about a time I ran into obstacles while working with a group and how I resolved it. Another round asked for a presentation and then followed up with software engineering questions, so it helped to be ready to explain past projects clearly and defend design choices.
I wouldn’t call it easy, but it was very manageable if you had hands-on experience with the stack they care about and could speak comfortably about your work. There were also some basic data structures and language-specific questions, including a simple string manipulation question in Python with indexing. Overall, the process felt organized and professional, with room to ask questions in each round. I ended up receiving an offer, and my main takeaway was that preparation should focus more on practical engineering experience, Kubernetes, and being able to discuss your past work and decisions clearly than on grinding algorithm problems.
Prep tip from this candidate
Be ready to discuss Kubernetes and your past engineering work in detail, since those came up directly in the screening and principal engineer rounds. Also prepare for a presentation-style technical interview and a few basic Python or Java questions, including simple string indexing/manipulation.
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 Astrazeneca
Write a function to return any subset of the input list where the elements sum to zero and that does not contain the number 0.
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Digit Accumulator | |
| Common Prefix | |
| Greatest Common Denominator | |
| Mapping Nicknames | |
| Client Solution Pushback | |
| Maximal Substring | |
| Automated Labeling | |
| 2nd Highest Salary | |
| Weighted Keys | |
| Monthly Customer Report | |
| Cumulative Distribution | |
| P-value to a Layman | |
| Last Transaction | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Always Excited Users | |
| Brain Cancer Treatment Outcomes | |
| Total Spent on Products | |
| Flatten JSON | |
| Valid Anagram | |
| Cumulative Reset | |
| Rider Discount | |
| Search Linked List | |
| Time Difference | |
| Count Transactions | |
| Subscription Retention | |
| Possible Triangles | |
| Concurrent LLM Serving |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with an initial screening conversation with HR over Microsoft Teams. This stage is used to cover background, motivation, and basic fit for the Software Engineer role before moving forward.
Next is a screening conversation with the hiring manager, also conducted over Microsoft Teams. This round focuses on your previous experience, how you approach software engineering problems, and whether your background aligns with the team’s needs.
Candidates then go through three technical interviews covering Cheminformatics, Software Engineering, and DevOps. These rounds are conversational rather than leetcode-heavy, with discussion of practical engineering experience, Kubernetes, backend knowledge, basic data structures, and some language-specific questions such as Python string manipulation.
One of the technical rounds includes a presentation followed by software engineering questions. You should be prepared to explain past projects clearly, defend design choices, and discuss how you handled real-world engineering work.
The final round is a values-based interview with behavioral questions. Expect prompts about teamwork, obstacles you faced in a group setting, and how you resolved them, along with room to ask questions at the end.