cswork / libraryOpen practice workspace

Interview guides · Kernel

Kernel Software Engineer Interview Guide

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

The 60-second brief

As a Software Engineer at Kernel, you will work at the absolute frontier of neurotechnology. Kernel is pioneering non-invasive brain-computer interfaces (BCIs) to record and translate high-fidelity brain activity. In this role, you are not just writing standard application code; you are building the critical software infrastructure that interfaces with advanced physical hardware, processes massive streams of real-time neural data, and presents complex scientific insights in an intuitive way. Your work directly impacts the speed and accuracy with which researchers and clinicians can interpret brain signals. Whether you are optimizing low-level data ingestion pipelines, implementing sophisticated signal processing algorithms, or building responsive web interfaces for data visualization, your contributions are vital to unlocking the mysteries of the human brain.

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

Focus areas

  • API Development
  • Observability
  • Frontend Engineering

The Kernel interview process

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

Phone Screen

Initial call to discuss your background, career goals, and alignment with the company’s mission.

What to demonstrate

  • Initial call to discuss your background, career goals, and alignment with the company’s mission
  • Depth in API Development

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 Screening

Assessment involving practical coding or a deep dive into your domain expertise.

What to demonstrate

  • Assessment involving practical coding or a deep dive into your domain expertise
  • Depth in API Development

How to prepare

  • Answer aloud and timed: Walk me through how you would handle memory management when processing large multi-gigabyte datasets in memory.
  • Answer aloud and timed: Design a basic caching mechanism for frequently accessed neural signal records.

Panel Interview

Comprehensive video conference interview with engineering and cross-functional teams discussing experiences and problem-solving.

What to demonstrate

  • Comprehensive video conference interview with engineering and cross-functional teams discussing experiences and problem-solving
  • Depth in API Development

How to prepare

  • Answer aloud and timed: How would you approach reconstructing brain activities or physical source signals from a set of noisy, measured sensor signals?
  • Answer aloud and timed: What techniques would you use to filter out high-frequency noise from a real-time data stream?

Where candidates lose points

Clarify requirements immediately

When given a coding or design prompt, do not jump straight into writing code. Ask clarifying questions to understand the constraints, input sizes, and expected outputs. This shows a methodical, engineering-first mindset.

Focus on trade-offs

Whenever you make a technical decision (such as choosing a specific data structure or architectural pattern), explicitly explain the trade-offs to your interviewer. Discussing time complexity versus memory usage is highly valued.

Arguing past a hint

When the interviewer asks what happens for a particular input or floats a different data structure, stop and take it seriously; it is almost always a correction rather than idle curiosity. Talking over it converts a recoverable wrong turn into a data point about how you handle review.

Questions & practice

Explain how you would optimize the runtime of a data pipeline processing real-time streaming data.

Medium · Practical Systems & Data Structures

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?

Which data structure would you choose to store rapidly updating sensor coordinates, and why?

Medium · Practical Systems & Data Structures

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 me through how you would handle memory management when processing large multi-gigabyte datasets in memory

Medium · Practical Systems & Data Structures

Walk me through how you would handle memory management when processing large multi-gigabyte datasets in memory.

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?

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?

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?

Design a basic caching mechanism for frequently accessed neural signal records.

Medium · Practical Systems & Data Structures

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 approach reconstructing brain activities or physical source signals from a set of noisy, measure

Medium · Signal Processing & Domain Mathematics

How would you approach reconstructing brain activities or physical source signals from a set of noisy, measured sensor signals?

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?

What techniques would you use to filter out high-frequency noise from a real-time data stream?

Medium · Signal Processing & Domain Mathematics

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?

Explain the concept of inverse scattering or signal deconvolution in the context of wave physics or imaging.

Medium · Signal Processing & Domain Mathematics

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?

How do you manage complex, highly dynamic state in a single-page application?

Medium · Frontend & Application Development

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?

Walk me through how you would build a highly responsive chart that renders thousands of data points in real ti

Medium · Frontend & Application Development

Walk me through how you would build a highly responsive chart that renders thousands of data points in real time.

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?

What are the performance implications of rendering large datasets in React, and how do you mitigate them?

Medium · Frontend & Application Development

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?

How do you structure your CSS and HTML to ensure a clean, maintainable, and responsive design?

Medium · Frontend & Application Development

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?

One log partition stops advancing while the others drain

Easy · poison message · head-of-line blocking · consumer lag

Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.

Approach

  1. Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
  2. Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
  3. Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
  4. Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.

Follow-up

  • The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
  • How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?

Suggested practice checklist

Built from the rounds and topics Kernel candidates report.

Day 1 — Map the Kernel loop

  • Write out the reported sequence: Phone Screen, Technical Screening, Panel 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 API Development

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

Deliverable: One timed worked example in API Development.

Day 3 — Work Observability

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

Deliverable: One timed worked example in Observability.

Day 4 — Work Frontend Engineering

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

Deliverable: One timed worked example in Frontend Engineering.

Day 5 — Answer out loud: Practical Systems & Data Structures

  • Answer aloud, timed: Explain how you would optimize the runtime of a data pipeline processing real-time streaming data.
  • Answer aloud, timed: Which data structure would you choose to store rapidly updating sensor coordinates, and why?

Deliverable: Spoken answers to 2 reported Practical Systems & Data Structures question(s), under time.

Day 6 — Answer out loud: Signal Processing & Domain Mathematics

  • Answer aloud, timed: How would you approach reconstructing brain activities or physical source signals from a set of noisy, measured sensor signals?
  • Answer aloud, timed: What techniques would you use to filter out high-frequency noise from a real-time data stream?

Deliverable: Spoken answers to 2 reported Signal Processing & Domain Mathematics question(s), under time.

Day 7 — Answer out loud: Frontend & Application Development

  • Answer aloud, timed: How do you manage complex, highly dynamic state in a single-page application?
  • Answer aloud, timed: Walk me through how you would build a highly responsive chart that renders thousands of data points in real time.

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

Behavioural preparation

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

How do you handle missing or corrupted data points in a continuous time-series dataset?

Medium · Signal Processing & Domain Mathematics

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 to work with a teammate who had a fundamentally different technical opinion

Medium · Behavioral & Situational Alignment

Describe a situation where you had to work with a teammate who had a fundamentally different technical opinion. How did you resolve 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?

Tell me about a time when a project's requirements changed midway through development. How did you adapt?

Medium · Behavioral & Situational Alignment

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?

Give an example of a difficult technical bug you encountered in your career. How did you diagnose and solve it

Medium · Behavioral & Situational Alignment

Give an example of a difficult technical bug you encountered in your career. How did you diagnose and solve 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?

How do you prioritize your tasks when working in a fast-paced environment with competing deadlines?

Medium · Behavioral & Situational Alignment

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?