Solicité el puesto a través de un captador. Acudí a una entrevista en GameChanger
Entrevista
Met with a number of folks. Most of the conversations were pretty good.
Completed the take home - not only implementing what they required - but went above and beyond to demonstrate my abilities. The review of the take home neglected my efforts - almost as if the individual felt their job security threatened.
In the architecture whiteboard interview, I presented a high level diagram covering a lot of bits to demonstrate understanding. This is supposed to be high level right? I'm not applying for system architect but my knowledge/diagram was pretty thorough regardless.
Had a great chat with the final "culture/personality" interviewer..
and yet, somehow, some way, they blew me off as I was deemed 'not hitting the technical mark'.
Your loss. Not mine.
Preguntas de entrevista [1]
Pregunta 1
A take home coding technical building out some apis.
Envié una solicitud electrónica. Acudí a una entrevista en GameChanger (New York, NY) en ago 2024
Entrevista
While there seems to be a structured process in place it is anything but that. It is a group of mediocre people (particularly the marketing team) who seek to insulate and defend their own mediocrity. It's a classic case of B-players looking for C-players so they can continue to be mediocre.
Acudí a una entrevista en GameChanger (New York, NY)
Entrevista
I found the interview to be frustrating. There were very few technical questions and nothing in-depth. It wasn't clear what the interviewer was looking for in most of the questions being asked.
Preguntas de entrevista [1]
Pregunta 1
What's most important for a junior developer to know?
Envié una solicitud electrónica. Acudí a una entrevista en GameChanger (New York, NY) en feb 2023
Entrevista
Applied online. Took a bit over 2 weeks. 1. Initial phone call 2. Technical interview with hiring manager (behavioral questions) 3. On-site virtual interviews Like some feedbacks from here, coding practice was a big dissapointment. First interview with coding practice didn't go well. Senior interviewer was suggesting me to edit a front-end code for React but I explained to him that his suggestion wouldn't work becauuse of the lifecycle of React. He still insisted on going his way and I followed his direction. When he realized that it wasn't the right direction, we decided to go my original code. It was a bit questionable because of it should be the basic fundemental of React lifecycle and the person who reviews my skills didn't have much of knowledge worried me about grading my skills properly. All the interviewers were nice, but I was interrupted frequently during the coding challenge which caused some confusion. I got the rejection few days later. The interview questions weren't challenging much so I feel frustrated because everything seemed went well on my end but still got rejected with the basic template rejection letter. Need to ask more technical questions to challenge interviewees instead of asking easy questions. What's the point of conducting 3-4 hour long interviews if everyone can give you the answer without much effort?
Preguntas de entrevista [1]
Pregunta 1
- Tell me about your background. - Doesn't understand how useEffect work in React (senior with years of experience)