I applied online. The process took 8 weeks.
The interview process I went through was broken up into several parts: 1. Initial ~30min screening call. Nothing out of the ordinary here, mostly just ensuring the job role was right for both parties, talking about experience, salary expectations, etc. 2. 1hr interview with an engineering director, going over my area of interest & expertise, how I'd solve specific problems, etc. 3. 1hr interview with potential colleagues. A coding challenge was presented in this interview (for a take-home project) and was then opened up for questions & discussion. At least for me, the coding challenge was not an overwhelming amount of work given the allowed timeframe. 4. 1hr interview with potential colleagues. This time was spent going over the coding challenge, while talking about a variety of topics like design patterns, reliability, scalability, what could have been done differently, etc.
How would you go about diagnosing performance problems in production (among many other observability questions)?
What are your opinions on database modeling & performance considerations?
What are the common concurrency/parallelism design patterns, and how would one go about implementing them?
The following metrics were computed from 13 interview experiences for the Kong Senior Software Engineer role.
Kong's interview process for their Senior Software Engineer roles is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Kong's Senior Software Engineer interview process.