READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 101 of 153
Interview experiences · Oscar Insurance
Oscar Insurance Software Engineer interview: ghosted after coding
I started with a recruiter call and moved quickly into a LeetCode-style interview. If that went well, I had been told to expect another LeetCode interview and a system-design discussion. I felt I did well across the steps. Then the communication dropped away. I was ghosted after the interviews, and when nothing happened I followed up about a week later. The rest of the process had felt normal, so…
Interview experiences · Oscar Insurance
Oscar Insurance Software Engineer interview: technical funnel to manager screen
After I reached out on LinkedIn, a recruiter contacted me and the process followed a clean series of rounds. First came a technical phone screen. The next stage combined an algorithms-focused screen with a system-design screen, and the final step was a manager screen. Each round seemed to add another lens. It began with core technical ability, then divided into algorithms and system design, befor…
Interview experiences · Otter.ai
Otter.ai Senior Software Engineer Interview Experience — Two Tech Screens, Three Onsites and a Silent Coding Interviewer
Tech Screen - 1 LC 2654 with one of the SDEs from the company. The focus was on executing code so that it compiles, not a lot of focus on edge cases etc. I was able to get this through with minimal help. Tech Screen - 2 A Senior Manager from the team. I explained project work with a presentation. Onsite 1 Another senior manager doing behavioral questions. Onsite 2 Google Docs system design with a…
Interview experiences · Otter.Ai
Otter.Ai Software Engineer Interview Experience — Rotting Oranges Plus a Meeting-Bot System Design
Coding round: Rotting Oranges System design Design a system: the user enters a video meeting link on a web page, the system assigns a bot from a Bot Pool, has the bot join the meeting, and continuously reports the bot's status back to the user. The meeting platform could be Zoom, Google Meet, Microsoft Teams, WebEx, etc. Existing components Both ends of the system already exist: Web UI user enter…
Interview experiences · Oura
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…
Interview experiences · Oura
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…
Interview experiences · Oura Ring
Oura Ring Software Engineer interview: clear timelines and practical rounds
After an initial conversation with the internal recruiter, I went through a mix of behavioral and technical stages. At every step, I got clear timelines, notice of what came next, and quick answers to my questions. Everyone I met was prepared and professional, and the atmosphere felt friendly and respectful. There was an early HR-style conversation, then technical discussions of relevant work and…
Interview experiences · Oura Ring
Oura Ring Software Engineer interview for a contract role with portfolio feedback
I went through a recruitment process for a contract role, and the team was unusually responsive. They welcomed my questions and gave specific answers instead of generic ones. They even offered feedback on my portfolio, which made the process feel constructive. The feedback was more specific than what I've seen from many other companies, and the conversations felt thoughtful. I didn't get an offer…
Interview experiences · Oura Ring
Oura Ring Software Engineer interview: late visa eligibility decision
The process started out promising, and I felt good as I moved through the rounds. I disclosed my visa requirements at the beginning, completed multiple interviews, and received positive feedback throughout. Communication was solid, and everyone I spoke with seemed professional, so I genuinely thought I was on track. The immigration issue changed things late in the process. After I had spent signi…
Interview experiences · Oura Ring
Oura Ring Software Engineer interview: TypeScript assessment and take-home project
I went through a harder interview loop than I expected. After I applied, the recruiter took a while to get back to me, but once we connected, scheduling moved quickly. The process centered on technical evaluation, including whiteboarding, live coding, and a take-home component in the later stages. The coding parts felt strict and focused on actual expertise, with a high bar for getting the detail…
Interview experiences · Oura Ring
Oura Ring Software Engineer interview where the director did not show
My first round went well. It was an HR conversation, and everything felt smooth and successful. After that, I was scheduled for a technical interview with a director, but the interviewer never showed up. When I followed up, I received no response or explanation for the missed meeting. That was the main problem for me. The interview had been scheduled, I had set aside the time, and then it seemed…
Interview experiences · Oura
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…
Interview experiences · Oura
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…
Interview experiences · Oura
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…
Interview experiences · Oura
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…
Interview experiences · Oura
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…
Interview experiences · Palantir
Palantir Forward-Deployed Engineer interview: referral, decomposition, and long decision wait
After applying with a referral, I went through an HR screen and a decomposition round, then an onsite with three separate interviews on coding, learning, and decomposition. A final hiring-manager conversation ended the process. The format felt deliberate. Even before the onsite, the rounds appeared to build toward the same skill: taking an open-ended situation and making it actionable through bot…
Interview experiences · Palantir
Palantir Intern Software Engineer Interview Experience — Three-Part FDE OA Building a Grocery Coupon System, Watch the Rounding
I got the OA and worked through it in about an hour and a half. Nothing was especially hard, but watch out for rounding. I've organized everything and posted it all below. Part 1 — Initial Problem You're building a discount system for Trader Yojoe's, a growing grocery chain. Their business is thriving, but they're starting a new pilot program where shoppers can bring coupons and apply them to ite…
Interview experiences · Palantir
Palantir Software Engineer 30-minute deployment strategist screen
I expected a heavy technical process, but the first call surprised me. I had a 30-minute phone screen with a deployment strategist, and it went very well. We talked mainly about my resume, projects, and general background. It felt like a conversation about how I think and what I had been doing, not an immediate coding test. I did not receive an offer. What stayed with me was that the early stage…
Interview experiences · Palantir
Palantir Software Engineer interview: algorithms, REST API, and learning loop
After a recruiter call about my background and interests, I took a coding assessment with two medium-style algorithm questions and a REST API task. About a day later, I had a 45-minute technical interview that stayed focused on practical problem solving instead of theory alone. The process then moved into an onsite-style loop about learning and decomposition. In one round, I broke down an ambiguo…
Interview experiences · Palantir
Palantir Software Engineer interview experience
The process began with a basic recruiter call, then an OA, followed by a first technical round that already felt like a moving target. I had to do decomp and debug in the interview flow. The final technical round combined coding and behavioral questions. The journey had a coin-flip quality: it seemed possible to be solid technically and still not proceed, or to perform roughly and still advance d…
Interview experiences · Palantir
Palantir Software Engineer Interview Experience — Graph Code Review, Dijkstra, and a Multithreaded System Monitor
This company isn't that hard — it's basically all repeat questions from previous write-ups on this forum. If you go through the compiled experiences here, you'll run into the exact same problems. Phone screen. Onsite 1 had three technical rounds. Each one also asked some behavioral questions and asked about the projects on my resume. Coding round: a stock question from this forum, exactly the sam…
Interview experiences · Palantir technologies
Palantir technologies Forward-Deployed Engineer interview: decomposition and onsite loop
I applied with a referral and first had a recruiter screen, followed by a decomposition round. I then reached an onsite loop with three interviews covering coding, learning, and decomposition. The rounds felt connected, as if each one was testing whether I could reason through problems in a forward-deployed way. After the onsite, I had a hiring-manager round for the final decision. I did not make…
Interview experiences · Palantir technologies
Palantir technologies Software Engineer interview: coding, REST API, and decomposition
I began with a short recruiter call that felt like a fit and motivation check rather than a technical grilling. I discussed my background and past work, and I got the sense they wanted to know whether I cared about the mission and the real-world impact of the software, not just the title. About a week later, I had a technical screen with a small set of coding questions: a couple of LeetCode-style…