MDA Software Engineer interview with basic Python and disrupted onsite

MDA·Software Engineer·Reported Aug 2026
Technical ScreenOnsiteSenior+OfferHard

I began with a short expectation-setting call that felt vague, more like a quick check than a senior-level conversation. I discussed my experience and answered one basic Python question about a list versus a tuple. There was little follow-up about what the role required or what they expected at that level.

The next day I went to the Farnborough office for an onsite. The meeting felt chaotic: the lead took phone calls several times and spoke another language while I was reviewing my answers without stepping out. The assessment was a sheet of fundamentals, including inheritance, polymorphism, encapsulation, what init does, mutable versus immutable types, and a simple missing-number puzzle. I finished everything, but it did not connect to the software-validation or test-engineering work the title implied.

The process felt unprofessional and disorganized. I expected senior-role depth and left disappointed that the interview was not designed for the work.

Location: United Kingdom. Overall feedback: neutral. Offer status: got offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
MDA
Role
Software Engineer
Level
Senior+
Rounds
Technical Screen → Onsite
Outcome
Offer
Difficulty
Hard
Date
Reported Aug 2026

Real MDA interview experiences

First-hand reports from MDA candidates — the rounds, the questions they were asked, and how it went.

All 6 MDA interview experiences