
OKG Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at OKG.
Senior Android Developer
I recently interviewed for the Senior Android Developer role at OKX. The interview was an hour long and had two parts: a coding round for about 40 minutes and technical questions for about 20 minutes. The technical questions were pretty standard for Android, but the follow-ups made them tough. I got nervous and confused my answers, especially on the follow-ups where they probed deeper. I knew how it would end, but I was hoping for some feedback, which OKX doesn't give unless you reapply after six months. It was a good learning experience though. If you're preparing, practice common Android concepts like activity lifecycle and ViewModels, and work on coding problems focusing on time and space efficiency because they dig deep into your thought process.
- I was given a problem where I had to transform an integer array, and it needed careful consideration of time and space optimization.
- When I suggested using a hashmap for optimization, I was asked to explain how hashmaps work internally.
Senior Android Engineer
Applied after a recruiter reached out via cold email. Honestly, this was the worst experience I've ever had. No feedback whatsoever after the interview, and the interviewer was openly using their phone during our conversation. It felt like they'd already decided to reject me before we even started talking. The process involved a Leetcode-style algorithm problem, followed by questions on Android foundations, Java, and Kotlin. Then, a deeper dive into Android knowledge and project experience. The next round focused on network and CS fundamentals. Finally, there was an HR interview.
- Solve a Leetcode medium problem involving arrays.
Senior Android Developer
So, first HR called to chat about my application, background, and what I'm looking for. Then, the first technical interview was all about Kotlin and Android stuff, with live coding to see how I solve problems. The second technical one got way more advanced, digging into blockchain, data structures, and network concepts. Finally, another HR chat, less technical, more about the company culture. HR was super helpful through it all, keeping me in the loop and making sure things ran smoothly.
- Tell me about Kotlin, project design, and Android core concepts, and let's do some live coding on strings to see your problem-solving skills.
- Regarding memory leaks, how would you identify and resolve them without relying on external tools? Also, explain system design and answer other Android-related questions.
- Can you explain system design and related questions?
OKG Android Engineer Interview Questions
Quoted word for word from OKG interview reports.
“What is a Kotlin lambda function?”
Read reports →“Can you explain what the Android kernel is?”
Read reports →“What are methods to prevent collisions in a hash table?”
Read reports →“Solve a Leetcode medium problem involving arrays.”
Read reports →“Could you sort an array with repeating integers?”
Read report →“Describe the mechanism of a custom callback.”
Read report →“Can you explain how a hash table functions?”
Read report →“What is the sequence of events when an application is launched?”
Read report →“When I suggested using a hashmap for optimization, I was asked to explain how hashmaps work internally.”
Read report →Formats, difficulty and experience
Across all 7 OKG interview reports.