A Software Engineer at Pratt & Whitney plays a critical role in the intersection of cutting-edge aerospace engineering and advanced software systems. Our software engineering teams build, test, and maintain the highly complex, safety-critical systems that power military and commercial aviation. From the flight control software embedded in our state-of-the-art Geared Turbofan (GTF) engines to the sophisticated simulation and modeling tools used by our structural and dynamic analysis teams, software is the invisible backbone of flight safety and efficiency. In this role, you will contribute to systems where performance, reliability, and precision are absolute. Unlike traditional consumer software roles, software engineering at Pratt & Whitney requires a deep appreciation for hardware integration, physical systems, and rigorous compliance standards. Your work directly impacts millions of passengers daily and supports global defense networks, making code optimization and architectural integrity a matter of global safety. You will collaborate closely with multidisciplinary teams, including thermodynamicists, structural engineers, systems designers, and control specialists. Whether you are developing embedded real-time applications, modeling complex combustion behaviors, or building internal analytical pipelines, your contributions will push the boundaries of what is possible in aviation technology.
Initial Screening
reportedA brief phone call with HR or a casual discussion at a recruiting event to assess initial fit.
What to demonstrate
- A brief phone call with HR or a casual discussion at a recruiting event to assess initial fit
- Depth in Kalman Filter Design
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.
Online Assessment
reportedEntry-level candidates may complete an online assessment or a text-based digital interview.
What to demonstrate
- Entry-level candidates may complete an online assessment or a text-based digital interview
- Depth in Kalman Filter Design
How to prepare
- Answer aloud and timed: Give an example of a time when you made a mistake on a project. How did you identify it, and what steps did you take to rectify it?
- Answer aloud and timed: How do you approach explaining a complex technical concept to a non-technical stakeholder or team member?
Superday Event
reportedA comprehensive, multi-hour event involving facility tours, company presentations, and multiple interviews.
What to demonstrate
- A comprehensive, multi-hour event involving facility tours, company presentations, and multiple interviews
- Depth in Kalman Filter Design
How to prepare
- Answer aloud and timed: What does diversity and inclusion mean to you, and how do you foster it in your day-to-day work environment?
- Answer aloud and timed: Walk me through the steps to design and implement a Kalman filter for state estimation.
Technical Presentation
reportedSome teams may require candidates to deliver a technical presentation on a past project.
What to demonstrate
- Some teams may require candidates to deliver a technical presentation on a past project
- Depth in Kalman Filter Design
How to prepare
- Answer aloud and timed: How would you model a physical phenomenon, such as combustion instability, and what software tools or languages would you use to simulate it?
- Answer aloud and timed: Explain how you would write and optimize a piece of code to run on an embedded system with strict memory and processing constraints.
Offer Discussion
reportedCandidates may receive offers within 48 hours of the Superday, though onboarding may take longer.
What to demonstrate
- Candidates may receive offers within 48 hours of the Superday, though onboarding may take longer
- Depth in Kalman Filter Design
How to prepare
- Answer aloud and timed: Describe the architecture of a software project you previously built. What were the key design trade-offs you had to make?
- Answer aloud and timed: Write a pseudo-code implementation of a standard sorting or searching algorithm and explain its time and space complexity.
PracHub editorial advice for the preparation topics above.
Clarify your compensation expectations early
Some candidates have reported discrepancies between advertised salary ranges and final offers. Ensure you discuss salary expectations with your HR recruiter early in the screening process to ensure alignment.
Research our engine portfolio
Spend time reading about our key products, especially the Geared Turbofan (GTF) and military engines like the F135 (which powers the F-35 Lightning II). Showing that you know our products demonstrates high motivation.
Prepare your questions
At the end of every interview, you will have time to ask questions. Use this opportunity to ask about their specific engineering challenges, the software development tools they use, or their experiences working at Pratt & Whitney.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain how you would write and optimize a piece of code to run on an embedded system with strict memory and p
Explain how you would write and optimize a piece of code to run on an embedded system with strict memory and processing constraints.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- 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?
Write a pseudo-code implementation of a standard sorting or searching algorithm and explain its time and space
Write a pseudo-code implementation of a standard sorting or searching algorithm and explain its time and space complexity.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Collapse a redelivered event batch into per-aggregate high-water marks
You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.
Approach
- One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
- Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
- Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
- If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.
Follow-up
- The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
- How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Walk me through the steps to design and implement a Kalman filter for state estimation.
Walk me through the steps to design and implement a Kalman filter for state estimation.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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 would you model a physical phenomenon, such as combustion instability, and what software tools or language
How would you model a physical phenomenon, such as combustion instability, and what software tools or languages would you use to simulate it?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 the architecture of a software project you previously built. What were the key design trade-offs you
Describe the architecture of a software project you previously built. What were the key design trade-offs you had to make?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- 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?
Why do you want to work at Pratt & Whitney specifically, rather than a traditional consumer tech company?
Why do you want to work at Pratt & Whitney specifically, rather than a traditional consumer tech company?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 do you know about our Geared Turbofan engine technology, and why does it interest you?
What do you know about our Geared Turbofan engine technology, and why does it interest you?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- 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?
How do your personal career goals align with our emphasis on continuous education, work ethics, and long-term
How do your personal career goals align with our emphasis on continuous education, work ethics, and long-term career development?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
One log partition stops advancing while the others drain
Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.
Approach
- Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
- Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
- Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
- Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.
Follow-up
- The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
- How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?
Built from the rounds and topics Prattwhitney candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Prattwhitney loop
- Write out the reported sequence: Initial Screening, Online Assessment, Superday Event, Technical Presentation, Offer Discussion.
- 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 5 reported rounds, with the weakest marked.
02Work Kalman Filter Design
- Spend the session on Kalman Filter Design, which Prattwhitney candidates report being tested on.
- Write one worked example in Kalman Filter Design and time yourself on it.
Deliverable: One timed worked example in Kalman Filter Design.
03Work Combustion Instabilities
- Spend the session on Combustion Instabilities, which Prattwhitney candidates report being tested on.
- Write one worked example in Combustion Instabilities and time yourself on it.
Deliverable: One timed worked example in Combustion Instabilities.
04Work Technical Interviewing (Fundamentals)
- Spend the session on Technical Interviewing (Fundamentals), which Prattwhitney candidates report being tested on.
- Write one worked example in Technical Interviewing (Fundamentals) and time yourself on it.
Deliverable: One timed worked example in Technical Interviewing (Fundamentals).
05Answer out loud: Behavioral & Situational (STAR Format)
- Answer aloud, timed: Describe a time when you had to manage multiple competing tasks and tight deadlines. How did you prioritize your work?
- Answer aloud, timed: Tell me about a situation where you had to resolve a conflict within a cross-functional team.
Deliverable: Spoken answers to 2 reported Behavioral & Situational (STAR Format) question(s), under time.
06Answer out loud: Technical & Domain-Specific
- Answer aloud, timed: Walk me through the steps to design and implement a Kalman filter for state estimation.
- Answer aloud, timed: How would you model a physical phenomenon, such as combustion instability, and what software tools or languages would you use to simulate it?
Deliverable: Spoken answers to 2 reported Technical & Domain-Specific question(s), under time.
07Answer out loud: Motivation & Company Alignment
- Answer aloud, timed: Why do you want to work at Pratt & Whitney specifically, rather than a traditional consumer tech company?
- Answer aloud, timed: What do you know about our Geared Turbofan engine technology, and why does it interest you?
Deliverable: Spoken answers to 2 reported Motivation & Company Alignment question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a time when you had to manage multiple competing tasks and tight deadlines. How did you prioritize yo
Describe a time when you had to manage multiple competing tasks and tight deadlines. How did you prioritize your work?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
Tell me about a situation where you had to resolve a conflict within a cross-functional team.
Tell me about a situation where you had to resolve a conflict within a cross-functional team.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
Give an example of a time when you made a mistake on a project. How did you identify it, and what steps did yo
Give an example of a time when you made a mistake on a project. How did you identify it, and what steps did you take to rectify it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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 approach explaining a complex technical concept to a non-technical stakeholder or team member?
How do you approach explaining a complex technical concept to a non-technical stakeholder or team member?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
What does diversity and inclusion mean to you, and how do you foster it in your day-to-day work environment?
What does diversity and inclusion mean to you, and how do you foster it in your day-to-day work environment?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- 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?
- 01
Describe a time when you had to manage multiple competing tasks and tight deadlines. How did you prioritize your work?
- 02
Tell me about a situation where you had to resolve a conflict within a cross-functional team.
- 03
Give an example of a time when you made a mistake on a project. How did you identify it, and what steps did you take to rectify it?
- 04
How do you approach explaining a complex technical concept to a non-technical stakeholder or team member?
How technical is the Software Engineer interview?
It varies significantly by team. If you are interviewing for an embedded flight controls or systems modeling group, expect a highly technical evaluation covering control theory, code optimization, and physical modeling. If you are interviewing for general systems or internal tool development, the focus will lean more toward software architecture, resume reviews, and behavioral scenarios.
Prattwhitney Software Engineer candidate reports ↗What should I wear to my on-site interview?
You should dress formally and professionally. Even if our day-to-day workplace culture is relaxed, our interview processes are highly formal. Wearing a professional suit is strongly recommended for all on-site panel interviews and presentations.
Prattwhitney Software Engineer candidate reports ↗How long does the hiring process take?
While verbal offers are sometimes extended very quickly (within 24 to 48 hours of a Superday), the formal hiring process can take anywhere from 2 to 6 weeks. Because we operate in a highly regulated defense and aerospace sector, background checks, export control screenings, and budget approvals can sometimes cause delays.
Prattwhitney Software Engineer candidate reports ↗Can I choose which team I join?
Yes, to a large extent. During the Superday event, you will typically interview with multiple hiring managers from different departments (such as structures, design, hot section, or controls). This round-robin format allows both you and the managers to assess mutual fit and match you with the group that best aligns with your skills and career interests.
Prattwhitney Software Engineer candidate reports ↗What topics does Prattwhitney test in interviews?
Prattwhitney interviews most often cover Problem Solving, Behavioral Interviewing, Python, Stakeholder Management, and SQL. The exact emphasis depends on the specific role you apply for.
Prattwhitney Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Prattwhitney Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p