Conocimientos y uso de principios SOLID
Senior Ios Engineer Interview Questions
621 senior ios engineer interview questions shared by candidates
Gestión de persistencia para la app
NDA
Are you located out of the country?
Take home challenge: build the blog posts view of their app. Render html in labels, loading states for views and images, etc
Memory management for iOS questions, lifecycle questions, how to do networking requests, architecture patterns, make an app that does basic collection view things, make an app that does basic table view things, make the logic for a game (chess, checkers, tic tac toe, ect.)
First it's the regular HR questions, your motivation, background, etc, then for the second one you are supposed to explain your approach for solving technical issues (high-level), your technical background, etc. Then you receive a Playground to do actual coding. This Playground covers different things like mapping (Codable), XCTest, UI, architecture (MVVM-C) and threading (dispatch queue). After spending some hours on it and documenting every step of my approaches, I sent them my modified Playground version. After a couple of days, I got what seemed like a generic rejection message saying they would not proceed with my application. There's no explanation why. I kindly asked for more details on why the proposed solutions didn't met the expectations. After some back and forth and insisting from my side, they sent me the feedback from engineering, and apparently the issue had to do with dependency injection. I've used the most plain and simple injection solution out there, which is to pass in dependencies as arguments in the initialisers -- but apparently that was not enough for some reason. When dealing with technical solutions, one has to keep in mind that there are many ways for doing the same thing. If a certain way is expected, the company should make it very clear, otherwise the process will be a waist of time for both sides. And when hiring for a senior position, you have to be prepared to reason and argue about technical approaches as well. Why is the solution not "good" enough? What was the motivations behind it? Please elaborate on the trade-offs and what would you do if you have more time? These are the kind of questions that would reveal how much experienced an engineer is. The generic rejection e-mail is simply deplorable. That by itself tells a lot about the iOS engineering team @Clue.
Describe the SOLID principles. What design patterns do you use. Do you think it's important to test your code.
General questions, nothing specific (auto layout, core animation, info about current project and role).
How might you build 2 screens that use a common region?
Viewing 511 - 520 interview questions