
KISI Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 52 interview experiences · FREE TO READ
Which role are you interviewing for?
24 roles · 52 reportsCandidate interview experiences
First-hand accounts from people who interviewed at KISI.
Embedded Firmware Developer
The interview process was a good experience overall. It started with a recruiter call where the interviewer was friendly and shared a lot about the role and company. Following that, I was sent a technical task in C, which was quick to complete. The process continued with two more virtual interviews, one with the CTO and another with the team. It all went smoothly, leaving me with a positive impression of the company.
- Can you describe a difficult technical problem you encountered and how you resolved it?
Director of Support
I recently interviewed, and my experience was extremely disappointing and unprofessional. After an initial conversation with the recruiter, who expressed strong enthusiasm about my fit for the role, I was immediately asked to complete a case study. This request came before even meeting with the hiring manager, which was supposed to be the next step. They then indicated that if I submitted the case study by Monday, they would pass it along to the hiring manager with a promised turnaround of 1-2 days. I put in significant effort and submitted the assignment ahead of schedule. However, despite the recruiter’s previously prompt responses, I heard absolutely nothing back. I waited a few days—still nothing. I waited until the end of the week and reached out again, but I was completely ghosted. I followed up via email, sent messages on LinkedIn, and even reached out directly to multiple people, but received no response whatsoever. It’s now been nearly two weeks, and I have not received a single word acknowledging my assignment, let alone any feedback or updates on my candidacy. My conclusion? It feels like they used the case study, my 90 day plan, to get free consultative work and insights without any intention of moving forward in the hiring process. This behavior is not only unprofessional but also incredibly manipulative and it needs to stop. We need to call out companies that follow these shady practices!
- Can you outline a detailed 90-day plan to streamline support at the company, focusing on actionable quick wins that can be implemented immediately?
Revenue Operations Manager
The interview process was transparent and communication was timely at the start. I got good feedback on the technical task and the interview conversation. However, I spent a lot of time on a technical task that was supposed to be a key part of one of my final interviews. It felt abrupt to be cut before that interview, especially with the COO interview coming up. This happened even before I could discuss my technical work. The way and timing of this decision felt disrespectful of the effort candidates put in. Candidates spend a lot of time and resources preparing for interviews and tasks, especially when these tasks are for later stages. Closing positions just before scheduled interviews, particularly with senior management, leads to a bad candidate experience. Being considerate, respectful, and communicating well are super important for candidates. I hope future processes are more mindful of candidates' time and effort.
- What high-level questions were asked?
- Could you elaborate on the technical task and the structure of its associated questions?
Backend Developer
I was contacted by a recruiter about a RoR backend role, and they didn't ask for my CV, just some standard questions. Then, I had to complete a tech challenge over the weekend. After that, I had a technical interview with the CTO himself, which was surprisingly only 30 minutes. He asked a few questions about my solution, and that was it. When I asked him about the kind of candidate he was looking for, he could only describe a senior developer who gets things done. He had to leave midway through my questions for another meeting. The whole vibe felt rushed and unwelcoming. They rejected me, saying others were a better fit, but couldn't explain what they were looking for, and they ignored my request for feedback. Not a great experience.
- What impact would changing this element have?
- What was the reasoning behind your approach in the tech challenge?
- Could you elaborate on the qualities you seek in a senior developer?
KISI Interview Questions
Quoted word for word from KISI interview reports.
“Can you explain JavaScript hoisting?”
Read reports →“What are some ways to optimize React components?”
Read reports →“What impact would changing this element have?”
Read reports →“Imagine you're on a narrow mountain road in the snow, and people are trying to make you crash by throwing things. What would you do, and how would you react emotionally?”
Read reports →“Can you clarify the division of responsibilities between a Product Manager and a UX/UI Designer?”
Read report →“Why do you think Kisi would be a good fit?”
Read report →“How do you approach following up with a prospect after losing a deal?”
Read report →“Can you build a background job system for Rails using Google Pub-Sub, following a detailed set of specifications?”
Read report →“Do you enjoy doing this on a daily basis? Because it wouldn't be interesting to have someone who is bored and not excited doing this.”
Read report →Formats, difficulty and experience
Across all 52 KISI interview reports.