cswork / libraryOpen practice workspace

Interview guides · Argonne National Laboratory

Argonne National Laboratory Software Engineer Interview Guide

Argonne National Laboratory Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Argonne National Laboratory, you play a vital role in powering world-class scientific discovery, high-performance computing, and national research infrastructure. Your work directly impacts how researchers manage massive data streams, orchestrate containerized workloads on leadership-class supercomputers, and build robust software services for complex experimental systems. Whether you are developing infrastructure-as-code pipelines, administering on-premise Kubernetes clusters, or writing low-level control systems, your engineering output enables breakthroughs across diverse scientific domains. The complexity of this role lies at the intersection of enterprise software reliability and cutting-edge scientific research.

This guide is scoped to a Software Engineer candidate at Argonne National Laboratory.

Focus areas

  • Kubernetes
  • GitOps methodologies
  • Linux

The Argonne National Laboratory interview process

Argonne National Laboratory candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Initial Screening Call

A call with a recruiter or hiring manager to discuss your background, interest in the lab's mission, and basic role requirements.

What to demonstrate

  • A call with a recruiter or hiring manager to discuss your background, interest in the lab's mission, and basic role requirements
  • Depth in Kubernetes

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.

Technical Deep-Dive Screen

Discussion of past projects, architectural decisions, and relevant technologies related to the team.

What to demonstrate

  • Discussion of past projects, architectural decisions, and relevant technologies related to the team
  • Depth in Kubernetes

How to prepare

  • Answer aloud and timed: How do Linux namespaces and cgroups work under the hood to isolate containerized workloads?
  • Answer aloud and timed: What experience do you have with graphical user interface development and design patterns in enterprise environments?

Comprehensive Panel Interview

A panel interview with cross-functional team members, including peer engineers and scientists, focusing on project presentations and behavioral questions.

What to demonstrate

  • A panel interview with cross-functional team members
  • Including peer engineers and scientists
  • Focusing on project presentations and behavioral questions

How to prepare

  • Answer aloud and timed: How would you approach troubleshooting a network routing issue involving Container Network Interfaces in an on-premise Kubernetes deployment?
  • Answer aloud and timed: Can you describe your familiarity with software release management protocols and planned infrastructure upgrades?

Where candidates lose points

Tailor your technical seminar carefully

If your interview requires a presentation, focus on clear storytelling, architectural rationale, and measurable impact. Engage the panel by welcoming questions and treating the session as an interactive scientific discussion.

Highlight cross-functional empathy

Emphasize instances where you successfully bridged the gap between technical infrastructure teams and end-users, such as researchers or scientists who have unique workflow requirements.

Demonstrate security and compliance awareness

Given the institutional setting, show that you understand the importance of strict access controls, network policies, and compliance frameworks when managing shared infrastructure.

Administrative communication can occasionally experience delays during hiring committee reviews

Maintain open communication with your HR contact and exercise patience throughout the timeline.

Questions & practice

Can you explain the basics of multithreaded programming and how you handle race conditions in C++ or Java?

Medium · Technical and Domain 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?

What experience do you have with graphical user interface development and design patterns in enterprise enviro

Medium · Technical and Domain Fundamentals

What experience do you have with graphical user interface development and design patterns in enterprise environments?

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?

Track a rolling failure rate per destination for circuit decisions

Easy · sliding window · ring buffer · circuit breaker

The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.

Approach

  1. Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
  2. Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
  3. State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
  4. Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.

Follow-up

  • The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
  • A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?

Hold a per-tenant active cap against concurrent creates

Hard · write skew · isolation levels · constraints

A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.

Approach

  1. Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
  2. Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
  3. Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
  4. State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.

Follow-up

  • A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
  • The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads 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?

This category evaluates your core knowledge of programming languages, operating systems, and domain-specific d

Medium · Technical and Domain Fundamentals

This category evaluates your core knowledge of programming languages, operating systems, and domain-specific development practices.

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 do Linux namespaces and cgroups work under the hood to isolate containerized workloads?

Medium · Technical and Domain Fundamentals

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?

Can you describe your familiarity with software release management protocols and planned infrastructure upgrad

Medium · Technical and Domain Fundamentals

Can you describe your familiarity with software release management protocols and planned infrastructure upgrades?

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?

This category examines your ability to design scalable, secure, and maintainable systems for production worklo

Medium · System Architecture and Design

This category examines your ability to design scalable, secure, and maintainable systems for production workloads.

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 approach designing a declarative infrastructure-as-code pipeline using GitOps methodologies like Ar

Medium · System Architecture and Design

How do you approach designing a declarative infrastructure-as-code pipeline using GitOps methodologies like ArgoCD?

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 strategies do you use for secrets management and role-based access control in a multi-tenant cluster envi

Medium · System Architecture and Design

What strategies do you use for secrets management and role-based access control in a multi-tenant cluster environment?

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 would you integrate a new software service with existing facility-wide networking and security compliance

Medium · System Architecture and Design

How would you integrate a new software service with existing facility-wide networking and security compliance teams?

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 approach troubleshooting a network routing issue involving Container Network Interfaces in an on

Medium · Technical and Domain Fundamentals

How would you approach troubleshooting a network routing issue involving Container Network Interfaces in an on-premise Kubernetes deployment?

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?

How do you model core values of safety, integrity, and respect when dealing with an urgent production outage?

Medium · Behavioral and Collaboration

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 Argonne National Laboratory candidates report.

Day 1 — Map the Argonne National Laboratory loop

  • Write out the reported sequence: Initial Screening Call, Technical Deep-Dive Screen, Comprehensive Panel Interview.
  • 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 3 reported rounds, with the weakest marked.

Day 2 — Work Kubernetes

  • Spend the session on Kubernetes, which Argonne National Laboratory candidates report being tested on.
  • Write one worked example in Kubernetes and time yourself on it.

Deliverable: One timed worked example in Kubernetes.

Day 3 — Work GitOps methodologies

  • Spend the session on GitOps methodologies, which Argonne National Laboratory candidates report being tested on.
  • Write one worked example in GitOps methodologies and time yourself on it.

Deliverable: One timed worked example in GitOps methodologies.

Day 4 — Work Linux

  • Spend the session on Linux, which Argonne National Laboratory candidates report being tested on.
  • Write one worked example in Linux and time yourself on it.

Deliverable: One timed worked example in Linux.

Day 5 — Answer out loud: Technical and Domain Fundamentals

  • Answer aloud, timed: This category evaluates your core knowledge of programming languages, operating systems, and domain-specific development practices.
  • Answer aloud, timed: Can you explain the basics of multithreaded programming and how you handle race conditions in C++ or Java?

Deliverable: Spoken answers to 2 reported Technical and Domain Fundamentals question(s), under time.

Day 6 — Answer out loud: System Architecture and Design

  • Answer aloud, timed: This category examines your ability to design scalable, secure, and maintainable systems for production workloads.
  • Answer aloud, timed: How do you approach designing a declarative infrastructure-as-code pipeline using GitOps methodologies like ArgoCD?

Deliverable: Spoken answers to 2 reported System Architecture and Design question(s), under time.

Day 7 — Answer out loud: Behavioral and Collaboration

  • Answer aloud, timed: This category tests how you communicate, handle cross-functional projects, and align with institutional values.
  • Answer aloud, timed: Can you describe a project where you collaborated closely with non-technical stakeholders or scientific research teams?

Deliverable: Spoken answers to 2 reported Behavioral and Collaboration question(s), under time.

Behavioural preparation

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

Describe a time when you had to scale a contemporary web application or distributed service under heavy user l

Medium · System Architecture and Design

Describe a time when you had to scale a contemporary web application or distributed service under heavy user load.

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?

This category tests how you communicate, handle cross-functional projects, and align with institutional values

Medium · Behavioral and Collaboration

This category tests how you communicate, handle cross-functional projects, and align with institutional values.

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 describe a project where you collaborated closely with non-technical stakeholders or scientific resear

Medium · Behavioral and Collaboration

Can you describe a project where you collaborated closely with non-technical stakeholders or scientific research teams?

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 and balance a diverse workload while maintaining high code quality and

Medium · Behavioral and Collaboration

How do you manage competing priorities and balance a diverse workload while maintaining high code quality and documentation?

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 me about a time when you identified a systemic technical inefficiency and independently drove a solution.

Medium · Behavioral and 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?