SwitchUpCB published "I called my Technical Interviewer a LOSER" on Medium.
I called my Technical Interviewer a LOSER
How this FAANG interviewer wasted my time and effort in LIFE.
Another day. Another FAANG interview. You know the drill…
The Phone Interview
I started the day of my phone interview out like any other day. Wake up. Tune into the weather channel. Except, I’m a remote worker, so I don’t watch it for the weather, if you know what I’m saying.
My routine was going well until I remembered, “Oh yeah, I have a FAANG interview today.” Then, I received a notification from my calendar app reminding me that my interview wasn’t just “today” but in like 5 minutes.
Oh f*ck!
So what started as a soft, warm day became one where coffee was replaced with a raging adrenaline rush: I ran to my office, turned on my computer, then ran to my bedroom to put on my remote work attire. While searching for my pants, I heard a ring from the office.
Sh*t.
At that moment, I had a few seconds to decide what to do: I didn’t want to risk missing the call, so I just decided to run to my office and answer the video call without pants on. I mean, this is a remote call, so what’s the worst that could happen?
Oh my gosh!
The recruiter was a woman. Not just any woman, either. Like, you expect these recruiters to have a space complexity of O(1), but her’s were O(n^n). They were so big! I adjusted my attached webcam so it would look like I was looking into her eyes the entire call.
All was going well until my brain decided to go monke mode: My you know what was so hard it was bumping against the bottom of my desk. And as a “problem solver who gets things done”, this was a problem I had to solve.
I just started jerkin’ off…
I thought the interview was going well until the recruiter paused between one of the questions confirming role fit.
So my cover almost got blown, and then I started to BLOW.
Oh my!
I did my best to keep my composure and continued to look into her “eyes” on the screen. While this happened, she talked about the “steps if you make it to the next round”. Then, we put a polite end to the conversation and ended the call.
Honestly, after all that, I didn’t think I would make it. So imagine my surprise when I got another email from the recruiter saying I had moved on to the next stage.
“Hi Caleb,
Thanks for your continued interest in FAANG! We would love to invite you to chat with HIRING MANAGER as the next step in our process!
Please select a few dates and times using the green “Find A Time” link below and we will get that call set up for you!
Thanks,
RECRUITER”
The Technical Interview
The technical interview was with the Hiring Manager of the storage team. We spent ~10 minutes talking about our experience, then started the Data Structures and Algorithms LeetCode interview.
The question — which I had seen before — instructed you to find the number of possible combinations you can use to eat a one-dimensional chocolate bar (split into multiple pieces). This question was either a LeetCode medium or easy, given that I solved it in less than 20 minutes.
I can’t publish the code I submitted, but the brute force solution is recursive. From there, you use memoization to optimize the brute force solution by caching the number of possible combinations a smaller-sized chocolate bar has, then using that cached value to calculate the number of possible combinations for bigger-sized chocolate bars.
I must have solved the first question too fast because the hiring manager decided to ask me another question about graphs: I could tell that the second question was a LeetCode hard in terms of difficulty and involved the topological sort algorithm.
It’s recommended to communicate your solution to a programming problem in a technical interview. Unfortunately, programmers — some of whom are interviewers — spend so much time with relational databases that using graphs tends to confuse them.
Like no, don’t use recursive CTEs in MySQL or PostgreSQL for graphing functionality unless you want SH*T performance!
I didn’t want to waste my time explaining an optimal solution that went over the interviewer’s head: You can call me paranoid, but that happened in my Spotify interview. So before explaining my solution, I asked my interviewer to show me his GitHub profile.
The man hesitated for a moment before letting out a sigh and placing his profile’s URL in the chat. I copied the link, pasted it into my browser’s search bar, and clicked enter.
Silence consumed the call as I waited for my interviewer’s profile to load…
And then it did: The star icon was clear as day on my screen.
“Ugh! No Stars? Oh men.”
I couldn’t hide my disgust. I started to feel dirty inside. All those followers, no stars…
The interviewer had no idea what to do. He stared at me for a few moments before uttering a response: “Y’kn- Y’know, I-, I’m the one with the job here. It doesn’t ma-” but before he finished his sentence, I cut him off.
“NO STARS?! YOU ARE A LOSER!!!”
Then I clicked him off my screen. I muted him in perpetuity. I ended the call.
I proceeded to blackhole the company’s domain from my email server and marked the prior conversations as spam. Hit the gym. Lawyered up.
Look, I didn’t pay $80,000 to graduate from college just to get interviewed by a LOSER with NO STARS! Like, what are you going to tell me next? That this man coded for Two Sigma but has nothing to show for it because he signed an NDA?!
Not even one star?
I debated whether or not I should publish this story on the internet for a long time. Who am I to judge a man’s stars when I have less than one thousand myself? But then I remembered that this is the second time my interviewer has fewer stars than I do on GitHub.
So it’s clear that I must send a message and set the record straight.
You aren’t qualified to interview me if you have fewer stars than I do on GitHub: Give me your job and resign — without notice — NOW!
