In the second interview, he asked me to share my screen and do some coding with Xcode. It was fairly simple and if you have at least 3 years of iOS experience you won’t have any big problems. Make sure you remember how to do sync, async code. They really care about you being able to manage async code.
mostly technical to iOS , Swift basics
closures, MVVM, Coredata, Multithreading, mvc
Basic Swift questions like optionals
Ios basics like memory management
Basics about iOS and objectives c language, oops concepts
During technical interview I was asked about Swift & iOS: generics, generic protocols, how Swift Optionals work, difference between closures and functions, how memory is allocated for closures, capturing values in closures, difference between structs and classes, how memory is allocated for structs and classes + edge cases (struct in heap, class in stack). After that showed me different code samples and tasks: DispatchQueue spaghetti task (to determine execution order), execution order, Unit-Testing sample task (to improve code and make a proper test), retain cycle task (to find this cycle or prove that there's no problems)
During Live Coding I had a small app to write, the purpose of this app was to parse local json file with geo points and put these points on the MapKit map. Solution should be clear, testable, scalable and support later migration from local file to remote data source. Things to think about: architecture and error handling.
They asked how I would structure and test an iOS feature that updates financial data frequently, including how I would handle architecture, async updates, cancellation, and stale responses.
Principales diferencias entre ObjectiveC y swift
Viewing 6601 - 6610 interview questions