real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Natixis Network Engineer interview: fifteen coding problemsNatixis · Network Engineer · Technical Screen · Jun 2026
After a phone screen, I had two more rounds with hiring managers. The pace was fast but structured. The first two conversations were straightforward; the third was the real stamina test. That last interview was a full sheet of LeetCode-inspired coding problems: roughly fifteen questions in about forty-five minutes. Many were easier problems, but the time limit made the exercise intense. Some requ…
- Navigation Constraints and Mapping SystemsWaymo · Software Engineer · Onsite · Jun 2026
The author lists a Waymo phone screen followed by onsite system-design and coding interviews. The screen involved a robot moving in four directions, returning to its starting point, and avoiding obstacles. The design discussion asked about a vehicle fleet collecting map information. One onsite coding task matched dictionary words against input containing repeated letters. Another used a map with…
- New Relic Software Engineer Interview Experience: good rounds followed by silenceNew Relic · Software Engineer · Technical Screen · Jun 2026No response
The early part moved quickly. I had technical rounds that went well in a single day, then a hiring-manager conversation a few days later. That conversation felt positive, and communication during it was easy and on track. What threw me off was everything afterward. HR went quiet, and when I messaged, I got nothing back. After about a week of silence, I wanted feedback, even negative feedback, bec…
- Northrop Grumman Software Engineer interview with a one-hour behavioral roundNorthrop Grumman · Software Engineer · Other · Jun 2026Offer
I started with a recruiter introduction call, followed by a one-hour behavioral interview with a manager. The questions were fairly standard for an entry-level software engineering track, and they didn’t go deeply into complex technical trivia. There was no presentation, and the process felt organized and smooth. I spent most of the interview explaining my experience clearly and answering behavio…
- Northrop Grumman Software Engineer onsite with LeetCode-style questionsNorthrop Grumman · Software Engineer · Onsite · Jun 2026
I was contacted and ended up in an in-person interview focused on LeetCode-style questions. It felt more intense than the behavioral-heavy rounds I'd heard about. Once I was in the room, the interview was clearly testing problem-solving. I didn't get immediate closure afterward. A recruiter followed up and scheduled another phone conversation, so the process wasn't over right away. The format was…
- Northrop Grumman Software Engineer onsite with senior engineersNorthrop Grumman · Software Engineer · Onsite · Jun 2026Offer
I had a straightforward onsite interview in a conference room with a couple of senior engineers. The difficulty felt entry level, and the focus was on discussing my background and how I described my experience. The room dynamic stood out. The senior interviewers listened closely, and I had to explain clearly what I had worked on and how I approached engineering tasks. It was a direct, in-person c…
- Notion Labs Software Engineer Interview Experience: fast updates and a thoughtful closeNotion Labs · Software Engineer · Jun 2026Rejected
A recruiter reached out, and the process moved quickly after that. I received email updates soon after each stage, and every interviewer I met was friendly and easy to work with. The whole experience gave me the sense that candidate experience mattered to them. The recruiter call focused on logistics, but its warm and understanding tone put me at ease before the technical work. Nothing in the res…
- NPCI Full Stack Engineer Interview Experience: core Java, OOP, and a React questionNPCI · Full Stack Engineer · Technical Screen · Jun 2026
The interview began immediately with an introduction about me, then moved into core Java and OOP fundamentals. I was asked about inheritance and how I would implement it in a small Java program. I needed to explain the code clearly, including what it did and how its pieces worked together. The discussion went deeper into Java-internals topics. I was asked about the diamond problem and how HashMap…
- NVIDIA QA Engineer Interview Experience: Python, systems, and VP troubleshootingNVIDIA · QA Engineer · HR Screen · Jun 2026
The process started with an HR interview, then moved into a technical conversation on Python, Linux, networking, QA methodology, and systems knowledge. It felt like they were assessing how my experience would translate to QA work on a real platform, rather than whether I knew the right buzzwords. The last stage was a more demanding VP interview. We discussed previous projects, troubleshooting sce…
- Nyc Staffing Software Engineer Interview Experience: a mobile role with mismatched screeningNyc Staffing · Software Engineer · Technical Screen · Jun 2026
My recruiter screen was about a week after I applied and felt generic. They asked a couple of questions about my resume but gave little detail beyond the posting. I then shared availability for a hiring-manager round that was scheduled about two weeks away. What I heard about the hiring manager made me think I would be a strong fit. A few days later, I was asked to arrange a technical screen. Aft…
- Onsite Coding and Job Scheduler System Design, No OfferSnowflake · Software Engineer · Onsite · Jun 2026Rejected
Coding: this was an OO design problem I hadn't seen anywhere on the forum before, implementing two functions. One function is addTask(taskId, priority, timestamp) — the same task can be added multiple times at different timestamps. The other is executeTask(), which is the tricky part — you first sort by priority, and if a task has already been executed, you skip it. System design: job scheduler.…
- Onsite Word-Guessing Algorithm Question, No OfferFlexport · Software Engineer · Onsite · Jun 2026Rejected
This year, all the onsite questions were new ones -- job hunting is really tough this year. Hoping this helps other people who are also job hunting. Phone screen: an algorithm question. Given a bunch of meeting start and end times, output the total time spent, counting any overlaps only once. Follow-up: if there's overlap, you'd need multiple meeting rooms -- find the minimum number of meeting ro…
- Oracle Health Account Executive interview: a late recruiter call and unanswered concernsOracle Health · Account Executive · Jun 2026Rejected
My process began with a recruiter interaction that already made me uneasy. The recruiter was late, and the tone felt cold and dismissive. People already in the role had told me the process should be simple and that I would not be expected to know everything. I went through the interview steps anyway and was ultimately rejected without meaningful feedback. What stayed with me was not only the miss…
- Orange Software Engineer interview: long coding and salary discussionsOrange · Software Engineer · Technical Screen · Jun 2026Offer
The process made me feel that time and professionalism were not handled well. One interview was extremely long, combining live coding with a prolonged discussion afterward and running late into the evening, while people were still working around me. I passed the technical parts, but the overall atmosphere never became comfortable. At another time, the process felt equally shaky because I was prom…
- Oscar Health Software Engineer interview: algorithms, system design, and manager roundOscar Health · Software Engineer · Technical Screen · Jun 2026
A recruiter contacted me on LinkedIn, and the process became three rounds. I started with a technical phone screen. The next round covered both an algorithms-style screen and system design, and the final stage was a manager screen. I would not say every detail went perfectly smoothly, but the structure held together: technical evaluation first, then a leadership conversation at the end. I was not…
- Oscar Insurance Software Engineer interview: technical funnel to manager screenOscar Insurance · Software Engineer · Technical Screen · Jun 2026
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…
- Oura Ring Software Engineer interview: late visa eligibility decisionOura Ring · Software Engineer · Technical Screen · Jun 2026
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…
- Oura Software Engineer interview with late immigration constraintsOura · Software Engineer · HR Screen · Jun 2026
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…
- Palo Alto Networks Software Engineer interview: three-hour mixed evaluationPalo Alto Networks · Software Engineer · Online Assessment · Jun 2026
I began with an online HackerRank completed on my own. Next came behavioral questions on HireVue, without video recording. A recruiter call followed with the usual request to walk through myself and similar basics, meant to confirm fit and direction before the deeper stages. The next step was the largest one. The recruiter said it would take around three hours, and that was how it played out: rou…
- Passed VO1 With a Billboard Rotation Coding Round and an ML Job Scheduler System DesignNetflix · Software Engineer · Onsite · Jun 2026In progress
Netflix's VO (virtual onsite) has two rounds — VO1 and VO2. VO1 is more general. VO2 leans into stuff related to the specific team you're interviewing with. I'll share VO1 here. Coding: movie billboard rotation. Don't use a heap — use two treemaps. Two followups total: 1) multi-threading, 2) how you'd scale it in production and how you'd store/access the data. SD: schedule ML jobs. The main point…
- Pinterest Software Engineer interview: route reconstruction and Sparse MatrixPinterest · Software Engineer · Jun 2026Offer
I expected Pinterest to be intense, but the technical interview was surprisingly light. There were only two coding questions, and both were straightforward enough that I felt a little underwhelmed afterward. One asked me to reconstruct routes from unordered travel tickets. The other was to implement a Sparse Matrix class. I had prepared with PracHub case studies, which gave me a useful structure…
- Plaid Account Executive interview: behavioral phone screen and Zoom meetingPlaid · Account Executive · Other · Jun 2026Rejected
My process started with a behavioral interview over the phone, followed by a formal Zoom meeting. The sequence felt structured from the beginning. I didn't run into any major problems during the conversations, but I didn't make it to the final round. The experience ended sooner than I had hoped, and I was disappointed that the last stage never happened for me. I didn't get an offer, though I appr…
- Plangrid Account Executive interview: strong early rounds and no follow-upPlangrid · Account Executive · Jun 2026No response
The beginning of my process was genuinely positive. People were friendly and professional, and I found the conversations engaging as I went through several rounds. I eventually gave a presentation and had a final skip-level interview with senior leadership. At that point, I felt good about how everything had gone. After that last round, the communication stopped. I waited without a clear update,…
- Plangrid QA Automation Engineer interview: practical QA panelPlangrid · QA Automation Engineer · Jun 2026
After a recruiter call, I spoke with the hiring manager and then went to a technical panel with developers, QA, and devops. The hiring-manager conversation focused on behavioral questions. I also walked through an app I had tested and explained what they could expect from my approach. The panel was built around practical problem-solving. I got some leet-code style questions, while the group also…
- Powerschool Account Executive interview: five interviews and delayed follow-upPowerschool · Account Executive · HR Screen · Jun 2026No response
For an entry-level sales role, the process involved many steps, although communication was transparent while it was happening. After a recruiter call, I went through five interviews: an HR interview, a conversation with my direct boss, and three separate interviews with team members. The questions were typical for the role. They covered my background and how I would approach client, sales, and ro…
- Prime Video Network Engineer Interview Experience: opaque online tasks without an offerPrime Video · Network Engineer · Jun 2026
After applying, I went through something that did not resemble a traditional interview. I was told I would be "successful" after completing a set of tasks, but the process mostly involved online work, watching videos, and answering questions. There was no clear, standard interview to prepare for in the usual way. Feedback itself came fairly quickly. A few days later, I got an email saying I had b…
- Prime Video Software Engineer Interview Experience: broad fundamentals and leadership themesPrime Video · Software Engineer · Online Assessment · Jun 2026
The process had a looping structure. It began with an online assessment, then moved through data structures and algorithms, basic OOP and DBMS concepts, and Amazon leadership principles. There was also an HR interview and a low-level design component, so the process covered a broad mix rather than one narrow subject. I learned about the steps as things progressed. The leadership-principle part st…
- Prime Video Software Engineer Interview Experience: high-pressure coding and design roundsPrime Video · Software Engineer · Other · Jun 2026
I began with a LeetCode-style coding round and solved two DSA problems, one medium and one hard. I had to explain my thinking, cover edge cases, and give time and space complexity. The interviewer kept asking about alternative approaches and the trade-offs behind them. Next came system design. I worked through a problem resembling a scaled Amazon-style service and discussed API design, data model…
- Prime Video Software Engineer Interview Experience: leadership, coding, and system designPrime Video · Software Engineer · Online Assessment · Jun 2026
After applying, I completed an online assessment and then spoke with a recruiter. About a week later, I entered an onsite loop. From the assessment through the final decision, the process took roughly a few months. The loop had multiple back-to-back rounds in one day, mixing technical and behavioral evaluation. Early on, the bar raiser focused on Amazon-style leadership principles. I used STAR-st…
- Prime Video Software Engineer interview: DSA screening and technical loopPrime Video · Software Engineer · Jun 2026
The Prime Video process opened with a conversation about my resume and experience, then moved immediately into technical work. The first serious step covered mid-to-hard DSA: dynamic programming, matrix-related problems, and graph questions. They wanted to hear the approach I planned to take before I started. The screening and loop followed what felt like a standard order. The phone interview was…
