Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

7 stories

Likes earn the author +10 XP for the first 3 likes each day

OuraSoftware Engineer
Reported Jul 2026

Oura Software Engineer interview: calm and responsive process

After speaking with a recruiter, I met several interviewers across a few coordinated rounds. The process included an HR-style introduction, technical conversations, and later time for HR and final fit. Everyone was prepared and interested in my background, and the questions stayed grounded in my experience and the role. The timeline was clear and communication was responsive, so I did not have to…

HR Screen0
OuraSoftware Engineer
Reported Jun 2026

Oura Software Engineer interview with late immigration constraints

The process was mostly smooth at the beginning, but the closer it got to the final rounds, the more it felt like important context was missing. I disclosed my visa needs to the recruiter right at the start, completed multiple interview rounds, and received positive feedback along the way. When it came time for the decision, I was told that immigration couldn't move forward and that an offer would…

HR Screen0
OuraSoftware Engineer
Reported May 2026

Oura Software Engineer interview: TypeScript assessment and take-home deep dive

The most stressful part of my process was the coding work, which started right away with an online assessment. I received an email for a TypeScript assessment, but I hadn't been told it would specifically use TypeScript before committing, so I was somewhat underprepared for the language details. The grading felt strict about expertise, which made the experience feel high stakes. The process then…

Online Assessment0
OuraBackend Engineer
Reported Mar 2026

Oura Backend Engineer interview with architecture, coding, and take-home rounds

After I applied, I had an initial recruiter conversation about the role and my background. The recruiter explained clearly what the overall process would look like. A week or two later, I had a system architecture discussion with a team member. It felt structured and intentional. After that, I interviewed with the hiring manager. The process then became more practical. I did live coding with the…

OfferHR Screen0
OuraBackend Engineer
Reported Feb 2026

Oura Backend Engineer interview: CodeSignal timing made the assessment feel unreliable

I started with a CodeSignal assessment that was supposed to be a straightforward skills check, but the timing threw me off. The whole thing moved way too fast. There wasn’t enough time to slow down, understand the problem properly, and implement a solid solution. The question itself wasn’t described as wildly complicated, but the time limit made it hard to demonstrate capability instead of simply…

Online Assessment0
OuraSystems Engineer
Reported Dec 2025

Oura Systems Engineer interview with a one-day offer window

I was contacted by a talent scout, and we agreed on a one-hour online interview. A couple of days later, I had a team interview that also lasted about an hour, followed by a final conversation with a team leader. Everyone I spoke with was encouraging and polite. The atmosphere felt supportive rather than intimidating. The process moved surprisingly fast. Within about a week, I was offered the job…

Offer0
OuraSoftware Engineer
Reported Oct 2025

Oura Software Engineer interview with a missed technical interview and delays

A lot of my experience came down to reliability. I started with an HR conversation that went fine, then waited for a technical interview that never happened. After the interviewer didn't show, I followed up but received no real response or explanation. The lack of communication felt disrespectful because I'd set aside time and built expectations around the meeting. Scheduling caused more problems…

HR Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP