Actually, this is just me venting...
First, the onsite is called a "hiring event," and there were about a dozen people there. After checking in, we even had to walk back to the car to put up the parking permit — pretty chaotic.
The hiring manager for the BQ round was 15 minutes late! If they hadn't shown up soon, I was ready to pack up and leave. The conversation itself was pretty mediocre — not sure if it was on my end or something else, but they had this attitude the whole time like "none of the problems you're describing are a big deal." After I told my story, it had that vibe of "oh, what you did is maybe important, but you're lucky you didn't have to deal with XXX's problems."
They were supposed to make up the 15 minutes they were late, but they said they were too busy and had to leave...
Then I just sat in that room waiting. 30 minutes later, the next interviewer still hadn't shown up, so I called the recruiter, and it turned out my second round was actually on a different floor, starting in 15 minutes. I rushed over, and it took 10 minutes to find the meeting room — the interviewer had the same problem. This floor didn't even have a map, and there was no signage pointing to the meeting room either.
The coding round ended at 12:30, and the interviewer told me to wait 15 more minutes right there for the next interview. So I waited until 12:45 to start the system design round. By the time that finished it was 1:30, and I still hadn't eaten.
This was my first time doing an in-person onsite — before that it was always virtual. Is onsite interviewing always this unprofessional, or was it just that this company's arrangement was this bad?
The phone screen and the onsite coding round were actually the exact same question — unbelievable.
The onsite required writing code by hand on a whiteboard. The system design question was similar to what this team actually builds — design a service where users can browse products and merchants can list products for sale. The main deep dive was about handling a large volume of writes and a large volume of reads, so most of the discussion focused on the database.
Discussion
Loading comments…