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
- Oracle Account Executive interview: easy call, poor follow-throughOracle · Account Executive · HR Screen · Jul 2026Rejected
One process began with a short recruiter conversation that felt easy and genuinely smooth. It lasted about 10 to 15 minutes, and I received positive feedback about the call, yet I was rejected afterward. A follow-up message after the call was never answered. In another run, the recruiter side broke down. The recruiter seemed careless and unprofessional, did not give useful detail about the role,…
- Oracle Health Account Executive interview: an Oracle Eats mock cold callOracle Health · Account Executive · Other · Jul 2026Offer
After a recruiter call, I went through interviews that increasingly focused on how I'd handle a sales scenario. Near the end, I answered behavioral questions and took part in a mock cold call selling something called "Oracle Eats." That exercise felt like the biggest hurdle. I needed to think and respond under pressure as well as explain my background. The process seemed focused on fit and carryi…
- Oracle Health Account Executive interview: brief and unresolvedOracle Health · Account Executive · HR Screen · Jul 2026Rejected
I began with a short HR interview of about 10 to 15 minutes, and it went smoothly. The recruiter gave me positive feedback, so I was surprised to be rejected later. A follow-up email also received no response. It was a brief experience with a friendly tone at the start, but the later silence left it feeling incomplete. The biggest surprise was how quickly it ended despite the initial positivity.…
- Oracle Health Account Executive interview: missed interviews and frozen positionOracle Health · Account Executive · Other · Jul 2026Rejected
The recruiter experience started badly and never recovered. I found the recruiter unprofessional and more focused on getting through the process than helping me understand the role. My questions went unanswered, and even after several follow-ups I still did not know the next steps. I was also missed for an interview I had been scheduled to attend. When I was booked to speak with a VP of sales, I…
- Oracle Health Account Executive interview: mock call and behavioral stepsOracle Health · Account Executive · HR Screen · Jul 2026
After speaking with the recruiter, the process felt relaxed and early stage. I expected sales-heavy questions, but the conversation was broader: who I was, my experience, what I wanted, and the basics of the account executive role. It felt like a real conversation rather than a grilling. About a week later, I moved into two interviews. The flow included a mock call and a behavioral component, and…
- Oracle Health Software Engineer interview: five-hour loop and existing Java codebaseOracle Health · Software Engineer · Technical Screen · Jul 2026
A recruiter contacted me about two weeks after I applied. The recruiter call was basic, and a technical screener was scheduled for the following week. That first technical conversation was friendly and straightforward, almost a check on basics such as if-else control flow. The final loop was much harder to arrange: five separate one-hour interviews spread across a week, and I took PTO to make it…
- Oracle Health Software Engineer interview: four interviews and a two-week offerOracle Health · Software Engineer · Technical Screen · Jul 2026Offer
The process felt well organized. Some of it was technically challenging, but I never felt completely lost. After a recruiter conversation, I moved through a sequence that added up to four interviews. The discussions were professional and engaging, progressing from core coding to broader engineering questions. I worked through a live LeetCode-style algorithms and data structures question. The rest…
- Oracle Health Software Engineer interview: LRU cache under pressureOracle Health · Software Engineer · Technical Screen · Jul 2026Offer
My interview loop was tougher than I expected, although the overall tone was engaging. Across several technical rounds, I implemented an LRU cache and solved a course-prerequisite-ordering problem. The pace kept me on my toes and made it hard to relax into the problems. The last round became more intense with an optimization-style challenge: maximizing the container area between vertical lines. I…
- Oracle Health Software Engineer interview: trade reconciliation and low-level designOracle Health · Software Engineer · Jul 2026
My loop began with a detailed low-level design round where I designed a trade reconciliation service. The interviewer was knowledgeable and helpful, but the bar for clarity and completeness felt strict. I left realizing that my preparation had gaps. Later rounds were more focused. One was described as basic DSA. Another drilled into my projects, asking me to defend design decisions rather than ju…
- Oracle Software Engineer interview: intern technical sequenceOracle · Software Engineer · Intern · Online Assessment · Jul 2026Offer
For a Software Developer Intern role, I went through an online assessment, three technical interviews, and an HR interview. The process felt positive and straightforward, and the panelists were friendly. They concentrated on problem solving, understanding my own projects, and core computer-science basics instead of trying to catch me with trick questions. The questions still required real fundame…
- Oracle Software Engineer interview: LRU cache and course orderingOracle · Software Engineer · Other · Jul 2026Offer
The technical rounds were more demanding than I expected. The questions did not seem unfair, but the interviewer energy and live problem-solving pace kept me switching gears. I implemented an LRU cache and then worked on a course-prerequisite ordering problem, which made me think about ordering constraints as well as code. The final round was the most stressful. I had to maximize the area trapped…
- Oracle Software Engineer interview: panel rounds and a quick offerOracle · Software Engineer · Technical Screen · Jul 2026Offer
The process felt smooth and organized, and it did not start with technical questions. I first had a screening-style call where the team explained what to expect and set the context. After that, I moved to team interviews that focused more directly on what I could do. I completed two panel rounds, one technical and one behavioral, with questions aligned to the team's interests. The technical panel…
- Order-Matching HackerRank Then a Quant Systems Deep DiveTwo Sigma · Quantitative Software Engineer · Technical Screen · Jul 2026
Round 1: HackerRank Coding — Stock Exchange / Order Matching The task was to implement buy/sell order matching: Buy side uses max priority. Sell side uses min priority. Match orders when the price can cross. Handle partial fills. Output trade records. Handle the remaining resting orders. Follow-ups: How to add more tests to increase confidence. Why my output didn't match the sample. How multiple…
- Oscar Health Business Analyst interview: quick recruiter response while the process continuedOscar Health · Business Analyst · Jul 2026In progress
After I applied, the recruiter responded quickly, which gave the process a positive start. The culture seemed to match what I was hoping for, and communication felt efficient compared with other processes I had experienced. When I wrote about it, I was still in the middle of the process and had not received an offer. I was waiting for the next steps and hoping to hear back soon because I had like…
- Oscar Health Software Engineer interview experienceOscar Health · Software Engineer · Technical Screen · Jul 2026
Recruiter outreach was quick. After a short recruiter call with basic Q&A, I went to a technical screen that was essentially a hard, tightly constrained LeetCode-style coding task. I was warned that the question would be challenging, and it was. I did not have a comparable pattern fresh in mind, and getting to a complete answer inside the time limit was difficult. The interviewer seemed to know t…
- Oscar Health Software Engineer interview: silence after codingOscar Health · Software Engineer · Technical Screen · Jul 2026No response
The recruiter call was routine, followed by a LeetCode interview. If that went well, I was told the next steps would be a two-hour LeetCode session and a system-design interview. I thought I had done well enough and left feeling that the rounds had gone well. Then the company went silent. I followed up after about a week and still never heard back. That was the frustrating part. Everything before…
- Oscar Insurance Software Engineer interview: ghosted after codingOscar Insurance · Software Engineer · Technical Screen · Jul 2026No response
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…
- Oura Ring Software Engineer interview: clear timelines and practical roundsOura Ring · Software Engineer · HR Screen · Jul 2026
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…
- Oura Software Engineer interview: calm and responsive processOura · Software Engineer · HR Screen · Jul 2026
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…
- Palantir Forward-Deployed Engineer interview: referral, decomposition, and long decision waitPalantir · Forward-Deployed Engineer · HR Screen · Jul 2026Rejected
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…
- Palantir Software Engineer 30-minute deployment strategist screenPalantir · Software Engineer · Jul 2026
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…
- Palantir Software Engineer interview experiencePalantir · Software Engineer · Online Assessment · Jul 2026
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…
- Palantir Software Engineer interview: algorithms, REST API, and learning loopPalantir · Software Engineer · Technical Screen · Jul 2026
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…
- Palantir technologies Forward-Deployed Engineer interview: decomposition and onsite loopPalantir technologies · Forward-Deployed Engineer · Onsite · Jul 2026Rejected
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…
- Palantir technologies Software Engineer interview: coding, REST API, and decompositionPalantir technologies · Software Engineer · Technical Screen · Jul 2026
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…
- Palo Alto Networks Software Engineer interview experience: missed interview follow-upPalo Alto Networks · Software Engineer · Jul 2026No response
The technical content was not what defined this process for me. Recruiter contact started well, then communication stopped. My emails and phone outreach went unanswered, and even an interview that had been scheduled did not happen as expected. There was a no-show situation where I was left waiting without follow-up. That missed interview felt secondary to the larger problem: I never received any…
- Palo Alto Networks Software Engineer interview: project decisions and AIPalo Alto Networks · Software Engineer · HR Screen · Jul 2026
After applying, I had a recruiter phone screen about my experience and the technologies I had used. Soon afterward, the technical discussion focused on how I had built real projects: one project in depth, the design decisions I made, and the trade-offs behind them. That conversation also included how I had considered adopting AI in my current work. Coding-related exchanges were woven into the pro…
- Paychex Software Engineer interview: take-home and load testingPaychex · Software Engineer · HR Screen · Jul 2026
After speaking with the recruiter, the process moved quickly into structured technical work. I had a technical screen with clear questions about my experience, then a longer coding take-home. Afterward, we reviewed my solution and covered more basic technical questions about fundamentals and how I approached the problem. Next came a longer manager discussion with behavioral questions and addition…
- PayPay India Backend Engineer Interview Experience: Perfect test score, rejectionPayPay India · Backend Engineer · Jul 2026Rejected
I applied online and quickly received an automated CodeSignal link. I completed four questions and scored 600 out of 600. There was no recruiter conversation, only the test and then a wait. About a week later, I received a rejection email. It made me suspect scoring was being used as an automatic filter without real human review, and left a bitter impression that felt like ghost hiring. Location:…
- PayPay India Backend Engineer Japanese-language assessment experiencePayPay India · Backend Engineer · Online Assessment · Jul 2026Rejected
After applying, I took an online coding assessment and then reached a first-round interview. The assessment had four algorithm problems. One was a simulation task that required careful edge-case handling rather than only straightforward logic. I passed the assessment and had a technical interview, but did not move past the next step. The emails and interview communication were all in Japanese, so…
