The National Radio Astronomy Observatory (NRAO) designs, builds, and operates some of the world's most sophisticated radio telescopes, including the Very Large Array (VLA), the Very Long Baseline Array (VLBA), and the Atacama Large Millimeter/submillimeter Array (ALMA). As a Software Engineer at NRAO, you do not just write standard business logic; you build the digital nervous system that controls massive physical instruments, processes petabytes of cosmic data, and enables groundbreaking astronomical discoveries. Your work directly impacts the global scientific community by transforming raw radio signals into clear, actionable scientific data. In this role, you will work at the intersection of high-performance computing, real-time control systems, and scientific data pipelines. Whether you are developing low-level control software for telescope antennas, optimizing data transmission from remote high-altitude sites, or building user-facing tools that astronomers use to configure observations, your contributions will require high reliability and precision. NRAO employs both specialized scientific software developers and pure software professionals. You do not need a background in astrophysics to succeed here; rather, the organization highly values robust software engineering fundamentals, clean code architecture, and a strong capability to solve complex, non-standard engineering problems.
Phone Screen
reportedInitial conversation with a recruiter or hiring team member to assess availability, interest in the mission, and high-level technical qualifications.
What to demonstrate
- Initial conversation with a recruiter or hiring team member to assess availability, interest in the mission, and high-level technical qualifications
- Depth in Software Engineering
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 Interview Phase
reportedComprehensive technical interviews conducted online or on-site, including panel interviews with team members and technical discussions.
What to demonstrate
- Comprehensive technical interviews conducted online or on-site
- Including panel interviews with team members and technical discussions
How to prepare
- Answer aloud and timed: Describe how you would implement error handling and recovery in a system that controls physical hardware.
- Answer aloud and timed: What are the trade-offs of using a compiled language like C++ versus an interpreted language like Python for data-heavy applications?
On-site Experience
reportedCollaborative on-site interviews that include panel discussions, a shared lunch, and a tour of local facilities.
What to demonstrate
- Collaborative on-site interviews that include panel discussions, a shared lunch, and a tour of local facilities
- Depth in Software Engineering
How to prepare
- Answer aloud and timed: Walk me through how you would diagnose a network latency issue between a data acquisition system and a storage archive.
- Answer aloud and timed: Describe your experience with containerization and continuous integration (CI/CD) pipelines in a shared development environment.
PracHub editorial advice for the preparation topics above.
Show enthusiasm for the scientific mission
While you do not need to be an astronomer, showing genuine curiosity about radio astronomy, the telescopes, and the scientific discoveries enabled by NRAO goes a long way with the hiring team.
Travel and lodging expenses for on-site interviews are fully reimbursed by NRAO
This includes your flights, hotel, and reasonable meal costs incurred during your travel.
Highlight your adaptability
Scientific software often deals with unique, non-standard constraints. Be ready to share examples of how you successfully adapted to unfamiliar technologies, legacy systems, or ambiguous requirements in your past roles.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain the difference between process-based and thread-based concurrency. When would you use one over the oth
Explain the difference between process-based and thread-based concurrency. When would you use one over the other?
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?
What are the trade-offs of using a compiled language like C++ versus an interpreted language like Python for d
What are the trade-offs of using a compiled language like C++ versus an interpreted language like Python for data-heavy applications?
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?
Canonicalise a request body into a stable idempotency fingerprint
idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.
Approach
- Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
- Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
- Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
- Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.
Follow-up
- A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
- Where does the fingerprint get computed relative to request decompression and the body-size limit?
Find version gaps and relay lag with window functions
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
- 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.
- 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.
- 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.
- 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?
Write the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
How do you optimize a slow-running data pipeline that processes large binary files?
How do you optimize a slow-running data pipeline that processes large binary files?
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 how you would implement error handling and recovery in a system that controls physical hardware.
Describe how you would implement error handling and recovery in a system that controls physical hardware.
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?
Walk me through how you would diagnose a network latency issue between a data acquisition system and a storage
Walk me through how you would diagnose a network latency issue between a data acquisition system and a storage archive.
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?
How do you approach writing automated tests for legacy codebases that lack documentation?
How do you approach writing automated tests for legacy codebases that lack documentation?
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?
How do you translate highly technical scientific requirements from an astronomer into clear, actionable softwa
How do you translate highly technical scientific requirements from an astronomer into clear, actionable software specifications?
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 a situation where you had to work with a team member who had a very different technical background th
Describe a situation where you had to work with a team member who had a very different technical background than yours. How did you ensure successful collaboration?
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 is your approach to managing technical debt when working on long-term scientific infrastructure?
What is your approach to managing technical debt when working on long-term scientific infrastructure?
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 customer endpoint stalls deliveries to every other destination
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
- 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.
- 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.
- 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.
- 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?
Built from the rounds and topics National Radio Astronomy Observatory candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the National Radio Astronomy Observatory loop
- Write out the reported sequence: Phone Screen, Technical Interview Phase, On-site Experience.
- 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.
02Work Software Engineering
- Spend the session on Software Engineering, which National Radio Astronomy Observatory candidates report being tested on.
- Write one worked example in Software Engineering and time yourself on it.
Deliverable: One timed worked example in Software Engineering.
03Work Electronics Engineering Fundamentals
- Spend the session on Electronics Engineering Fundamentals, which National Radio Astronomy Observatory candidates report being tested on.
- Write one worked example in Electronics Engineering Fundamentals and time yourself on it.
Deliverable: One timed worked example in Electronics Engineering Fundamentals.
04Work RF Receiver Technology
- Spend the session on RF Receiver Technology, which National Radio Astronomy Observatory candidates report being tested on.
- Write one worked example in RF Receiver Technology and time yourself on it.
Deliverable: One timed worked example in RF Receiver Technology.
05Answer out loud: Technical & Core Software Engineering
- Answer aloud, timed: Explain the difference between process-based and thread-based concurrency. When would you use one over the other?
- Answer aloud, timed: How do you optimize a slow-running data pipeline that processes large binary files?
Deliverable: Spoken answers to 2 reported Technical & Core Software Engineering question(s), under time.
06Answer out loud: Systems & Task Execution
- Answer aloud, timed: Walk me through how you would diagnose a network latency issue between a data acquisition system and a storage archive.
- Answer aloud, timed: Describe your experience with containerization and continuous integration (CI/CD) pipelines in a shared development environment.
Deliverable: Spoken answers to 2 reported Systems & Task Execution question(s), under time.
07Answer out loud: Collaboration & Scenario-Based
- Answer aloud, timed: How do you translate highly technical scientific requirements from an astronomer into clear, actionable software specifications?
- Answer aloud, timed: Describe a situation where you had to work with a team member who had a very different technical background than yours. How did you ensure successful collaboration?
Deliverable: Spoken answers to 2 reported Collaboration & Scenario-Based 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 your experience with containerization and continuous integration (CI/CD) pipelines in a shared develo
Describe your experience with containerization and continuous integration (CI/CD) pipelines in a shared development 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?
Describe a time when you had to quickly learn a new framework or tool to complete a critical project milestone
Describe a time when you had to quickly learn a new framework or tool to complete a critical project milestone.
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 handle a situation where a critical system failure occurs during an active observation run?
How do you handle a situation where a critical system failure occurs during an active observation run?
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 your experience with containerization and continuous integration (CI/CD) pipelines in a shared development environment.
- 02
Describe a time when you had to quickly learn a new framework or tool to complete a critical project milestone.
- 03
How do you handle a situation where a critical system failure occurs during an active observation run?
Do I need a background in astronomy or physics to get hired?
No. While a background or interest in science is a plus, NRAO hires pure software engineers who can bring industry-standard software development practices to their scientific projects. You will learn any necessary astronomical concepts on the job from the domain experts you work with.
National Radio Astronomy Observatory Software Engineer candidate reports ↗What is the work culture like at NRAO?
The culture is highly collaborative, academic, and mission-driven. Engineers take great pride in supporting cutting-edge scientific discovery. The environment is generally more relaxed and stable compared to fast-paced commercial tech startups, with a strong focus on work-life balance.
National Radio Astronomy Observatory Software Engineer candidate reports ↗How long does the hiring process typically take?
The process can take anywhere from one to three months. Because NRAO is a federally funded research facility, administrative steps, background checks, and hiring committee reviews can sometimes take longer than in the private sector. Maintaining patience and clear communication with your recruiter is key.
National Radio Astronomy Observatory Software Engineer candidate reports ↗Are there opportunities for remote or hybrid work?
Yes, depending on the specific role and team. While some software positions require on-site presence—especially those dealing directly with physical hardware at telescope sites like Green Bank or the VLA—many software roles offer flexible hybrid or fully remote arrangements.
National Radio Astronomy Observatory Software Engineer candidate reports ↗What topics does National Radio Astronomy Observatory test in interviews?
National Radio Astronomy Observatory interviews most often cover Software Engineering, Systems Engineering, Systems Administration, Electronics Engineering Fundamentals, and RF Receiver Technology. The exact emphasis depends on the specific role you apply for.
National Radio Astronomy Observatory 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.
- 01National Radio Astronomy Observatory 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.
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.
X: The Moonshot Factory Software Engineer Interview Guide
What X: The Moonshot Factory asks Software Engineer candidates, from reported rounds and questions.
Xona Space Systems Software Engineer Interview Guide
What Xona Space Systems asks Software Engineer candidates, from reported rounds and questions.
Western Alliance Bank Software Engineer Interview Guide
What Western Alliance Bank asks Software Engineer candidates, from reported rounds and questions.