Zendar Software Engineer Interview Guide

The 60-second brief

A Software Engineer at Zendar plays a pivotal role in shaping the future of autonomous vehicle perception and radar technology. By developing high-performance software that processes complex sensor data, you will directly contribute to making self-driving systems safer and more reliable in all weather conditions. The engineering team at Zendar is tasked with bridging the gap between raw hardware capabilities and sophisticated software algorithms, solving challenges that lie at the intersection of signal processing, machine learning, and systems engineering. In this role, your work will directly impact the development of Zendar's high-resolution radar imaging and sensor fusion pipelines. You will be responsible for building, optimizing, and deploying software that processes massive streams of environmental data in real time.

This guide is scoped to a Software Engineer candidate at Zendar.

Focus areas

• Sensor Fusion
• System Design
• Localization

The Zendar interview process

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

Recruiter Conversation

Initial discussion with a recruiter or hiring manager about your background and interest in Zendar.

What to demonstrate

• Initial discussion with a recruiter or hiring manager about your background and interest in Zendar
• Depth in Sensor Fusion

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 Coding Assessment

Live technical assessments focusing on practical application and solving realistic engineering problems.

What to demonstrate

• Live technical assessments focusing on practical application and solving realistic engineering problems
• Depth in Sensor Fusion

How to prepare

• Answer aloud and timed: Walk through a past project where you had to parse, transform, and visualize complex multidimensional data.
• Answer aloud and timed: How do you handle state management and rendering efficiency when dealing with rapidly updating streams of sensor data?

Onsite Interview

Intensive onsite interview with multiple segments including system design, conversations with leadership, and practical exercises.

What to demonstrate

• Intensive onsite interview with multiple segments including system design, conversations with leadership, and practical exercises
• Depth in Sensor Fusion

How to prepare

• Answer aloud and timed: Design a system layout and integration pipeline that combines raw radar data with camera feeds for real-time object detection.
• Answer aloud and timed: How would you structure a low-latency data ingestion pipeline to handle high-throughput sensor inputs without dropping frames?

Where candidates lose points

Clarify Ambiguous Requirements

Some technical rounds may involve real-world internal issues where requirements are intentionally left vague. Do not hesitate to ask clarifying questions and state your assumptions clearly before writing code.

Do not jump straight into coding during your technical rounds

Take a moment to discuss your proposed architecture, state your assumptions, and align with your interviewers on the scope of the problem first.

Highlight Hardware-Software Co-design

Showing an awareness of hardware constraints, such as GPU utilization limits, memory bandwidth, or sensor latency, will make your technical answers stand out.

Questions & practice

Build a component (e.g., using React or your framework of choice) that dynamically renders a table with a spec

Medium · Technical & Coding Questions

Build a component (e.g., using React or your framework of choice) that dynamically renders a table with a specified number of rows and columns based on real-time input.

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?

Explain how you would optimize a performance-critical algorithm to run efficiently on resource-constrained har

Medium · Technical & Coding Questions

Explain how you would optimize a performance-critical algorithm to run efficiently on resource-constrained hardware or GPUs.

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?

Walk through a past project where you had to parse, transform, and visualize complex multidimensional data.

Medium · Technical & Coding Questions

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?

Write the update path that detects a concurrent edit

Medium · optimistic concurrency · transactional outbox · audit history

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

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

Denormalise tenant onto revisions and backfill it live

Hard · denormalisation · online migration · backfill

resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.

Approach

1. Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
2. Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
3. Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
4. Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.

Follow-up

• The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
• How do you verify the backfill actually finished, given rows are still being inserted while it runs?

Design a system layout and integration pipeline that combines raw radar data with camera feeds for real-time o

Medium · System Design & Integration Questions

Design a system layout and integration pipeline that combines raw radar data with camera feeds for real-time object detection.

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

How would you structure a low-latency data ingestion pipeline to handle high-throughput sensor inputs without

Medium · System Design & Integration Questions

How would you structure a low-latency data ingestion pipeline to handle high-throughput sensor inputs without dropping frames?

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?

Describe your approach to designing a modular software architecture that allows different sensor fusion algori

Medium · System Design & Integration Questions

Describe your approach to designing a modular software architecture that allows different sensor fusion algorithms to be swapped out dynamically.

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

How would you manage synchronization and latency issues when fusing data from sensors with different frame rat

Medium · System Design & Integration Questions

How would you manage synchronization and latency issues when fusing data from sensors with different frame rates and clocks?

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?

Every query on one table stalls for forty seconds mid-deploy

Medium · lock contention · ddl · migrations

During a release on PostgreSQL, every query touching resource times out for about 40 seconds and then recovers with no intervention. The release ran one migration, ALTER TABLE resource ADD COLUMN archived_reason TEXT, and the migration log shows it completing in 6 ms. Unrelated tables showed no change in error rate. Explain how a 6 ms statement caused a 40-second stall, give the ordered checks you would run on a live system to confirm it, and give the migration procedure that prevents a repeat.

Approach

1. Separate the statement's duration from the lock's duration. ADD COLUMN with no default is a catalogue-only change and genuinely runs in milliseconds, but it requires ACCESS EXCLUSIVE, and it cannot acquire that until every transaction already touching the table has finished.
2. Account for the queueing, which is the part that surprises people. A lock request that is waiting blocks later requests for conflicting modes behind it rather than letting them overtake, so one long-open transaction holds the DDL and the DDL holds all the traffic. The stall length is set by the longest open transaction, not by the size of the change.
3. Confirm on a live system in this order: pg_stat_activity for that table ordered by xact_start, looking for the oldest transaction and specifically for state = idle in transaction; then pg_locks where granted = false to find the waiter; then join them on pid to name blocker and blocked. pg_blocking_pids() does that join for you and is the fastest single call.
4. Prevent rather than merely time it better. Set lock_timeout to a second or two on the migration session so the DDL abandons the queue after a bounded wait and is retried, instead of holding it for as long as the oldest transaction lives. Be exact about what that buys: queries arriving during the wait still queue behind the pending ACCESS EXCLUSIVE request, so each attempt costs them up to one lock_timeout of added latency. The outage goes from 40 seconds to about one second per attempt, not to zero. Also run migrations away from deploy-time peaks, and put a statement timeout and an idle-in-transaction timeout on the analytics role that opens the long transactions.

Follow-up

• The same release also wants NOT NULL on that column. What is the sequence that gets there without a long lock?
• Your lock_timeout retry fails ten times in a row because the analytics transaction is always open. What do you change?

Suggested practice checklist

Built from the rounds and topics Zendar candidates report.

Day 1 — Map the Zendar loop

• Write out the reported sequence: Recruiter Conversation, Technical Coding Assessment, Onsite Interview.
• For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

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

Day 2 — Work Sensor Fusion

• Spend the session on Sensor Fusion, which Zendar candidates report being tested on.
• Write one worked example in Sensor Fusion and time yourself on it.

Deliverable: One timed worked example in Sensor Fusion.

Day 3 — Work System Design

• Spend the session on System Design, which Zendar candidates report being tested on.
• Write one worked example in System Design and time yourself on it.

Deliverable: One timed worked example in System Design.

Day 4 — Work Localization

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

Deliverable: One timed worked example in Localization.

Day 5 — Answer out loud: Technical & Coding Questions

• Answer aloud, timed: Build a component (e.g., using React or your framework of choice) that dynamically renders a table with a specified number of rows and columns based on real-time input.
• Answer aloud, timed: Explain how you would optimize a performance-critical algorithm to run efficiently on resource-constrained hardware or GPUs.

Deliverable: Spoken answers to 2 reported Technical & Coding Questions question(s), under time.

Day 6 — Answer out loud: System Design & Integration Questions

• Answer aloud, timed: Design a system layout and integration pipeline that combines raw radar data with camera feeds for real-time object detection.
• Answer aloud, timed: How would you structure a low-latency data ingestion pipeline to handle high-throughput sensor inputs without dropping frames?

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

Day 7 — Answer out loud: Behavioral & Background Questions

• Answer aloud, timed: Why are you interested in working on radar technology and sensor fusion at Zendar?
• Answer aloud, timed: Tell me about a time you had to debug a complex, ambiguous technical issue with very little documentation. How did you approach it?

Deliverable: Spoken answers to 2 reported Behavioral & Background Questions question(s), under time.

Behavioural preparation

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

How do you handle state management and rendering efficiency when dealing with rapidly updating streams of sens

Medium · Technical & Coding Questions

How do you handle state management and rendering efficiency when dealing with rapidly updating streams of sensor data?

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?

Why are you interested in working on radar technology and sensor fusion at Zendar?

Medium · Behavioral & Background Questions

Approach

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

Follow-up

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

Tell me about a time you had to debug a complex, ambiguous technical issue with very little documentation. How

Medium · Behavioral & Background Questions

Tell me about a time you had to debug a complex, ambiguous technical issue with very little documentation. How did you approach it?

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?

Walk me through your resume and highlight a project where you had to collaborate closely with cross-functional

Medium · Behavioral & Background Questions

Walk me through your resume and highlight a project where you had to collaborate closely with cross-functional teams, such as hardware or systems engineers.

Approach

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

Follow-up

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

How do you handle working in a fast-paced environment where hardware limitations or system requirements might

Medium · Behavioral & Background Questions

How do you handle working in a fast-paced environment where hardware limitations or system requirements might change rapidly?

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?