I applied through a recruiter. The process took two weeks.
I interviewed for a position that involved a loop scheduled across two days: approximately 1.5 hours on the first day and one hour on the second. The first day went smoothly, and the interviewer gave positive feedback at the end, noting that I asked the right questions to understand the role's requirements well. On the morning of the second day, I received an email asking whether I could reschedule my remaining interview. Due to my own commitments, I wasn't able to accommodate the change and communicated this politely. Within about five minutes of responding, I received a rejection. The reason given was that I didn't ask enough questions during the interview, which was surprising, as it directly contradicted the positive feedback I'd received the day before. While I understand that not every interview results in an offer, the inconsistency between the in-person feedback and the stated rejection reason, along with the timing, made the experience feel less than transparent. I'd encourage the team to ensure that rejection feedback aligns with the actual interview experience.
The interview involved a system design question to design a recommendation system.
The following metrics were computed from 6 interview experiences for the StubHub Senior Software Engineer role in San Francisco, California.
StubHub's interview process for their Senior Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having negative feelings for StubHub's Senior Software Engineer interview process in San Francisco, California.