📎 Webclip
I failed an interview because of an algorithm
The post walks through a full hiring process, from referral and HR screens to manager interviews and a final technical round. The author says he felt confident through most stages, especially the soft-skills interviews and the technical quiz.
Reading notes#
- The process started with a referral from a friend, followed by an HR call about experience, skills, and current work.
- The managers focused on soft skills such as conflict handling, technical decisions, and top-down decisions.
- The only feedback from that stage was that he seemed “more of a follower” than a leader.
- In the next HR call, the same answers were repeated and accepted, and the technical interview was scheduled.
- The technical interview covered JavaScript, CSS, testing, state management, React, and HTTP.
- He answered questions about
var,let, andconst, object freezing, DOM events, event delegation, RAF, CSS display values, vertical centering, HTTP methods, and status codes. - The coding challenge asked for a function that sorts version strings from highest to lowest.
- His first solution used default string sort followed by reverse, which passed one test but failed cases with different version lengths.
- He ran out of time while trying to normalize version lengths and compare them block by block.
- The rejection feedback said the devs liked his communication and most answers, but felt he did not do well on the final problem.
- The author argues that interview performance and job performance are not the same thing, and that failing an interview does not make someone a bad developer.
- He ends by saying the experience pushed him to prepare more broadly for future interviews, including practice on coding challenge platforms.
