Oura Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 23 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Oura.
Oura
Software Engineer
Entry Difficult Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Behavioral
The whole hiring process went pretty smoothly. They kept me in the loop about what was happening next and when. It wasn't a super long process: I applied, had an interview with HR, and then a technical interview. They were quick to get back to me with answers and to let me know they were going to offer me the job. The formal offer letter took a bit longer, but it wasn't bad. All in all, I thought the hiring process was really good. It felt well thought out and they were good to me as an applicant.
Confirmed questions1 question
- Can you tell me about a project you brought in? Let's dive into how it worked, the rationale behind your choices, and alternative approaches you considered.
Oura
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical
The recruiter was really enthusiastic about my 20 years of experience, but the hiring manager interview was a letdown. He was late and only gave me 4 minutes for my questions at the end. He didn't even know what job I was interviewing for until I asked him at the very end! Maybe it was the end of the day, but he seemed bored and lacked any personality, like talking to a wall. There was zero interaction or questions about my experience; he just asked basic 'check box' questions from a list. It was a disappointing experience.
Confirmed questions1 question
- Can you share an instance where you had a disagreement with a manager?
Oura
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral Coding Presentation
So the interviews kicked off with the Tech Lead for the team. It was a pretty chill interview, mostly covering some basic tech stuff and background questions. The lead was super helpful and made it feel relaxed and conversational. After that, I had the onsite interviews, which were actually three separate interviews. The first was behavioral and cultural, with some light technical questions. The second was with the Product Manager, and it was all about how I collaborate in a team, manage priorities, and if my development approach aligns with theirs. The third interview was a live coding challenge. I was given a prompt and had to build out the MVP features within a small existing codebase, and then work on some extra stretch features. All these interviews had a conversational vibe, which really highlighted the awesome company culture and gave me a good sense of what current employees honestly think. The recruiters also did a fantastic job making the process smooth. The only thing I'd tweak is maybe adding Calendly links for easier scheduling.
Confirmed questions3 questions
- Could you start by telling us about yourself?
- Describe a situation where you disagreed with a colleague and how you handled it.
- Are you able to integrate these new features into the current codebase?
Oura Software Engineer Interview Questions
Quoted word for word from Oura interview reports.
“Write a function that creates a canvas object with 'paint', 'undo', and 'redo' capabilities.”
Read reports →“How would you store data from the ring's sensors?”
Read reports →“How would you design an architecture for a messaging board?”
Read reports →“Can you review this frontend code?”
Read reports →“Would you rather use dynamic or static typing?”
Read report →“Build a mock activity-tracking app featuring robust business logic and a better, more intuitive user interface. It should support starting/stopping recordings with live metrics, saving sessions and displaying their history, and implementing a gradual rollout post-launch using a feature-flag system that mimics backend control.”
Read report →“Are you able to integrate these new features into the current codebase?”
Read report →“What makes you want to join Oura?”
Read report →“What is your motivation for joining the Women's Health Team?”
Read report →Formats, difficulty and experience
Across all 23 Oura interview reports.