Oura Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Oura.
Oura
Senior Android Engineer
Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Recruiter call
Interview formats
System Design Coding Behavioral
The whole thing was pretty smooth and organized. First, I had an intro chat with HR. Then, there were two technical rounds: a 90-minute session focused on architecture and design, followed by a take-home project that we reviewed a few days later. After that, I talked with the hiring manager, and it wrapped up with another HR chat. Everyone I met was really nice and made me feel at ease right away, which definitely helped when we got into the technical details. The conversations were to the point, fair, and felt like genuine engineering discussions, not tricky traps. All in all, a good and respectful experience.
Confirmed questions1 question
- Can you describe how you'd approach designing a feature from start to finish, covering everything from initial requirements through to testing and the final release?
Oura
Android Engineer
Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
System Design
The interview process was super streamlined! My recruiter was incredibly supportive and communicative to me through the entire process. From start to finish, it took less than a couple of weeks to get through all the interviews (which is so unlike the other companies I interviewed for!--I had a company I was interviewing for over a month). The questions that were asked felt in alignment to the values and the job description as opposed to standard leet coding questions.
Confirmed questions1 question
- A question about system design, similar to what you'd see in an interview.
Oura
Senior Android Engineer
Senior Average Neutral experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical
I was initially contacted by a headhunter. The process involved a couple of phone interviews with them. Then there were video calls with a manager and an HR person. Following that, there were two technical rounds: one was a discussion with the Android lead, and the other involved a codebase review. I didn't really like the tech rounds; they focused too much on specific tech details that might be used by Oura, but didn't really assess my ability to get things done or learn. It took a surprisingly long time to get an offer, which felt slow for a smaller tech company, though there were holidays like Christmas in between. Even though the role was technically a level below my current one, I decided it was fine since I was looking to change industries and the compensation was good.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Oura Android Engineer Interview Questions
Quoted word for word from Oura interview reports.
“How would you design a typical Android app that interacts with a backend API, covering aspects like caching and threading?”
Read reports →“Have you worked with Kotlin Flow?”
Read reports →“Were you able to work on the project in Android Studio?”
Read reports →“What's your background with Kotlin?”
Read reports →“During an interview focused on Android programming, what kind of questions were you asked?”
Read report →“What are your thoughts on general technical concepts?”
Read report →“Were you asked Android questions related to a project?”
Read report →“What was the tech stack in your last position?”
Read report →“Can you describe how you'd approach designing a feature from start to finish, covering everything from initial requirements through to testing and the final release?”
Read report →Formats, difficulty and experience
Across all 9 Oura interview reports.