cswork / libraryOpen practice workspace

Interview guides · Johns Hopkins Applied Physics Laboratory

Johns Hopkins Applied Physics Laboratory Software Engineer Interview Guide

Johns Hopkins Applied Physics Laboratory Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

A Software Engineer at Johns Hopkins Applied Physics Laboratory (APL) plays a critical role in solving complex research, national security, and space exploration challenges. Unlike traditional commercial technology companies focused on consumer web applications, Johns Hopkins APL develops mission-critical software systems, high-fidelity modeling and simulation platforms, real-time embedded software, signal processing pipelines, and AI-enabled capabilities. Engineers at the Laboratory contribute directly to domain-defining initiatives across space exploration, air and missile defense, cyber operations, and neural engineering. In this position, your work directly influences high-stakes applications where reliability, precision, and performance are paramount.

This guide is scoped to a Software Engineer candidate at Johns Hopkins Applied Physics Laboratory.

Focus areas

  • Behavioral Interviewing
  • Model Training Diagnostics (Overfitting/Underfitting)
  • React

The Johns Hopkins Applied Physics Laboratory interview process

Johns Hopkins Applied Physics Laboratory candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Technical Phone Screen

Initial technical phone screen or video call with a hiring manager or senior engineer focusing on your background and career goals.

What to demonstrate

  • Initial technical phone screen or video call with a hiring manager or senior engineer focusing on your background and career goals
  • Depth in Behavioral Interviewing

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.

Recruiter Call

Discussion with a Talent Acquisition Recruiter about the laboratory's structure, benefits, and security clearance requirements.

What to demonstrate

  • Discussion with a Talent Acquisition Recruiter about the laboratory's structure, benefits, and security clearance requirements
  • Depth in Behavioral Interviewing

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.

Panel Interview

Comprehensive panel interview with multiple small panels of team members, section leaders, and department managers, lasting between two hours and a full day.

What to demonstrate

  • Comprehensive panel interview with multiple small panels of team members, section leaders, and department managers, lasting between two hours and a full day
  • Depth in Behavioral Interviewing

How to prepare

  • Answer aloud and timed: Explain a research or university project in simple terms as if you were presenting to a non-technical stakeholder or client.
  • Answer aloud and timed: Describe the core principles of object-oriented programming (OOP), such as inheritance, encapsulation, and polymorphism.

Technical Presentation

Present a project of your choice to the team, followed by a Q&A session to simulate the collaborative environment.

What to demonstrate

  • Present a project of your choice to the team, followed by a Q&A session to simulate the collaborative environment
  • Depth in Behavioral Interviewing

How to prepare

  • Answer aloud and timed: Describe the differences between an interface and an abstract class in Java or C++.
  • Answer aloud and timed: What is the Big O time complexity of removing the first item from a linked list versus an array?

Where candidates lose points

Master Every Line on Your Resume

Interviewers will ask detailed questions about any language, framework, project, or course listed on your resume. If you list a technology, be prepared to discuss its internal mechanics and how you used it.

Structure Your Technical Presentation Early

If asked to give a 15-minute presentation, focus on clear problem statements, your individual contributions, architectural choices, challenges overcome, and measurable outcomes.

Highlight Interdisciplinary Collaboration

Emphasize experience working alongside engineers from non-software disciplines, such as physics, mechanical engineering, or operational analysis.

Do not attempt to exaggerate your experience with specific programming languages or technical domains on your resume

Panel members routinely ask targeted, foundational questions on listed skills to test true depth.

Questions & practice

What is the Big O time complexity of removing the first item from a linked list versus an array?

Medium · Computer Science Fundamentals & Object-O

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?

Compare and contrast the characteristics and memory models of C++ and Java.

Medium · Computer Science Fundamentals & Object-O

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 would you structure a basic algorithm to begin solving a complex logic puzzle like Sudoku?

Medium · Computer Science Fundamentals & Object-O

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?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

  1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
  2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
  3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
  4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

  • The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
  • A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

Explain why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.

Approach

  1. Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
  2. For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
  3. Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
  4. Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.

Follow-up

  • 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
  • A dashboard runs this for 40 owners in one page load. What changes about the design?

Walk through a recent technical project on your resume in detail, explaining your personal contributions, desi

Medium · Resume & Project Walkthroughs

Walk through a recent technical project on your resume in detail, explaining your personal contributions, design decisions, and trade-offs.

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 the most difficult technical problem or bug you have had to resolve in a prior project or research ef

Medium · Resume & Project Walkthroughs

Describe the most difficult technical problem or bug you have had to resolve in a prior project or research effort.

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 did you learn from your past projects, and how have those lessons shaped your engineering approach?

Medium · Resume & Project Walkthroughs

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?

Talk about a time you worked with large, pre-existing codebases or prediction models.

Medium · Resume & Project Walkthroughs

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?

Explain a research or university project in simple terms as if you were presenting to a non-technical stakehol

Medium · Resume & Project Walkthroughs

Explain a research or university project in simple terms as if you were presenting to a non-technical stakeholder or client.

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 the core principles of object-oriented programming (OOP), such as inheritance, encapsulation, and pol

Medium · Computer Science Fundamentals & Object-O

Describe the core principles of object-oriented programming (OOP), such as inheritance, encapsulation, and polymorphism.

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 the differences between an interface and an abstract class in Java or C++.

Medium · Computer Science Fundamentals & Object-O

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?

Explain the Systems Engineering Life Cycle (V-model) and how software development integrates into it.

Medium · Domain-Specific & Systems Engineering Co

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?

How would you evaluate or address underfitting and overfitting when training a machine learning model?

Medium · Domain-Specific & Systems Engineering Co

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 approach would you take to parse extremely large text files efficiently for identical content?

Medium · Domain-Specific & Systems Engineering Co

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?

Explain the key differences between symmetric and asymmetric encryption models.

Medium · Domain-Specific & Systems Engineering Co

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 your understanding of simulation frameworks, radar/sensor blending, or domain concepts like orbital m

Medium · Domain-Specific & Systems Engineering Co

Describe your understanding of simulation frameworks, radar/sensor blending, or domain concepts like orbital mechanics.

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?

One customer endpoint stalls deliveries to every other destination

Medium · bulkhead · timeouts · saturation

The egress service delivers about 1.5k webhooks/second across 40,000 destinations, with a per-destination concurrency cap of 4 and a 10-second connect-plus-read timeout. Throughput falls to 300/second, queue depth climbs, and p99 delivery latency for unaffected destinations goes from 200 ms to minutes, while the error rate barely moves. One tenant holds 900 destination rows whose URLs share a hostname that now answers in 9.5 seconds. Explain the mechanism with the arithmetic, then give the containment in the order you would apply it.

Approach

  1. Look at saturation before errors. A flat error rate with collapsing throughput says nothing is failing, things are waiting, so the first signal to pull is in-flight request count or pool wait time rather than the error counter. This is the distinction that decides the whole investigation.
  2. Group in-flight work by resolved host, not by destination id. The cap is keyed per destination row, so 900 rows sharing one hostname buy 3,600 concurrent slots against a single host, each held for 9.5 seconds. The bulkhead was never a bulkhead for that host, and grouping by the wrong dimension is why the dashboard looked healthy.
  3. Do the arithmetic in both directions. Required concurrency is arrival rate times latency, so 1.5k/second at 200 ms needs about 300 in flight, which is entirely consumed by 3,600 slow slots; conversely whatever concurrency is left sustains rate equals concurrency divided by 9.5 seconds, which is the 300/second you are seeing. Matching both numbers is what promotes this from a plausible story to the mechanism.
  4. Explain why the circuit breaker never helped. It opens on consecutive failures, and a 9.5-second response inside a 10-second timeout is a success. Slow is not failing, so an error-rate breaker cannot see this; you need a slow-call ratio, a deadline propagated from the caller's remaining budget, or a concurrency limiter.

Follow-up

  • The host recovers to 80 ms. How long does the queue take to drain, and what does the drain do to the recovered host?
  • Where should the 10-second timeout number actually come from?

Suggested practice checklist

Built from the rounds and topics Johns Hopkins Applied Physics Laboratory candidates report.

Day 1 — Map the Johns Hopkins Applied Physics Laboratory loop

  • Write out the reported sequence: Technical Phone Screen, Recruiter Call, Panel Interview, Technical Presentation.
  • 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

  • Spend the session on Behavioral Interviewing, which Johns Hopkins Applied Physics Laboratory candidates report being tested on.
  • Write one worked example in Behavioral Interviewing and time yourself on it.

Deliverable: One timed worked example in Behavioral Interviewing.

Day 3 — Work Model Training Diagnostics (Overfitting/Underfitting)

  • Spend the session on Model Training Diagnostics (Overfitting/Underfitting), which Johns Hopkins Applied Physics Laboratory candidates report being tested on.
  • Write one worked example in Model Training Diagnostics (Overfitting/Underfitting) and time yourself on it.

Deliverable: One timed worked example in Model Training Diagnostics (Overfitting/Underfitting).

Day 4 — Work React

  • Spend the session on React, which Johns Hopkins Applied Physics Laboratory candidates report being tested on.
  • Write one worked example in React and time yourself on it.

Deliverable: One timed worked example in React.

Day 5 — Answer out loud: Resume & Project Walkthroughs

  • Answer aloud, timed: Walk through a recent technical project on your resume in detail, explaining your personal contributions, design decisions, and trade-offs.
  • Answer aloud, timed: Describe the most difficult technical problem or bug you have had to resolve in a prior project or research effort.

Deliverable: Spoken answers to 2 reported Resume & Project Walkthroughs question(s), under time.

Day 6 — Answer out loud: Computer Science Fundamentals & Object-Oriented Design

  • Answer aloud, timed: Describe the core principles of object-oriented programming (OOP), such as inheritance, encapsulation, and polymorphism.
  • Answer aloud, timed: Describe the differences between an interface and an abstract class in Java or C++.

Deliverable: Spoken answers to 2 reported Computer Science Fundamentals & Object-Oriented Design question(s), under time.

Day 7 — Answer out loud: Domain-Specific & Systems Engineering Concepts

  • Answer aloud, timed: Explain the Systems Engineering Life Cycle (V-model) and how software development integrates into it.
  • Answer aloud, timed: How would you evaluate or address underfitting and overfitting when training a machine learning model?

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

Behavioural preparation

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

Why do you want to work for Johns Hopkins Applied Physics Laboratory, and how do your goals align with our mis

Medium · Behavioral & Team Collaboration

Why do you want to work for Johns Hopkins Applied Physics Laboratory, and how do your goals align with our mission?

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?

Walk through a situation where you had a disagreement with a team member on a technical approach and how you r

Medium · Behavioral & Team Collaboration

Walk through a situation where you had a disagreement with a team member on a technical approach and how you resolved it.

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 scenario where you made a technical mistake on a project and how you went about rectifying it.

Medium · Behavioral & Team Collaboration

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?

Do you prefer working as an individual contributor or in a collaborative team setting?

Medium · Behavioral & Team Collaboration

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?

Tell us about a time you led an initiative or took ownership of a critical team goal.

Medium · Behavioral & Team Collaboration

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?