Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Apple (Cupertino, CA) en may 2016
Entrevista
A recruiter reached out to me by email and then we scheduled to have a phone conversation. We talked about the roles they were interested in hiring me for and gave me the opportunity to learn more about other roles because they want people to stay in their position for years. I had a few more interviews with other Apple staff to learn more about the role from people who do it. Apple then scheduled an on-site interview in Cupertino and payed for all of my travel costs. The interview itself was super straight forward. There were several interviews with 2-4 people and they asked me questions varying from topics like what drives me forward, my technical experience, and cultural fits. It also seemed like they made the personalities of my interviewers different. Some were super hip and talkative, others were awkward and didn't feel like they wanted to be there and some were over FaceTime. I also had lunch with the team leader and my final interview was with the executive for developer publications. After those interviews, I didn't hear from them for one week and then the recruiter scheduled one more call with me to explain that I didn't have enough experience at that time and that he would reach out again in several months.
Preguntas de entrevista [2]
Pregunta 1
How would you build a trip planner for a transit app?
Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Apple (Cupertino, CA) en may 2024
Entrevista
Early on in the process it became apparent that this job wouldn't work for me for logistical reasons. Still, we had a very nice chat and the interviewer encouraged me to stay in touch.
Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en Apple (Austin, TX) en jul 2021
Entrevista
Lengthy and challenging in the sense that they'll really drill you, to understand if you know the ins and outs of the job or not. They're not going to hire you if you don't deeply understand what technical writers are trained to do.