cswork / libraryOpen practice workspace

Interview guides · Northrop Grumman

Northrop Grumman Software Engineer Interview Guide

Northrop Grumman Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Northrop Grumman, you develop critical software systems that support national security, aerospace exploration, and defense technology. From flight control algorithms and radar processing pipelines to advanced modeling and simulation environments, your code operates on platforms where high reliability and real-time performance are paramount. You will build software that powers autonomous systems, satellite communications, cyber defense frameworks, and multi-domain command-and-control architectures. The impact of your work extends across air, land, sea, space, and cyber domains. Unlike consumer software development, engineering at Northrop Grumman involves complex, integrated hardware-software ecosystems with stringent safety, security, and performance constraints.

This guide is scoped to a Software Engineer candidate at Northrop Grumman.

Focus areas

  • Behavioral Interviewing (STAR Method)
  • Resume-Based Technical Communication
  • SPC (Statistical Process Control)

The Northrop Grumman interview process

Northrop Grumman candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screen

Initial screening to verify basic qualifications, citizenship status, and clearance eligibility.

What to demonstrate

  • Initial screening to verify basic qualifications, citizenship status, and clearance eligibility
  • Depth in Behavioral Interviewing (STAR Method)

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Hiring Manager Interview

Discussion with the hiring manager to assess technical background and program alignment.

What to demonstrate

  • Discussion with the hiring manager to assess technical background and program alignment
  • Depth in Behavioral Interviewing (STAR Method)

How to prepare

  • Prepare two projects you led end to end, each with the decision you owned and what it cost.
  • Have three questions about the team's roadmap and how success is measured in the first six months.

Panel Interview

In-depth discussions with multiple engineers and managers focusing on past projects and technical decision-making.

What to demonstrate

  • In-depth discussions with multiple engineers and managers focusing on past projects and technical decision-making
  • Depth in Behavioral Interviewing (STAR Method)

How to prepare

  • Answer aloud and timed: How do you manage competing priorities when working under tight program deadlines?
  • Answer aloud and timed: What are the primary principles of Object-Oriented Programming, and how have you applied them in your projects?

Background Check

Post-offer process involving background checks and clearance processing, which can be lengthy.

What to demonstrate

  • Post-offer process involving background checks and clearance processing, which can be lengthy
  • Depth in Behavioral Interviewing (STAR Method)

How to prepare

  • Answer aloud and timed: Explain the difference between the stack and the heap in memory management.
  • Answer aloud and timed: How does a linked list differ from an array in memory, and what are the trade-offs in terms of lookup and insertion time?

Where candidates lose points

Review every bullet point on your resume thoroughly before your interview

Interviewers at Northrop Grumman ask detailed follow-up questions regarding the exact tools, architectures, and individual contributions mentioned on your resume.

Master the STAR Method

Prepare 4 to 6 detailed scenario stories from school or past employment covering technical failures, team conflicts, tight deadlines, and complex debugging achievements.

Emphasize Your Personal Contribution

When describing group projects, clearly differentiate what you built versus what the team completed by consistently framing responses with "I designed," "I implemented," or "I resolved."

Brush Up on Language Fundamentals

Be prepared to explain basic concepts in C++ or Java, such as dynamic memory, object-oriented pillars, polymorphism, and basic data structure trade-offs.

Questions & practice

Explain the difference between the stack and the heap in memory management.

Medium · Core Computer Science & OOP Fundamentals

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

How does a linked list differ from an array in memory, and what are the trade-offs in terms of lookup and inse

Medium · Core Computer Science & OOP Fundamentals

How does a linked list differ from an array in memory, and what are the trade-offs in terms of lookup and insertion time?

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Can you explain the difference between processes and threads, and how synchronization is handled in multi-thre

Medium · Core Computer Science & OOP Fundamentals

Can you explain the difference between processes and threads, and how synchronization is handled in multi-threaded software?

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Keep soft-deleted accounts from blocking re-registration

Easy · soft delete · unique constraints · engine differences

app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.

Approach

  1. Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
  2. Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
  3. For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
  4. State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.

Follow-up

  • A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
  • How do you honour an erasure request while resource_revision.actor_user_id still references this table?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.

Approach

  1. Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
  2. Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
  3. Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
  4. Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.

Follow-up

  • Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
  • Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?

What are the primary principles of Object-Oriented Programming, and how have you applied them in your projects

Medium · Core Computer Science & OOP Fundamentals

What are the primary principles of Object-Oriented Programming, and how have you applied them in your projects?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Describe how you would approach testing and verifying a software module for a mission-critical platform.

Medium · Systems Engineering & Architecture Conce

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

What experience do you have with systems engineering models, such as the Systems Engineering V-model or Model-

Medium · Systems Engineering & Architecture Conce

What experience do you have with systems engineering models, such as the Systems Engineering V-model or Model-Based Systems Engineering (MBSE)?

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

How do you ensure software maintainability and readability when contributing to a long-term codebase?

Medium · Systems Engineering & Architecture Conce

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Describe a project where you integrated software with hardware components or hardware simulators.

Medium · Systems Engineering & Architecture Conce

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

What is state machine architecture, and where would you implement a finite state machine in software?

Medium · Systems Engineering & Architecture Conce

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Walk me through the architecture of a major project listed on your resume.

Medium · Resume & Technical Deep Dives

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

What specific programming language features did you utilize in your capstone or prior job experience, and why?

Medium · Resume & Technical Deep Dives

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How did you determine which data structure or design pattern to select for your past software projects?

Medium · Resume & Technical Deep Dives

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What was your personal contribution to the key deliverables on your previous team?

Medium · Resume & Technical Deep Dives

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What is the concept of memory leaks, and how do you prevent them when writing code in C or C++?

Medium · Core Computer Science & OOP Fundamentals

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Describe a bug you encountered that was difficult to trace. What tools and methods did you use to debug it?

Medium · Resume & Technical Deep Dives

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Northrop Grumman candidates report.

Day 1 — Map the Northrop Grumman loop

  • Write out the reported sequence: Recruiter Screen, Hiring Manager Interview, Panel Interview, Background Check.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work Behavioral Interviewing (STAR Method)

  • Spend the session on Behavioral Interviewing (STAR Method), which Northrop Grumman candidates report being tested on.
  • Write one worked example in Behavioral Interviewing (STAR Method) and time yourself on it.

Deliverable: One timed worked example in Behavioral Interviewing (STAR Method).

Day 3 — Work Resume-Based Technical Communication

  • Spend the session on Resume-Based Technical Communication, which Northrop Grumman candidates report being tested on.
  • Write one worked example in Resume-Based Technical Communication and time yourself on it.

Deliverable: One timed worked example in Resume-Based Technical Communication.

Day 4 — Work SPC (Statistical Process Control)

  • Spend the session on SPC (Statistical Process Control), which Northrop Grumman candidates report being tested on.
  • Write one worked example in SPC (Statistical Process Control) and time yourself on it.

Deliverable: One timed worked example in SPC (Statistical Process Control).

Day 5 — Answer out loud: Behavioral & Team Dynamics

  • Answer aloud, timed: Tell me about a time you faced a significant technical challenge on a team project and how you resolved it.
  • Answer aloud, timed: Describe a situation where you had to deal with a non-performing or difficult teammate. What steps did you take?

Deliverable: Spoken answers to 2 reported Behavioral & Team Dynamics question(s), under time.

Day 6 — Answer out loud: Core Computer Science & OOP Fundamentals

  • Answer aloud, timed: What are the primary principles of Object-Oriented Programming, and how have you applied them in your projects?
  • Answer aloud, timed: Explain the difference between the stack and the heap in memory management.

Deliverable: Spoken answers to 2 reported Core Computer Science & OOP Fundamentals question(s), under time.

Day 7 — Answer out loud: Systems Engineering & Architecture Concepts

  • Answer aloud, timed: Describe how you would approach testing and verifying a software module for a mission-critical platform.
  • Answer aloud, timed: What experience do you have with systems engineering models, such as the Systems Engineering V-model or Model-Based Systems Engineering (MBSE)?

Deliverable: Spoken answers to 2 reported Systems Engineering & Architecture Concepts question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Tell me about a time you faced a significant technical challenge on a team project and how you resolved it.

Medium · Behavioral & Team Dynamics

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a situation where you had to deal with a non-performing or difficult teammate. What steps did you tak

Medium · Behavioral & Team Dynamics

Describe a situation where you had to deal with a non-performing or difficult teammate. What steps did you take?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Can you share an example of a time when a project or deliverable failed to meet expectations? What did you lea

Medium · Behavioral & Team Dynamics

Can you share an example of a time when a project or deliverable failed to meet expectations? What did you learn?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Why do you want to work for Northrop Grumman, and what interests you about the defense sector?

Medium · Behavioral & Team Dynamics

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you manage competing priorities when working under tight program deadlines?

Medium · Behavioral & Team Dynamics

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?