
Kong Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Kong.
Senior Software Engineer
The interview process was pretty clear and organized. It mostly focused on my past work. It started with a Hiring Manager screen, then a Take Home Assignment. After that, there was a Technical Screen that built on the take-home and asked deep questions about my experience. Then, I had 2 rounds with Product Managers and a final round with the Head of Engineering. The recruiter was really helpful and communicative all the way through. The whole thing took about a month.
- Can you tell me about proxies?
- What do you understand by Observability?
- What are AI native concepts?
Software Engineer
First I spoke with a recruiter who told me about the company and the interview process. Then I had a call with an engineering manager who described the product, team, and tech. After that, things got weird. I had a panel interview with some engineers where I was given documents about requirements and asked to find gaps. They seemed uninterested in my questions. I had a week to complete this assignment. The next interview was supposed to be a review of my assignment, with questions and a technical discussion. Instead, it was mostly aggressive, unrelated technical questioning, including random algorithm, language-specific, framework-specific (even though they knew I hadn't used it), and architecture questions. I wasn't warned about the format, making preparation impossible. The other engineers were hostile, seeming more interested in tripping me up than evaluating me.
No confirmed questions were included in this interview report.
Software Developer
Had a 1-hour meeting with the hiring manager, then a 1-hour session with the recruiter. After that, there were 2 hours of interviews with the team, consisting of two interviewers at a time. These 2-on-1s can be tough as you can't really connect with either interviewer. It ended after that because I didn't do well in the first two stages. The third interview got cancelled. Failed interviews in 1st and 2nd stages. Ended there because failed interviews in 1st and 2nd stages.
- Can you describe your general approaches to JavaScript?
- Implement pagination for the provided project, noting that it will be a screen share exercise and you should use VSCode.
Kong Software Engineer Interview Questions
Quoted word for word from Kong interview reports.
“Regarding DOM manipulation, how does JavaScript interact with elements, like adding or removing them?”
Read reports →“What are the tradeoffs between client-side and server-side sorting and filtering searches using JavaScript?”
Read reports →“What are some assumptions you'd need to consider regarding list size, pagination, etc. when comparing client-side versus server-side sorting and filtering?”
Read reports →“What are some common design patterns for concurrency and parallelism, and how would you implement them?”
Read reports →“Implement pagination for the provided project, noting that it will be a screen share exercise and you should use VSCode.”
Read report →“Could you write code to implement an authentication library?”
Read report →“Can you build a services API from a given user story?”
Read report →“Describe how to build a project from scratch.”
Read report →“How would you design a process to ensure users can access X even if they don't receive an email for Y?”
Read report →Formats, difficulty and experience
Across all 16 Kong interview reports.