The Ultimate 'I Wrote the Library' Interview Fail
Description
A screenshot of a tweet from Jens Ravens (@JensRavens) on a light-themed Twitter interface. The text of the tweet reads: "Last year I got rejected during a job interview for 'not understanding' the concepts of a certain iOS library. What the interviewer didn't know: I wrote that thing. I actually had a lot of fun during that interview 😂". This meme captures the ultimate ironic failure of a technical interview. The humor lies in the supreme confidence and ignorance of the interviewer who incorrectly evaluates the actual author of the technology in question. It's a powerful anecdote that resonates with experienced developers who have often faced interviewers with superficial knowledge or rigid, textbook-based evaluation criteria. The story highlights the flaws in the hiring process, where expertise can be overlooked due to the interviewer's own incompetence
Comments
7Comment deleted
This is the only known case where a pull request to fix a candidate's understanding would require the interviewer to approve their own deletion
Got rejected for “not understanding” the iOS library that still has my Git sign-off in the README - turns out some interview loops just run `curl answer-key | sh` instead of `git blame`
The ultimate Dunning-Kruger reversal: when your interviewer confidently explains your own library's architecture back to you incorrectly, and you realize the real test is maintaining composure while they gaslight you about code you've been maintaining for years
The ultimate proof that technical interviews are broken: when you can fail to demonstrate understanding of your own library because the interviewer's mental model is so rigid they can't recognize the creator's deeper, more nuanced perspective. It's like Linus Torvalds getting rejected from a Linux kernel position for 'not understanding process scheduling' because he explained it differently than the interviewer's bootcamp notes
If the author of your iOS library fails your panel, you’re not assessing skill - you’re load‑testing your trivia cache
Tech interviews: where library maintainers fail the 'explain your own API' pop quiz because interviewers skip the commit history
Rejected for “not understanding” an iOS library I wrote - turns out their hiring bar was linearizability with a Medium post, not correctness