DataArt 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.

The gig was for a Quantitative Analyst at a company in the US. Things kicked off with an HR chat which went super smooth. Then came the technical interview with someone from DataArt. This interviewer had a really thick accent and seemed to be in a mad rush, barely letting me get my answers out for some questions. They threw a bunch of stuff at me that those devs don't even use day-to-day, not focusing on data analysis, Pandas, SQL, or how to solve problems. Oddly, they didn't ask anything about my background, my problem-solving skills, or how I handle learning new things. Honestly, if you interview like that, you'll miss out on hiring good engineers and end up with folks who just crammed the answers.

The hiring process kicked off with a recruiter's message, then a standard screening call with another recruiter where we chatted about my background and experience. Things got weird after that though. Even though I'd already confirmed I had permanent residency and full work rights in Brazil, they asked again by email. Then they requested my citizenship, which felt out of place, and finally, before even the second interview round, they wanted a scan of my government-issued ID. I found this to be a really sensitive request way too early on. When I asked why it was needed so soon, I got vague answers like it was to 'avoid any obstacles later' and that it's 'hard to go back' once things are further along. No clear explanation was ever given despite me following up politely. Also, there was confusion about whether the job was internal or for a client; one call said 'internal,' but emails hinted at a 'client.' Again, no explanation despite me asking. That confusion, plus the ID request and general lack of openness, led me to pull out. My advice: if you're thinking about applying, ask upfront about the role's specifics (internal/external) and how your data is handled. For DataArt, trust and clear communication are key, and this process failed on both counts. You can't expect candidates to trust you with sensitive info while dodging questions and being unclear.

First, an HR interview. Then, an English interview. After that, a company technical interview where we covered .NET theory and did an easy live coding exercise, but no algorithms. Next, there was a preparation for the customer interview, which was a Q&A session with the developers working on the customer's project. Finally, the customer technical interview involved a hard, customer-specific live coding task without any theory or algorithms, followed by a customer soft skills interview with the feature team.