Why General Dynamics? A 4-Part Answer That Sounds Genuine

What the interviewer is really asking

On the surface, 'Why do you want to work for General Dynamics?' is a simple motivation question. In practice, interviewers use it to check three things: have you done real research, does your reason hold up under follow-up questions, and are you likely to stay and perform once you've joined.

General Dynamics is a large aerospace and defence company. Its work is generally described in four broad areas: aerospace, marine systems, combat systems, and technologies (which includes IT and mission systems). Because the business is so varied, 'I like big, innovative companies' tells the interviewer almost nothing. A strong answer shows you know which part of the business you're applying to and why it matters to you.

Do your research before you hit record

You don't need insider knowledge, and you shouldn't pretend to have any. Public sources are enough: the company's website, its annual report, press releases, and the job description itself. Spend 30 to 45 minutes on the following:

• The specific business unit or site you're applying to, and what it builds, maintains or delivers.
• One or two recent public programmes, products or announcements relevant to that unit. Check that they are current before you cite them.
• The language of the job description: which skills, tools and responsibilities are repeated?
• Any requirements such as security clearance, nationality or eligibility checks, so your answer doesn't clash with them.
• Your own non-negotiables: what draws you to this kind of work, and what you'd want from your first two years?

A four-part structure for your answer

Aim for 60 to 90 seconds. Generic answers tend to be all company praise or all personal ambition. The strongest answers connect the two in this order:

• 1. The company hook (10-15 seconds): one specific thing about General Dynamics or your target unit that interests you, such as the type of engineering, the scale of the programmes, or the long-term nature of the work.
• 2. Your personal link (20-30 seconds): a short STAR-style story showing where that interest comes from. Give the Situation and Task briefly, then spend more time on your Action and Result.
• 3. Role fit (15-20 seconds): how your skills match what the job description asks for.
• 4. What you'll contribute and learn (10 seconds): a forward-looking close that shows you intend to add value, not just collect a title.

Worked example: graduate engineering role

The example below is illustrative. Replace the details with your own experience, and don't copy it word for word.

'What draws me to General Dynamics is the chance to work on complex engineered systems that have to perform reliably for decades, which is why the marine systems and combat systems work in particular interests me. (Company hook.) That interest started in my final-year project, where our team had to design a lightweight bracket that met a strict load specification, and we were two weeks behind (Situation). I was responsible for the stress analysis and for making sure our testing evidence was good enough to defend the design (Task). I set up a simple test plan, ran the simulations, found that our first design failed at one joint, and redesigned it with a supervisor's feedback, documenting every change (Action). The final design passed our load test with margin to spare, and we received a first-class mark for the project, with the examiners singling out our documentation (Result). (Personal link.) That taught me that I enjoy the rigour and accountability of engineering where the details really matter, and the graduate role's emphasis on design verification and teamwork is exactly where I want to build my skills. (Role fit.) I'd like to contribute carefully checked work from day one, and learn from engineers who've delivered long programmes. (Contribution.)'

Notice what this answer does: it names a specific interest, backs it with evidence rather than adjectives, and ties directly to the role.

Handling the defence question honestly

Because General Dynamics is a defence contractor, some interviewers may probe how you feel about working in the sector. Don't dodge it, and don't give a rehearsed slogan. You don't need to make a political speech, but you should have a sincere, considered position you can state calmly.

Honest angles might include pride in the engineering challenge, interest in the role of technology in national security and safety, or a belief that capable, ethical people should be part of the industry. If aspects of defence work give you pause, it is better to consider that before the interview and decide whether this is the right employer than to say something you don't believe. If you can't give a truthful answer comfortably, that's useful information for you.

Do and don't: common mistakes

Small differences in phrasing change how credible you sound.

• Don't: 'It's a huge, well-known company with great career opportunities.' Do: 'I'm interested in the long-lifecycle engineering on programmes like the ones in your marine business, because I like work where reliability is critical.'
• Don't: recite the 'About us' page. Do: pick one fact and explain why it matters to you.
• Don't: focus only on salary, brand or benefits. Do: lead with the work, and mention growth or stability as secondary points.
• Don't: claim to know internal culture or how the company hires. Do: stick to what's public and say what you hope to learn.
• Don't: go over two minutes in a timed video interview. Do: rehearse until 75 seconds feels natural.

Practising for a one-way video interview

In a one-way video interview you get a short preparation window, one attempt or very few, and no friendly nods to guide you. Write your four-part answer as bullet points (not a script), then practise speaking it aloud against a timer. A tool like ScreenReady lets you record timed answers on camera and review AI feedback on structure and clarity, which helps you spot rambling or a missing result.

Finally, prepare two or three flexible STAR stories that can also answer competency questions about teamwork, problem-solving and attention to detail. The same stories that make your motivation answer believable will carry you through the rest of the interview.