Here were my otherwise easy questions:
Role was for web engineer:
- Is JavaScript strongly typed?
- What is TypeScript?
- On my resume - what is Cypress?
I couldn't remember at the time because I recently started using it
- What does ownership mean?
- What does loyalty mean?
- Why do you want to work at apple?
- What does it mean to be a part of apple?
- Name a time you technically solved a problem?
That's all I remember.
After asking my four questions to the interviewer and I ended off saying "please let me know what the next steps are". Never say that lol.
My mistakes:
I got rejected for the dumbest reason and I can only blame myself. I genuinely thought the interview would test my coding skills.
I even was sent a coderpad link along with the WebEx link.
Day of the interview I click both links I discover it was not.
I learned:
- Ask the recrutier what to expect especially for the first round. Looking back at it having a conversation first makes sense and I should have expected some technical questions. I mean I don't know too many companies that just jump right in to coding right away, right?
- Know everything on your resume.
- Maybe have better answers ready to e.g. why do you want to work at apple: https://www.glassdoor.ca/Interview/Why-do-you-want-to-work-for-Apple-QTN_1600546.htm
- Know everything I can especially the basics. I tried to fine tune my prep for what I thought the interview was. Honestly, interviews are never what I think they are.
Thought I'd share so no one else experiences this!