Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Meta

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Meta | Offres d’emploi chez Meta | Salaires chez Meta | Avantages sociaux chez Meta
      Entretiens chez MetaEntretiens d’embauche pour IOS Engineer chez MetaEntretien chez Meta


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour IOS Engineer

      28 juil. 2017
      Candidat à l'entretien anonyme
      San Francisco, CA

      Autres retours d’entretien d’embauche pour un poste comme IOS Engineer chez Meta

      Entretien pour IOS Engineer

      30 oct. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Meta (San Francisco, CA) en juil. 2017

      Entretien

      I was initially contacted by a recruiter via LinkedIn. They set me up with an initial phone screening to ask personality and behavioral questions. This phone screen went really well, and I was quickly asked to schedule a technical interview which would take place over the phone and on Coder Pad. I studied algorithm design and whiteboard coding for about two months to prep for the interview to come. Interview day finally arrived, and I was called by a developer who told me that the interview would be based on my problem-solving skills, algorithm design, and it would be totally fine if I didn't know all of the language syntax because that would be absurd. First, I was asked basic questions about my programming language of choice (Swift). What is an optional? What are some ways we can unwrap optionals? What does the question mark do? What's the difference between a Class and a Struct? When would be an appropriate time to use one vs. the other? I was then asked the fairly popular, medium-level Merge Intervals leetcode question. It took me about ten minutes to walk through my process, code out my algorithm, and run through edge cases. The interviewer said that I had successfully solved the question, and moved on to the second step of the interview. This step required me to debug a faulty TableView. After making quick work of this step (I'm very familiar with TableViews - who isn't?), we moved on to the third and final coding question. I was asked to write a function that would run some task on a background thread asynchronously, and run a second task on the main thread after the async-task was complete. I wasn't exactly sure of the syntax for Grand Central Dispatch, and mentioned this to my interviewer. Regardless, I pushed on. I wrote out what I thought the syntax might be, explaining the difference between threads, the benefits/drawbacks of background vs. main, how GCD works in iOS. When I was done, I had something that, while syntactically incorrect, would run a completion block on the main thread after finishing the async-task. The interviewer kept repeatedly asking, "You don't know the syntax for this?" To which I continuously replied, "No, I usually have a custom function that handles this sort of stuff for me, but I know exactly how it works." And I would go on explaining exactly how GCD works and why. As you can probably already tell, I did not get the job. I was emailed by the recruiter two days later saying they had chosen to go with someone with a better understanding and memory of the syntax. I was shocked. Blown away. Not only do you constantly hear from recruiters, interview prep, and the Facebook tech community that syntax isn't super important during the process, but to have the interviewer explicitly state that it wouldn't matter, you would think they were telling the truth. Why would a "good" programmer memorize the syntax of everything? How is this really that important? When will there ever really be a time when I don't have code-complete during my job? I honestly loved the idea of working at Facebook. I still do, in fact, but working for people who don't realize or care how broken the interview process is, would get annoying real quick.

      Questions d'entretien [7]

      Question 1

      What are optionals in Swift & when would we use them?
      Répondre à cette question

      Question 2

      What are some ways to unwrap optionals in Swift?
      Répondre à cette question

      Question 3

      Why would we NOT want to run an API call on the main thread?
      Répondre à cette question

      Question 4

      What does the question mark (?) and exclamation mark (!) do in Swift?
      Répondre à cette question

      Question 5

      What's the difference between a Class and a Struct & when to use one vs. the other?
      Répondre à cette question

      Question 6

      Debug UITableView code.
      Répondre à cette question

      Question 7

      Write a perfect implementation of GCD (background & main threads).
      Répondre à cette question
      19

      J'ai passé un entretien chez Meta

      Entretien

      It was just as they described except that the interviewers came with their biased personality. I hate, hate, hate interviewing for meta. Always arrogant and I think ageist. When you think of tech bros, this is it. I will never bother with them again.

      Questions d'entretien [1]

      Question 1

      write a method to detect where in the coordinate space you are and validate some requirements. Super easy stuff but having an intuition that answers the question immediately is not what they want.
      Répondre à cette question
      1

      Entretien pour IOS Engineer

      28 oct. 2025
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 jour. J'ai passé un entretien chez Meta (New York, NY) en août 2025

      Entretien

      Met with recruiter. Went over process. Didn't seem to be a good fit for the particular role. Said I would hear back for a position that would be more fitting and then never heard back again.

      Questions d'entretien [1]

      Question 1

      Asked about personal contributions to projects, and specifically contributions that helped deliver solutions at scale.
      Répondre à cette question

      Entretien pour IOS Engineer

      17 juin 2025
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Meta (New York, NY)

      Entretien

      Initial HR Round followed by a 45 minute technical interview, As soon as the recruiter joined, he asked me to work on DSA question's related to views and trees. Interview was smooth. But did not get the offer.

      Questions d'entretien [1]

      Question 1

      Initial HR Round followed by a 45 minute technical interview, As soon as the recruiter joined, he asked me to work on DSA question's related to views and trees. Interview was smooth. But did not get the offer.
      Répondre à cette question