Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Apple
Colloquio
1 Phone screen
2 On-site (4 technical rounds on day 1 and 5 behavioral rounds on day 2)
After all that, a shallow no. Technical questions were all good and reasonable, also got positive feedback after day 1. But never seen 5 behavioral rounds for software development role in any other company.
Domande di colloquio [1]
Domanda 1
Mostly solving daily life algorithm problems and some UI problems
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Apple nel mese di feb 2022
Colloquio
I received the first interview email where it was specified I will have to discuss the role and my experience and I won't be expected to code.
But the interview was a full on technical one. Even if it was easy and related to my experience it wasn't what I was expecting from an Apple recruitment.
It was like being interviewed from a startup, random questions about technologies used.
Domande di colloquio [1]
Domanda 1
Best Improvement in ES6 vs previous versions
React libraries I've worked with
ES6 loops
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 7 settimane. Ho sostenuto un colloquio presso Apple (Cupertino, CA) nel mese di mar 2019
Colloquio
It was a bit of a lengthy process comprising LinkedIn messages, emails, a phone interview, a development homework assignment, an invitation for an on-site, the on-site interview itself, and a final decision. All told, it was about a 7-week process. The phone interview was only 30 minutes and was mostly about me as a person and how I prefer to work. The homework assignment was fairly simple – but a little gotchya here, they used it as fodder for my first on-site interview session, expecting me to have all that 2-week-old information at the forefront of my mind. The on-site interviews were all pretty great, though – everyone was very nice, helpful, friendly, etc. No big gotchya questions or pointless tidbits like trivia, etc. A bit of whiteboard coding (my first experience with this) but it didn’t matter what language you decided to write in (or even pseudo-language) or if you made syntax errors in that process – it was all about the “why?” behind the code you were writing. On-site was 6 separate interview sessions involving 8 people and was spread out over 5.5 hours with a break for lunch. They got back to me within a week of the on-site interview.
Domande di colloquio [9]
Domanda 1
Q: How would you go about adding feature X to [the app you built as homework]?
Q: How would you create an app that is a data-dashboards app with multiple dashboards per user, each one having its own widgets which are all configurable – can resize and position them however you wish, and you can determine what data stream to be represented, how much of it, and in what way (e.g. line chart or bar chart)?
Q: If we pull the top 100 search results from 7 separate services, let’s say, and then pull those into a single service and want to return just the top 100 from all of those, how would you implement that?
Q: Here is a mockup of a design we’ve been tasked with implementing. For now we’ll just do some basic HTML, CSS, and JavaScript to populate a page with items from a hard-coded JSON response to match the look of the mockup, and we’ll implement some simple JavaScript handling of a button.
Q: Given a certain relational database setup, let’s say we want to know the conversation rate for each device type (iPhone or iPad) across the A and B instances of some experiment named “New Experiment.” How would you write that SQL?
Q: (Drawn on the whiteboard) Let’s say you’re a Person, and you have a certain relationship to Animal, Hat, Leg, & Escalator. What would you label each of those relationships? How would you order them, from 1–5, in terms of how tightly coupled they are (1 being most tightly coupled)?