Real, anonymous reports from people who interviewed for Software Engineer at Khan Academy, newest first and distilled into what to expect across the loop.
After a recruiter screening, I interviewed with the hiring manager. The overall vibe felt off: the hiring manager came across pretty disengaged and not very interested during the conversations, and even when I could clearly connect my experience to what the role needed, I still ended up being rejected. What stuck with me most was how the process didn’t feel like it was evaluating me in good faith, even though I had a professional background that genuinely fit the lens they claimed to care about.
My interview process went smoothly right up until the end. The only thing that really threw me was that they mixed up when my technical interviews were supposed to happen, so I got surprised by the timing and had to quickly recalibrate. Other than that, I felt like I was treated fairly and the people involved were genuinely solid—helpful, professional, and welcoming.
The interview process typically begins with a recruiter screening, followed by a mix of technical and behavioral interviews, often including a project component. Candidates reported varying timelines, with some experiencing delays between rounds and others noting a more streamlined approach.
Candidates faced a variety of technical assessments, including coding challenges and project-based evaluations, with a mix of HackerRank-style questions and open-ended design discussions. The emphasis on unit testing and specific coding approaches was noted as a point of contention by some candidates.
Behavioral interviews were a significant part of the process, focusing on candidates' past experiences and decision-making processes. Many candidates felt that these discussions were designed to gauge cultural fit and collaboration skills rather than just technical prowess.
Candidate experiences varied widely regarding interviewer engagement, with some reporting friendly and supportive interactions, while others felt that interviewers were disengaged or unprepared. Communication about the process and decisions was also a common point of frustration.
The overall difficulty of the interviews was perceived as fair but challenging, with candidates often feeling that their performance was influenced by the interview format and interviewer behavior. Many candidates did not receive offers, leading to mixed feelings about the experience.
Candidates wished they had better clarity on what to expect, especially regarding the technical assessments and interview styles. Preparing for both coding and behavioral questions, along with understanding the project expectations, was highlighted as crucial.