iOS Engineer Interview Experience - New York, New York
Process
I applied online, and a recruiter got in touch about a week later.
Two weeks after that, I had a phone screen with a few easy coding questions and some language-specific (Objective-C) questions.
About a month later, I interviewed on-site at the New York office.
The on-site interview consisted of four hour-ish sessions:
- A design session
- Two whiteboard coding sessions
- One session that was half personality-type questions and half coding (I didn't have enough time to finish the coding portion of the last one, but the interviewer told me before we started that I probably wouldn't, so I was grateful for that).
Everyone I met was super nice and helpful when I got a bit stuck on things.
Questions
NDA. But know trees, graphs (at least cursorily), and simpler data structures like arrays and dictionaries. Be familiar with Objective-C trivia, such as memory management and property types. Of course, be prepared to talk about the running times of your code. I would also recommend talking through your ideas for solutions before starting to code.
Was this helpful?
Interview Statistics
The following metrics were computed from 7 interview experiences for the Meta iOS Engineer role in New York, New York.
Success Rate
Meta's interview process for their iOS Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Meta's iOS Engineer interview process in New York, New York.
Meta Work Experiences
- 3.0Great, if you don’t mind politicsiOS Engineer • Former EmployeeMenlo Park, California, United StatesSeptember 10, 2023Pros: A big tech company that still moves fast. You get to do lots of data science and analysis yourself on your own features to see if things are working or not. You have a suite of offices around the world to hang out from, even though I think now it’s mandatory three days at the office.Cons: Building fbios takes about 20 minutes on a cold build, but it can be more or less. It's still not compatible with Buck 2. Working with Objective-C++ is a nightmare, and the process to switch to Swift is long and low priority. It's definitely not as easy as it was for Android developers to automatically have their code switched to Kotlin. Data analysis is messy if you don't set up the experiments perfectly. You end up presenting to people with incomplete data and having to come up with persuasive reasons for XYZ. It's all quite shaky and uncomfortable. No matter what you do, some experiments you run will inevitably be unbalanced, and then you have to start over and wait another week.
- 3.0Work-life balance is bad, but the pay-work-life balance is okayiOS Engineer • Former EmployeeToronto, Ontario, CanadaApril 24, 2025Pros: Generous compensation with stock value increase.Cons: Toxic culture. Stress resilience required.
- 5.0Positive Environment, No ConsiOS Engineer • Former EmployeeSydney, New South Wales, AustraliaOctober 6, 2020Pros: The work environment was good.Cons: Not that I can think of.
Meta Interview Questions
