As a Software Engineer at True Anomaly, you will build the software that serves as the central nervous system for our spacecraft, mission control, and distributed ground systems. Our mission is to safeguard space security and sustainability by building cutting-edge technology at the intersection of spacecraft, autonomous systems, and tactical software. The applications you develop will bridge the gap between military objectives, advanced astrodynamics, and real-time human and autonomous control of spacecraft. In this role, you will work on highly complex, greenfield problems where off-the-shelf solutions do not exist. You will contribute to our advanced mission control platform, designing systems that process high-throughput telemetry, coordinate satellite commands, and render complex 2D and 3D space environments. Your work directly impacts national security, space situational awareness, and the operational capabilities of the U.S. and its allies. Whether you are optimizing a distributed backend in Elixir, building a highly responsive React and frontend, or developing low-level telemetry pipelines in or, you will be given immense ownership. You will collaborate daily with space operators, hardware designers, and astrodynamics algorithm engineers to build resilient, fault-tolerant systems capable of operating under extreme conditions. TypeScript C++ Python
Recruiter Screen
reportedInitial assessment of your technical background and interest in the company's mission.
What to demonstrate
- Initial assessment of your technical background and interest in the company's mission
- Depth in Technical Assessment (Homework)
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Hiring Manager Conversation
reportedTechnical and experience-based discussion with the hiring manager.
What to demonstrate
- Technical and experience-based discussion with the hiring manager
- Depth in Technical Assessment (Homework)
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
Core Technical Evaluation
reportedIncludes a practical homework assessment followed by a panel presentation.
What to demonstrate
- Includes a practical homework assessment followed by a panel presentation
- Depth in Technical Assessment (Homework)
How to prepare
- Answer aloud and timed: How would you implement a multithreaded telemetry processing application in C++ or Python?
- Answer aloud and timed: Explain how you would manage thread communication using queues and mutexes to avoid race conditions and deadlocks.
Panel Presentation
reportedDefend your design decisions in front of an engineering panel.
What to demonstrate
- Defend your design decisions in front of an engineering panel
- Depth in Technical Assessment (Homework)
How to prepare
- Answer aloud and timed: What are the advantages of the Actor model and Elixir GenServers when managing the state of individual spacecraft or ground stations?
- Answer aloud and timed: How do you design a system to handle high-concurrency connections from multiple ground operators simultaneously?
Executive Fit Check
reportedFinal alignment discussion with the CEO or senior leadership to ensure mission fit.
What to demonstrate
- Final alignment discussion with the CEO or senior leadership to ensure mission fit
- Depth in Technical Assessment (Homework)
How to prepare
- Answer aloud and timed: Describe a time when you had to build a complex system based on highly vague or incomplete requirements. How did you resolve the ambiguity?
- Answer aloud and timed: How do you handle constructive conflict when reviewing code or system designs with senior engineers and stakeholders?
PracHub editorial advice for the preparation topics above.
Treat the Homework as a Production Spec
The technical assignment prompt can be vague. Do not just build the bare minimum. Treat it as a real-world product request from a stakeholder. Document your assumptions clearly, explain why you chose specific protocols, and outline how your system would scale or handle failures.
Explicitly Use a Job Queue
When designing any system that communicates commands to a third-party API (such as the TT&C homework), always introduce a messaging or job queue (like RabbitMQ). Even if the prompt does not explicitly request it, the engineering panel heavily looks for this pattern to manage asynchronous tasks and API rate limits.
During your system design presentation, be prepared for highly active questioning
The engineers will challenge your choices of databases, protocols, and concurrency controls. This is not a sign of a bad interview; they want to see how you handle constructive technical conflict and defend your engineering decisions with data.
Brush Up on Basic Space Terminology
While space experience is not required, knowing the basics of what a satellite ground station, telemetry stream, and command uplink are will help you communicate much more effectively with the panel. It prevents minor misunderstandings during domain-specific system design questions.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How would you implement a multithreaded telemetry processing application in C++ or Python?
How would you implement a multithreaded telemetry processing application in C++ or Python?
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?
Explain how you would manage thread communication using queues and mutexes to avoid race conditions and deadlo
Explain how you would manage thread communication using queues and mutexes to avoid race conditions and deadlocks.
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 advantages of the Actor model and Elixir GenServers when managing the state of individual spacecr
What are the advantages of the Actor model and Elixir GenServers when managing the state of individual spacecraft or ground stations?
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?
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?
Hold a per-tenant active cap against concurrent creates
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
- 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.
- 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.
- 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.
- 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?
How would you design a Telemetry, Tracking, and Command (TT&C) server that interfaces with a third-party satel
How would you design a Telemetry, Tracking, and Command (TT&C) server that interfaces with a third-party satellite API?
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?
What protocols and data serialization formats would you choose to transmit commands and receive telemetry data
What protocols and data serialization formats would you choose to transmit commands and receive telemetry data under high-latency conditions?
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 structure a system to guarantee that critical spacecraft commands are delivered, retried, and re
How would you structure a system to guarantee that critical spacecraft commands are delivered, retried, and recorded in the event of a network partition?
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 do you manage rate-limiting and backpressure when consuming high-volume telemetry feeds from an external A
How do you manage rate-limiting and backpressure when consuming high-volume telemetry feeds from an external API?
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 you design a system to handle high-concurrency connections from multiple ground operators simultaneousl
How do you design a system to handle high-concurrency connections from multiple ground operators simultaneously?
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?
Listing latency scales with page size, not with filters
The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.
Approach
- Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
- Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
- Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
- Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.
Follow-up
- The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
- How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?
Built from the rounds and topics True Anomaly candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the True Anomaly loop
- Write out the reported sequence: Recruiter Screen, Hiring Manager Conversation, Core Technical Evaluation, Panel Presentation, Executive Fit Check.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.
02Work Technical Assessment (Homework)
- Spend the session on Technical Assessment (Homework), which True Anomaly candidates report being tested on.
- Write one worked example in Technical Assessment (Homework) and time yourself on it.
Deliverable: One timed worked example in Technical Assessment (Homework).
03Work Queue-Based Messaging
- Spend the session on Queue-Based Messaging, which True Anomaly candidates report being tested on.
- Write one worked example in Queue-Based Messaging and time yourself on it.
Deliverable: One timed worked example in Queue-Based Messaging.
04Work Multithreaded Programming
- Spend the session on Multithreaded Programming, which True Anomaly candidates report being tested on.
- Write one worked example in Multithreaded Programming and time yourself on it.
Deliverable: One timed worked example in Multithreaded Programming.
05Answer out loud: System Design & Architecture
- Answer aloud, timed: How would you design a Telemetry, Tracking, and Command (TT&C) server that interfaces with a third-party satellite API?
- Answer aloud, timed: What protocols and data serialization formats would you choose to transmit commands and receive telemetry data under high-latency conditions?
Deliverable: Spoken answers to 2 reported System Design & Architecture question(s), under time.
06Answer out loud: Concurrency & Systems Programming
- Answer aloud, timed: How would you implement a multithreaded telemetry processing application in C++ or Python?
- Answer aloud, timed: Explain how you would manage thread communication using queues and mutexes to avoid race conditions and deadlocks.
Deliverable: Spoken answers to 2 reported Concurrency & Systems Programming question(s), under time.
07Answer out loud: Behavioral & Mission Alignment
- Answer aloud, timed: Describe a time when you had to build a complex system based on highly vague or incomplete requirements. How did you resolve the ambiguity?
- Answer aloud, timed: How do you handle constructive conflict when reviewing code or system designs with senior engineers and stakeholders?
Deliverable: Spoken answers to 2 reported Behavioral & Mission 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 build a complex system based on highly vague or incomplete requirements. How d
Describe a time when you had to build a complex system based on highly vague or incomplete requirements. How did you resolve the ambiguity?
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 constructive conflict when reviewing code or system designs with senior engineers and stakeh
How do you handle constructive conflict when reviewing code or system designs with senior engineers and stakeholders?
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?
Why do you want to work at the intersection of aerospace, defense, and software engineering?
Why do you want to work at the intersection of aerospace, defense, and software engineering?
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 time you had to defend an architectural decision to a panel of engineers who disagreed with yo
Tell me about a time you had to defend an architectural decision to a panel of engineers who disagreed with your approach.
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 build a complex system based on highly vague or incomplete requirements. How did you resolve the ambiguity?
- 02
How do you handle constructive conflict when reviewing code or system designs with senior engineers and stakeholders?
- 03
Why do you want to work at the intersection of aerospace, defense, and software engineering?
- 04
Tell me about a time you had to defend an architectural decision to a panel of engineers who disagreed with your approach.
Do I need prior aerospace or space industry experience to apply?
No. True Anomaly actively hires talented software engineers from commercial, enterprise, and deep-tech backgrounds. While you will build software for spacecraft and ground systems, we have plenty of in-house space experts to guide you. You must, however, be eager to learn space domain concepts quickly.
True Anomaly Software Engineer candidate reports ↗How difficult is the technical homework assignment?
The assignment itself is moderately difficult but highly open-ended. It is often described as a "Rorschach test" because the requirements are intentionally high-level. Success depends on your ability to make sound architectural decisions, document your assumptions, and defend your design choices during the panel presentation.
True Anomaly Software Engineer candidate reports ↗What is the working culture like at True Anomaly?
We operate with high intensity, extreme ownership, and a commitment to professional, constructive conflict. We value engineers who are willing to challenge assumptions to deliver ambitious results. It is a highly collaborative environment where software engineers work directly alongside hardware builders and tactical space operators.
True Anomaly Software Engineer candidate reports ↗What is the policy on remote work?
While we offer flexible work hours and hybrid options depending on the team, many of our roles benefit from being close to our hardware and engineering labs in Denver, CO, to ensure tight feedback loops between software and physical systems.
True Anomaly Software Engineer candidate reports ↗What topics does True Anomaly test in interviews?
True Anomaly interviews most often cover Quality Assurance (QA) Engineering, Technical Assessment (Homework), Queue-Based Messaging, Test Stand Engineering, and Multithreaded Programming. The exact emphasis depends on the specific role you apply for.
True Anomaly 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.
- 01True Anomaly 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.
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.
Rystad Energy Software Engineer Interview Guide
Prepare for Rystad Energy software interviews with worked Python validation, OOP and decorator examples, plus an ingestion case and practical checks.
Zoom Video Communications Software Engineer Interview Guide
What Zoom Video Communications asks Software Engineer candidates, from reported rounds and questions.