Altimetrik Ios Engineer interviews, decoded.

The interviewer seemed unsure about the purpose of the written test. In this AI era, they asked me to avoid using the internet, Copilot, or higher-order functions, claiming these aren't used in real projects.

I went through a few interviews. First, there was a call with HR, then a technical coding part where they checked my Swift and iOS skills. After that, we did a system design interview. The last interview was with some engineering leaders to see if I'd be a good fit for the team and how I think about products.

The interview is split into three rounds. First, we'll dive into technical foundations, like ARC, SwiftUI's lifecycle, and the differences between structs and classes. You should be ready to talk about how @State, @Binding, and @ObservedObject handle data flow. Then, round two is about low-level design – basically, writing good, maintainable code. We'll want to see how you use SOLID principles and Design Patterns. The last round is client-facing/behavioral. We need to know if we can trust you with the client's product. Use the STAR method to walk us through past projects and how you've dealt with things like technical debt or when requirements change.