Software Engineer applicants have rated the interview process at OKG with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 63% positive. To compare, the company-average is 42.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at OKG overall takes an average of 22 days.
Common stages of the interview process at OKG as a Software Engineer according to 8 Glassdoor interviews include:
Phone interview: 33%
One on one interview: 22%
Skills test: 22%
Personality test: 11%
IQ intelligence test: 11%
Here are the most commonly searched roles for interview reports -
practical and hand on. 3 tech rounds. live coding involved but not heavily focused. experience demonstration is more important. interviewers are friendly and helpful. however the whole process can be very lengthy
I applied online. I interviewed at OKG (Hong Kong) in Feb 2026
Interview
The interview process was good, Li spoke well and was friendly.
Tested knowledge on Rust by asking questions about concepts and features generics, enums, clone/copy etc
Asked about work experience and specifically how I approached certain problems and how they were fixed.
The coding part was looking at some code and answering questions. Then onto a codepad website to solve a sliding window solution.
Overall; good interview, relaxed and friendly.
Interview questions [1]
Question 1
Explain the difference between Generics vs Trait Objects
I had a disappointing interview experience. The interviewer appeared to have limited proficiency in English, despite the fact that English is one of the major languages spoken in the city where the interview took place. This created significant communication barriers. Whenever I used technical terms (for example, API), I first had to check if the interviewer was familiar with them. Most of the time, the answer was no, which forced me to spend several minutes explaining basic concepts in another language. As a result, what should have been a one-hour technical interview turned into repeated explanations of fundamental programming concepts, leaving little time for meaningful discussion of my skills or experience. The interview difficulty mainly come from the language barrier
Interview questions [1]
Question 1
Can you explain some concepts that you usually wouldn't face in day to day operation in your previous internship experience?