Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en GitHub (Sídney)
Entrevista
The process started when I applied for the role. Responses were quite prompt. Interviewers were courteous. But It was negative experience for me due to the careless recruiter. Even after emailing them to get an update they didn't give me any response. After some googling I came to know that this is the typical GitHub recruitment experience. If you don't get selected, they don't have the minimum courtesy to let you know about the rejection, feedback is a far cry. This is very disappointing. I went for this role because I thought GitHub had great culture. When I see the Recruiters treating people and their time like trash, it makes me rethink my opinion.
I applied online and was asked to provide availability a couple days after. Took two weeks to book an appointment. I was pretty excited to interview Github but the screening call was a real letdown. The interviewers could not or would not give any relevant information about the position and the organization and there a very distinct age bias. The "process" was explained to me: 5 interviews! EM meeting, 2 coding rounds followed by a behavioral interview and a system deiagn interview (that's before meeting HR): everything from the book to dilute responsibility and avoid accountability, which is a big red flag. The third red flag: being ghosted.
In summary :
- age bias
- unrealistic process
- ghosting
Me postulé a través de un reclutador. El proceso tomó 3 días. Acudí a una entrevista en GitHub (San Francisco, CA) en dic 2023
Entrevista
In an earlier experience, there were three rounds of interviews after an initial screen, where I was ultimately rejected on account of a disability. This time around, despite matching numerous skill requirements (90%), the candidate can be rejected due to either being on a blacklist or not meeting equity targets.
Preguntas de entrevista [1]
Pregunta 1
In an earlier interview process, I had a live evaluation where I needed to check out code (ruby), deploy a GitHub enterprise server, and troubleshoot problems, and make changes to resolve the issue.
