Kernel logo

Kernel Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 17 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
58.8% Positive experience

Which role are you interviewing for?

7 roles · 17 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Kernel.

Showing 4 of 17
Kernel logo
Kernel

Product Manager

Product · nearly a year ago

Mid Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral

The interview process was straightforward and efficient, with the interviewers clearly knowing what they were looking for. They were very direct in their questioning and super flexible with scheduling.

Confirmed questions1 question
  • Can you tell me about your past work experience?
Kernel logo
Kernel

Electronic Technician

Engineering · more than a year ago

Mid Difficult Negative experience No offer 4 rounds
Interview process
Technical screen Onsite Presentation Background check
Interview formats
Technical Coding Presentation Other

This was a long interview process with four interviews. The first two were with project managers, then an in-person one with the engineering and technician team, and finally with the CTO. There was a lot of repeated technical questions, which suggests poor communication between the interviewers. The process also dragged on for weeks, and it seemed like the job requirements kept changing, with no one agreeing on the role. I even got caught in the middle of an argument between two teammates about the technician's duties, which was uncomfortable. The interview style was a tough test of knowledge and character, which got tiring and felt condescending after a while. The soldering test was also thrown together quickly, with no proper tools like a wet sponge or cleaning pad for the iron. The solder tip was too big, and the engineer pointed to a tiny, hard-to-reach component, asking if I knew what it was. I identified it as an 0402 resistor, and he seemed impressed. Then he asked me to desolder and replace it, but the solder roll was too thick for fine-pitch work. I tried my best with the provided materials, but I should have spoken up about the unsuitable equipment. In the end, the five hours of interviews and thirty emails for this position felt inefficient, disorganized, and disrespectful of my time.

Confirmed questions4 questions
  • Can you handle using a precision screwdriver for a 10-hour period?
  • Explain how you would determine the spacing between conductive pathways on a multilayer PCB that transmits data to a custom ASIC microprocessor.
  • Do you know what that component is? (referring to an 0402 resistor)
Kernel logo
Kernel

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Technical

Had a chat with a recruiter and then went on to a technical interview. It was supposed to be for an HTML/CSS/JS role, but they asked me to build an app using React. I pointed out that React wasn't mentioned in the job description, and they replied, "yeah that's on us". Then, they actually updated the job description right there on the call while I was still talking to them.

Confirmed questions1 question
  • Could you build a Todo list application using React and Typescript?
Kernel logo
Kernel

Physics Modeler

Research

Staff Easy Negative experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

The interviewer was 7 minutes late for our 15-minute chat, leaving only 8 minutes for me to talk about myself. They kept cutting me off while I was describing my projects, seemingly to brag. The interviewer seemed to have no clue about what they were looking for, even asking about reconstructing brain activities from signals without understanding inverse scattering. It really makes you wonder about the company culture - all talk about high-level concepts to impress investors, but no real drive for research.

Confirmed questions2 questions
  • Can you tell me about yourself?
  • What's your background in coding?

Kernel Interview Questions

Quoted word for word from Kernel interview reports.

Do you know what that component is? (referring to an 0402 resistor)

Read reports

Explain how you would determine the spacing between conductive pathways on a multilayer PCB that transmits data to a custom ASIC microprocessor.

Read reports

Can you handle using a precision screwdriver for a 10-hour period?

Read reports

Could you build a Todo list application using React and Typescript?

Read report

Can you tell me about your research experience with fNIRS?

Read report

Tell me about your experience with human subjects research.

Read report

Formats, difficulty and experience

Across all 17 Kernel interview reports.

Interview formats

Technical 40%
Behavioral 34.3%
Other 8.6%
Coding 8.6%
Presentation 5.7%

Interview difficulty

Easy 11.8%
Average 76.5%
Difficult 11.8%

Candidate experience

Positive 58.8%
Negative 35.3%
Neutral 5.9%

Reports by job function

Research 8
Engineering 7
Product 1
Operations 1