cswork / libraryOpen practice workspace

Interview guides · Harmonic Security

Harmonic Security Software Engineer Interview Guide

Harmonic Security Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

At Harmonic Security, a Software Engineer plays a pivotal role in shaping the future of data security in the era of generative AI. As organizations rapidly adopt large language models and AI-driven tools, securing sensitive enterprise data without stifling innovation has become one of the most critical challenges in technology. You will be responsible for building the highly performant, secure, and intuitive applications that allow enterprises to monitor, manage, and secure their data footprints in real time. Your work will directly impact how security teams interact with complex security telemetry.

This guide is scoped to a Software Engineer candidate at Harmonic Security.

Focus areas

  • JavaScript
  • React
  • CSS

The Harmonic Security interview process

Harmonic Security candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Initial Screening Call

The process begins with an initial call to assess your background and fit for the role.

What to demonstrate

  • The process begins with an initial call to assess your background and fit for the role
  • Depth in JavaScript

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 Discussion

A focused discussion around frontend concepts and your past engineering experiences.

What to demonstrate

  • A focused discussion around frontend concepts and your past engineering experiences
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: How does asynchronous execution work in JavaScript, and how would you handle multiple concurrent API requests efficiently?
  • Answer aloud and timed: Explain the concept of event delegation in JavaScript and when you would choose to use it over standard event binding.

Technical Panel

A comprehensive technical panel that includes a deep-dive project walkthrough and a collaborative whiteboarding session.

What to demonstrate

  • A comprehensive technical panel that includes a deep-dive project walkthrough and a collaborative whiteboarding session
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: Design a complex, multi-step user registration form. What local and global state structures would you use, and how would you handle validation across steps?
  • Answer aloud and timed: For the multi-step form design, what would the JSON payload look like that you send to the backend API, and what response structure do you expect in case of partial validation failures?

Final Conversation

A discussion with a founder or senior leader about team alignment, company vision, and career goals.

What to demonstrate

  • A discussion with a founder or senior leader about team alignment, company vision, and career goals
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: How would you design a frontend state management system for a real-time security alert dashboard that receives high-frequency updates via WebSockets?
  • Answer aloud and timed: Walk us through a software project you are exceptionally proud of. What was the core technical challenge, and how did you resolve it?

Where candidates lose points

Think out loud during the design phase

In the system design and whiteboarding exercises, the interviewers care deeply about your thought process. Talk through your assumptions, explain why you are choosing a particular data structure, and discuss any trade-offs you are making in real time.

Be honest about past project failures

When discussing a project you are proud of, do not hesitate to talk about what went wrong. Showing that you can identify architectural mistakes and explain how you would fix them today is a massive indicator of senior engineering maturity.

Brush up on CSS fundamentals

Do not overlook core CSS concepts. You may be asked direct questions about positioning, layout models, and responsive design, so make sure you can explain these concepts clearly without relying on utility frameworks.

Avoid over-engineering your solutions during the whiteboarding exercise

Start with the simplest architecture that meets the core requirements, and then explain how you would scale or optimize it if given more time.

Questions & practice

Explain how the virtual DOM works in React and how you would diagnose a performance bottleneck in a deeply nes

Medium · Frontend & Core Languages

Explain how the virtual DOM works in React and how you would diagnose a performance bottleneck in a deeply nested component tree.

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

How does asynchronous execution work in JavaScript, and how would you handle multiple concurrent API requests

Medium · Frontend & Core Languages

How does asynchronous execution work in JavaScript, and how would you handle multiple concurrent API requests efficiently?

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?

Explain the concept of event delegation in JavaScript and when you would choose to use it over standard event

Medium · Frontend & Core Languages

Explain the concept of event delegation in JavaScript and when you would choose to use it over standard event binding.

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

How do you approach working with ambiguous or incomplete product specifications?

Medium · Cultural Alignment & Startup Fit

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?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

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

  1. 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.
  2. 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.
  3. 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.
  4. 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?

Keep soft-deleted accounts from blocking re-registration

Easy · soft delete · unique constraints · engine differences

app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.

Approach

  1. Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
  2. Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
  3. For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
  4. State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.

Follow-up

  • A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
  • How do you honour an erasure request while resource_revision.actor_user_id still references this table?

Design a complex, multi-step user registration form. What local and global state structures would you use, and

Medium · System & Form Design

Design a complex, multi-step user registration form. What local and global state structures would you use, and how would you handle validation across steps?

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?

For the multi-step form design, what would the JSON payload look like that you send to the backend API, and wh

Medium · System & Form Design

For the multi-step form design, what would the JSON payload look like that you send to the backend API, and what response structure do you expect in case of partial validation failures?

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 design a frontend state management system for a real-time security alert dashboard that receives

Medium · System & Form Design

How would you design a frontend state management system for a real-time security alert dashboard that receives high-frequency updates via WebSockets?

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?

Walk us through a software project you are exceptionally proud of. What was the core technical challenge, and

Medium · Project Walkthrough & Technical Reflecti

Walk us through a software project you are exceptionally proud of. What was the core technical challenge, and how did you resolve it?

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?

Looking back at your proudest project, what architectural decisions turned out to be mistakes, and how would y

Medium · Project Walkthrough & Technical Reflecti

Looking back at your proudest project, what architectural decisions turned out to be mistakes, and how would you refactor them today?

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?

Why are you interested in working in the cybersecurity space, and specifically at Harmonic Security?

Medium · Cultural Alignment & Startup Fit

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?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

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

  1. 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.
  2. 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.
  3. 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.
  4. 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?

Suggested practice checklist

Built from the rounds and topics Harmonic Security candidates report.

Day 1 — Map the Harmonic Security loop

  • Write out the reported sequence: Initial Screening Call, Technical Discussion, Technical Panel, Final Conversation.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work JavaScript

  • Spend the session on JavaScript, which Harmonic Security candidates report being tested on.
  • Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 3 — Work React

  • Spend the session on React, which Harmonic Security candidates report being tested on.
  • Write one worked example in React and time yourself on it.

Deliverable: One timed worked example in React.

Day 4 — Work CSS

  • Spend the session on CSS, which Harmonic Security candidates report being tested on.
  • Write one worked example in CSS and time yourself on it.

Deliverable: One timed worked example in CSS.

Day 5 — Answer out loud: Frontend & Core Languages

  • Answer aloud, timed: Explain how the virtual DOM works in React and how you would diagnose a performance bottleneck in a deeply nested component tree.
  • Answer aloud, timed: What is the difference between relative, absolute, and fixed positioning in CSS, and how do you handle responsive layouts?

Deliverable: Spoken answers to 2 reported Frontend & Core Languages question(s), under time.

Day 6 — Answer out loud: System & Form Design

  • Answer aloud, timed: Design a complex, multi-step user registration form. What local and global state structures would you use, and how would you handle validation across steps?
  • Answer aloud, timed: For the multi-step form design, what would the JSON payload look like that you send to the backend API, and what response structure do you expect in case of partial validation failures?

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

Day 7 — Answer out loud: Project Walkthrough & Technical Reflection

  • Answer aloud, timed: Walk us through a software project you are exceptionally proud of. What was the core technical challenge, and how did you resolve it?
  • Answer aloud, timed: Looking back at your proudest project, what architectural decisions turned out to be mistakes, and how would you refactor them today?

Deliverable: Spoken answers to 2 reported Project Walkthrough & Technical Reflection question(s), under time.

Behavioural preparation

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

What is the difference between relative, absolute, and fixed positioning in CSS, and how do you handle respons

Medium · Frontend & Core Languages

What is the difference between relative, absolute, and fixed positioning in CSS, and how do you handle responsive layouts?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a time when you had to balance technical debt with the pressure to deliver a feature quickly. How did

Medium · Project Walkthrough & Technical Reflecti

Describe a time when you had to balance technical debt with the pressure to deliver a feature quickly. How did you make the trade-off?

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a situation where you had a strong technical disagreement with a teammate. How did you resolve it and

Medium · Cultural Alignment & Startup Fit

Describe a situation where you had a strong technical disagreement with a teammate. How did you resolve it and move the project forward?

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?