As a Software Engineer at Hyertek, you are at the forefront of modernizing critical federal systems. This role is not merely about writing code; it is about architecting secure, scalable, and resilient enterprise applications that operate within the most demanding environments, including Azure Government and classified Top Secret networks. Your work directly impacts the mission readiness of federal agencies by transforming legacy data structures into production-grade, cloud-native architectures. You will join a highly integrated delivery team composed of cloud architects, cybersecurity specialists, and DevSecOps engineers. Whether you are building full-stack applications with Node.js and TypeScript or implementing infrastructure as code to secure DoD workloads, you will be expected to balance technical innovation with strict compliance requirements. Because Hyertek leverages AI-assisted development as a core competency, you will act as both a builder and a validator, using cutting-edge tools to accelerate delivery while maintaining the highest standards of security and maintainability.
TS/SCI Clearance Discussion
reportedEarly focus on your TS/SCI clearance status, discussing your current clearance level and future maintenance.
What to demonstrate
- Early focus on your TS/SCI clearance status, discussing your current clearance level and future maintenance
- Depth in Node.js
How to prepare
- Answer aloud and timed: How do you approach migrating an embedded database to Azure SQL without regressing system behavior?
- Answer aloud and timed: Can you explain how you implement deny-by-default authorization and role-based access control in a REST API?
Technical Screening
reportedInitial technical assessment to evaluate your practical skills and experience.
What to demonstrate
- Initial technical assessment to evaluate your practical skills and experience
- Depth in Node.js
How to prepare
- Answer aloud and timed: What is your strategy for remediating OWASP and DISA STIG security findings in a production environment?
- Answer aloud and timed: How do you ensure your Node.js/TypeScript code remains maintainable and performant under heavy enterprise load?
Project-Based Interview
reportedFinal interview focusing on specific projects that reflect the work described in the job postings.
What to demonstrate
- Final interview focusing on specific projects that reflect the work described in the job postings
- Depth in Node.js
How to prepare
- Answer aloud and timed: How do you provide context to an AI coding agent to ensure the generated code meets strict security and project constraints?
- Answer aloud and timed: Describe a time you used an AI tool to refactor a complex module; how did you validate the result for correctness and security?
Behavioral Interview
reportedDiscussion of past experiences and how they align with the team-based delivery model.
What to demonstrate
- Discussion of past experiences and how they align with the team-based delivery model
- Depth in Node.js
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Highlight your clearance
If you have an active TS/SCI, ensure it is clearly stated on your resume and mentioned during your initial screening.
Focus on the "How
When discussing past work, explain the specific tools and methods you used to ensure security, such as how you handled private endpoints or managed identity.
Embrace the AI element
Be ready to discuss your experience with AI-assisted tools. Don't just say you use them—explain how you validate their output.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
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?
Identify the heaviest tenants in a five-minute window under memory pressure
The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.
Approach
- Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
- Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
- State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
- Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.
Follow-up
- The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
- Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?
Archive a resource graph without breaking live references or recursing
Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.
Approach
- Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
- Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
- Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
- Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
- The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
- The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?
How do you approach migrating an embedded database to Azure SQL without regressing system behavior?
How do you approach migrating an embedded database to Azure SQL without regressing system behavior?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
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?
Can you explain how you implement deny-by-default authorization and role-based access control in a REST API?
Can you explain how you implement deny-by-default authorization and role-based access control in a REST 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?
What is your strategy for remediating OWASP and DISA STIG security findings in a production environment?
What is your strategy for remediating OWASP and DISA STIG security findings in a production environment?
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 ensure your Node.js/TypeScript code remains maintainable and performant under heavy enterprise load
How do you ensure your Node.js/TypeScript code remains maintainable and performant under heavy enterprise load?
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 provide context to an AI coding agent to ensure the generated code meets strict security and projec
How do you provide context to an AI coding agent to ensure the generated code meets strict security and project constraints?
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?
Explain your process for designing a secure Azure landing zone with proper network segmentation.
Explain your process for designing a secure Azure landing zone with proper network segmentation.
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 infrastructure as code using Terraform or Bicep in a disconnected or air-gapped environment?
How do you manage infrastructure as code using Terraform or Bicep in a disconnected or air-gapped environment?
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 steps do you take to ensure high availability and disaster recovery for a mission-critical application?
What steps do you take to ensure high availability and disaster recovery for a mission-critical application?
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?
Exports duplicate a row range about once a week
Roughly once a week an export writes a file containing a duplicated range of rows. The affected job_run rows show attempt = 1, status = succeeded, one started_at, and a lease_owner naming a different host from the one whose logs show the job starting. Leases last 30 seconds and are heartbeated every 10 from inside the handler; lease_expires_at is computed on the worker and compared against the database's now(). Find the mechanism, and give a fix that holds even if you cannot fix the clocks.
Approach
- Start from the fact that eliminates the obvious answer. attempt = 1 means no retry was recorded, so this is not a re-run after failure; two workers ran the same row concurrently and the takeover path never touched the counter. lease_owner naming a host other than the one that started the job is the same statement from the other side.
- Enumerate the mechanisms that cause a premature takeover, then find the signal that separates them. Either the lease genuinely expired because the heartbeat did not fire, which is what happens when the heartbeat runs on the handler's own thread and the handler makes a long blocking call, or it only appeared expired because two clocks disagree, since lease_expires_at is written from the worker's clock and evaluated against the database's. The discriminator is the distribution: incidents clustered on the longest exports indict the heartbeat, incidents clustered on one host indict skew. Measure both, and measure each host's offset against the database directly.
- Read the reclaim query precisely. In PostgreSQL now() is transaction start time, not statement time, so a reclaimer holding a long transaction compares against an older timestamp than expected; clock_timestamp() is the statement-time function. This is worth ruling in or out before you redesign anything, because it changes which rows look expired.
- Remove the second clock rather than trying to synchronise it. Issue and extend the lease in the database, with lease_expires_at = now() + interval '30 seconds' in both the claim and the heartbeat, so exactly one clock is ever compared and worker skew stops mattering to this predicate.
Follow-up
- The displaced worker has already streamed half the file to object storage. What makes that side effect safe to repeat?
- You now count takeovers. What alert fires on that counter, and at what threshold?
Built from the rounds and topics Hyertek candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Hyertek loop
- Write out the reported sequence: TS/SCI Clearance Discussion, Technical Screening, Project-Based Interview, Behavioral 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 4 reported rounds, with the weakest marked.
02Work Node.js
- Spend the session on Node.js, which Hyertek candidates report being tested on.
- Write one worked example in Node.js and time yourself on it.
Deliverable: One timed worked example in Node.js.
03Work JavaScript/TypeScript
- Spend the session on JavaScript/TypeScript, which Hyertek candidates report being tested on.
- Write one worked example in JavaScript/TypeScript and time yourself on it.
Deliverable: One timed worked example in JavaScript/TypeScript.
04Work Express.js
- Spend the session on Express.js, which Hyertek candidates report being tested on.
- Write one worked example in Express.js and time yourself on it.
Deliverable: One timed worked example in Express.js.
05Answer out loud: Technical & Domain Expertise
- Answer aloud, timed: How do you approach migrating an embedded database to Azure SQL without regressing system behavior?
- Answer aloud, timed: Can you explain how you implement deny-by-default authorization and role-based access control in a REST API?
Deliverable: Spoken answers to 2 reported Technical & Domain Expertise question(s), under time.
06Answer out loud: AI-Assisted Development
- Answer aloud, timed: How do you provide context to an AI coding agent to ensure the generated code meets strict security and project constraints?
- Answer aloud, timed: Describe a time you used an AI tool to refactor a complex module; how did you validate the result for correctness and security?
Deliverable: Spoken answers to 2 reported AI-Assisted Development question(s), under time.
07Answer out loud: System Design & Infrastructure
- Answer aloud, timed: Explain your process for designing a secure Azure landing zone with proper network segmentation.
- Answer aloud, timed: How do you manage infrastructure as code using Terraform or Bicep in a disconnected or air-gapped environment?
Deliverable: Spoken answers to 2 reported System Design & Infrastructure 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 you used an AI tool to refactor a complex module; how did you validate the result for correctn
Describe a time you used an AI tool to refactor a complex module; how did you validate the result for correctness and security?
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 scenarios where an AI-generated solution fails to meet WCAG 2.1 AA accessibility or security
How do you handle scenarios where an AI-generated solution fails to meet WCAG 2.1 AA accessibility or security requirements?
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 situation where you had to explain a complex technical trade-off to a non-technical government stak
Describe a situation where you had to explain a complex technical trade-off to a non-technical government stakeholder.
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 us about a time you identified a critical security vulnerability before it reached production.
Tell us about a time you identified a critical security vulnerability before it reached production.
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 balance the need for rapid feature delivery with the rigorous documentation requirements of RMF and
How do you balance the need for rapid feature delivery with the rigorous documentation requirements of RMF and federal compliance?
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 you used an AI tool to refactor a complex module; how did you validate the result for correctness and security?
- 02
How do you handle scenarios where an AI-generated solution fails to meet WCAG 2.1 AA accessibility or security requirements?
- 03
Describe a situation where you had to explain a complex technical trade-off to a non-technical government stakeholder.
- 04
Tell us about a time you identified a critical security vulnerability before it reached production.
How much time should I spend preparing for the technical portion?
Given the hands-on nature of the role, spend significant time reviewing your past projects and identifying specific examples of how you handled database migrations or cloud security. Focus on the "why" behind your technical decisions.
Hyertek Software Engineer candidate reports ↗What is the company culture like?
Hyertek is a mission-driven, professional consulting environment. The culture values accountability, technical excellence, and the ability to work within the constraints of government requirements.
Hyertek Software Engineer candidate reports ↗How long is the typical interview process?
The process is designed to move as quickly as security vetting allows. You can expect multiple rounds of technical and behavioral discussion, usually concluding within a few weeks.
Hyertek Software Engineer candidate reports ↗What topics does Hyertek test in interviews?
Hyertek interviews most often cover Node.js, JavaScript/TypeScript, Express.js, REST APIs, and SQL Server / Azure SQL. The exact emphasis depends on the specific role you apply for.
Hyertek 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.
- 01Hyertek 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.
The Marlin Alliance Software Engineer Interview Guide
What The Marlin Alliance asks Software Engineer candidates, from reported rounds and questions.
Theinclab Software Engineer Interview Guide
What Theinclab asks Software Engineer candidates, from reported rounds and questions.
Telus Digital Software Engineer Interview Guide
What Telus Digital asks Software Engineer candidates, from reported rounds and questions.
Re:Build Manufacturing Software Engineer Interview Guide
What Re:Build Manufacturing asks Software Engineer candidates, from reported rounds and questions.