DataArt Ios Engineer Interview Questions
& Process

The interviewer was late and after about 10 minutes of waiting, I gave a brief overview of my background. Then, without further discussion about my experience, I was given an app coding task to complete within one hour. The task involved setting up the app architecture, configuring an HTTP API, adding unit tests, and creating a basic UI. I was unclear about the exact expectations – whether to fully complete the test app or just set up a clean architecture, as I didn't receive a clear response when I asked. I'm not sure if this is a standard process for all roles or specific to iOS, but it felt quite unusual. Despite the time constraint, I managed to set up the API, build two screens, implement a basic MVVM+C architecture, configure dependency injection, and create a usable UI, but unfortunately, I couldn't finish the unit tests. The feedback was also odd, mentioning my lack of focus on unit tests and inaccurately stating I had experience with a technology I never brought up. Overall, this experience has led me to decide against applying for DataArt jobs in the future.

It was a few steps, starting with an English test, then a technical interview, and finally a final interview with the HR Lead. The first two steps were conducted via Skype. The last one took place at the headquarters in Dnipro.

The whole process took about 2 weeks. The interview had several stages, like checking English level, theoretical knowledge, algorithms, and a practical part. The theoretical questions were split by themes: Objective-C, Core Data, iTunesConnect, memory management, and multithreading (queues, gcd, nsoperation).