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
- Rippling Software Engineer interview experience: financial precision codingRippling · Software Engineer · Technical Screen · Jul 2026
The coding challenge was the familiar driver-delivery system problem, and I had heard that Rippling used a relatively small pool of widely discussed questions. Financial representation mattered a great deal during the implementation. I had to justify using a particular numeric type instead of floating point. A copilot-style assistant inserted changes that did not meet the precision requirements.…
- Rippling Software Engineer interview: a dismissive phone screenRippling · Software Engineer · Technical Screen · Jul 2026Rejected
I applied online, and a recruiter contacted me a couple of weeks later to arrange a technical phone screen. The process went badly quickly because the interviewer seemed disengaged from the start. I was interrupted almost immediately during my introduction and could not finish it. The interviewer moved to the coding question and kept their camera off for most of the session. I still solved the pr…
- Rippling Software Engineer interview: CodePair rules and a quick recruiter turnaroundRippling · Software Engineer · Online Assessment · Jul 2026
I applied online, completed an online assessment, and then passed it. Recruiting invited me to schedule the next interviews. The process was organized, with a scheduling email that included prep resources: an overview video and links to an official interview kit. My first scheduled round was a one-hour technical interview with a Software Engineer II on CodePair. The session was recorded for train…
- Rippling Software Engineer interview: intern assessment in progressRippling · Software Engineer · Intern · Online Assessment · Jul 2026In progress
I was interviewing for a Full Stack Software Engineer Intern role, rather than the general software-engineer track. Early on, I completed a HackerRank assessment with 4 multiple-choice questions and 3 coding questions. Recruiting then invited me to a coding and algorithms interview with an engineer. Their communication was clear and professional, and I knew what came next. When I described the ex…
- Rippling Software Engineer interview: referral and familiar questionsRippling · Software Engineer · Jul 2026Offer
I came through a referral, and the initial call felt conversational rather than gatekeeping. Within about two and a half weeks, I had a technical coding interview and a behavioral interview. The coding questions asked for the first non-repeating character in a string and validation of parentheses. I had practiced something similar on PracHub just beforehand, so the patterns felt familiar and help…
- Rivian Software Engineer Interview Experience: OOP problem and delayed progressionRivian · Software Engineer · HR Screen · Jul 2026
After a recruiter screen, I answered resume-based behavioral questions and then had a technical interview built around an object-oriented problem tailored to the team. It seemed focused on how I reasoned, not only whether I could write code. There was also a short hiring-manager meeting, followed by bundled technical rounds: a coding round and a conceptual round, about half an hour each. Scheduli…
- Robert Slack Software Engineer interview experienceRobert Slack · Software Engineer · Online Assessment · Jul 2026No response
A few business days after applying, I received an interview invitation and began with a HireVue-style recording. It was highly automated: I read behavioral prompts and had a small window to record each answer on camera. I could redo answers a couple of times, but there was no interaction or sense of whether my answers landed. Near the end, the same session included coding. I could not ask clarify…
- Roblox Software Engineer interview: challenging but relaxed SuperdayRoblox · Software Engineer · Online Assessment · Jul 2026
After applying online, I took an online assessment built around game-style problem solving. The Superday itself was tough, though most interviewers were laid back and friendly. The technical side leaned heavily on numerous LeetCode-style questions in the medium-to-hard range. The behavioral questions were not just warmups. They were difficult enough that I had to be specific about how I would han…
- Rocket Lab Software Engineer interview: technical rounds, presentation and an onsite tourRocket Lab · Software Engineer · Technical Screen · Jul 2026
The process lasted a little over a month. After a recruiter call, I waited a week or two for a virtual hiring-manager interview, then had a technical interview with an engineer on the team. Those conversations followed a similar pattern: my resume, how I'd handled previous work and engineering fundamentals such as debugging and problem solving. The later stages were more demanding. I needed to de…
- Rocket Lab Software Engineer interview: technical-project presentationRocket Lab · Software Engineer · Technical Screen · Jul 2026
A recruiter scheduled the interview, which began with a presentation about my strongest technical project. The rest was a conventional mix of technical and behavioral conversations about my engineering experience. The process seemed designed to connect what I had built with how I solve day-to-day problems. There were no extreme gotchas, just steady evaluation of my technical approach and team fit…
- Rockstar Games QA Engineer Interview Experience: realistic testing role discussionRockstar Games · QA Engineer · HR Screen · Jul 2026
After applying, I had an HR-led process that walked through my resume, experience, and fit. The tone was relaxed but professional. We talked about why I was drawn to testing, what kept me interested in gaming, and the background relevant to the role. They also made sure I understood that QA did not mean playing games all day. Scheduling was slow, but the recruiter stayed in touch and felt approac…
- Rockstar Games Software Engineer interview: coding track and logisticsRockstar Games · Software Engineer · Other · Jul 2026Rejected
The process opened with a recruiter screen and moved directly into a technical track. In one version, the initial coding test covered basic Java, Spring Boot, SQL, and some problem solving. After that, I had a focused, practical screening or technical discussion with senior people. Later stages included a live CoderPad-style assessment with problems described as similar to LeetCode, followed by a…
- Rockstar Games Software Engineer interview: FiveM and RedM community assessmentRockstar Games · Software Engineer · Online Assessment · Jul 2026Rejected
My recruiter conversation covered my background, experience and interest in Rockstar. A little later, I met members of the Community team for a deeper interview about community management and creator relationships. We worked through ways to handle issues in the FiveM and RedM communities. The next step was a timed written assessment on CoderPad. It covered more than coding: I responded to communi…
- Rockstar QA Engineer Interview Experience: resume, gaming, and QA fitRockstar · QA Engineer · HR Screen · Jul 2026
I began with HR going through my resume step by step. We discussed prior work, why I wanted QA, and my interest in gaming and testing. The interviews stayed friendly and professional. The questions covered my familiarity with Rockstar titles, how I found issues, and why I fit the role. Talking naturally about gaming helped because it kept returning as a theme. Responses sometimes took longer than…
- Rockstar Software Engineer interview: community scenarios and an eleven-week processRockstar · Software Engineer · Online Assessment · Jul 2026Rejected
After speaking with a recruiter, I moved into interviews focused on the community side of the role. The first deeper conversation was with the Community team. We discussed community management and creator relations, including what I'd do when situations didn't go as expected and how I'd maintain relationships with creators and the wider audience. Next, I completed a timed written assessment on Co…
- Rockstar Software Engineer interview: Java, Spring Boot, and SQLRockstar · Software Engineer · Other · Jul 2026
I started with a coding test covering Java, Spring Boot, SQL, and some problem-solving prompts. It was a practical check across the stack, so I had to do the work rather than simply talk through what I might do. After that came a screening step and then a technical discussion with senior people. That conversation was more about how I approached problems and reasoned through solutions than about w…
- Rokt Software Engineer interview: CCAT, personality test, and one-way videoRokt · Software Engineer · Jul 2026No response
After applying, I was put through an automated sequence. First came the Criteria Cognitive Aptitude Test and the Employee Personality Profile. The CCAT was a timed, IQ-style block with pattern-recognition and math-style items. The personality portion took about 10 to 12 minutes and had no time limit. Some prompts were straightforward enough that it did not feel like a serious gatekeeping exercise…
- RTX Software Engineer interview: manager conversation and fast offerRTX · Software Engineer · New Grad · Technical Screen · Jul 2026Offer
I had an hour-long Zoom meeting with a manager for a new-grad role. I expected it to be more intimidating, but it was smoother than I expected. She explained what the team did and asked behavioral questions along with a few technical questions linked to my experience. The conversation covered my background, why I wanted to work at RTX, and how my experience fit the job. An offer arrived within an…
- RTX Software Engineer interview: projects, circuits and technical depthRTX · Software Engineer · Technical Screen · Jul 2026
I expected a mostly behavioral interview, but it became more technical. I discussed my projects and problem-solving approach, then answered questions about diodes and impedance and calculated current in a simple resistor circuit. Even in the casual format, the interviewer seemed to be looking for understanding rather than buzzwords. I was also able to choose technical topics from my background. I…
- RTX Software Engineer interview: short hiring-event fundamentals checkRTX · Software Engineer · Technical Screen · Jul 2026Offer
I attended an RTX hiring event with interviews compressed into 30-minute slots. The process felt low-pressure and straightforward, and most of the discussion was behavioral. There were still a couple of technical questions to check programming proficiency, including how to find the least child in a binary tree. Because the time was short, the discussion stayed on basics and clear answers rather t…
- Rubrik Account Executive interview: several meetings in a few daysRubrik · Account Executive · Onsite · Jul 2026Rejected
The process gained momentum quickly, with several stages packed into a few days. I had three face-to-face conversations and then a final session. Almost as soon as that last conversation began, I felt off balance. I was thrown by the first sentence and never quite recovered. The tone and pace left little room to reset. I didn't advance, but I received clear feedback and respected how direct they…
- Rubrik Software Engineer interview: coding depth and uneven later roundsRubrik · Software Engineer · Technical Screen · Jul 2026
Recruiting contacted me early, then I had a direct technical screen: solve a medium-to-hard coding and data-structure problem with the interviewer on the call and explain my reasoning. The interviewer gave hints when I was stuck, but the question demanded real understanding of the data structure. I left feeling that problem was the main filter. Later rounds included system coding and concurrency.…
- Safran Software Engineer interview: written aptitude and technical testSafran · Software Engineer · Online Assessment · Jul 2026
I remember a fairly structured process. After an initial recruiter discussion, I later completed a short written test with aptitude and technical questions. I had only 45 minutes to finish the whole test. That was followed by two interviews. The first covered basic questions related to the field. The second was more application oriented and lasted about 30 to 45 minutes. The whole process felt me…
- Sage Software Engineer interview experienceSage · Software Engineer · Technical Screen · Jul 2026
After a recruiter call, I had a technical screen of about an hour and then an HR conversation of around 30 minutes. The atmosphere was calm and not overly intense. I never felt set up to fail. The technical discussion drew heavily on my background and resume projects, then covered OOP, web-development basics, some distributed-systems ideas, and a couple of AIML questions. The interviewers were kn…
- Salesforce Account Executive interview with a three-stage in-person panel and account strategySalesforce · Account Executive · Onsite · Jul 2026
The recruiter process was organized and supportive. I got guidance that made the next steps clearer, along with preparation materials that helped me understand the expectations. The flow appeared to have three stages, with the last round as an in-person panel. The interviews were structured and purposeful. Instead of asking the same behavioral questions repeatedly, each interviewer focused on a d…
- Salesforce Account Executive interview with Dublin relocation questions and mismatched rejection feedbackSalesforce · Account Executive · Jul 2026Rejected
After a couple of early steps that felt fairly normal, the process broke down at the fourth stage. I had been told that the third interview would focus on my motivations and details around relocating to Dublin, so I prepared for that context and answered accordingly. When the rejection feedback finally arrived, it cited commercial skills that, as far as I understood, had never been asked about or…
- Salesforce Account Executive interview: demoralizing recruiter processSalesforce · Account Executive · Jul 2026
The recruiters made me feel as though my time was something I should be grateful to spend, and I did not feel heard. They seemed to move through checklists and pass me to other recruiters to see which openings existed. The process dragged with gaps in communication. I was asked whether I would take a lower role to get in, with the implication that others step back to join Salesforce. By the hirin…
- Salesforce Customer Success Engineer interview experienceSalesforce · Customer Success Engineer · Technical Screen · Jul 2026
After speaking with the recruiter, I had a technical round where I discussed my project experience and worked through a piece of provided code. I was asked to make the code more production-ready, and the coding-style questions connected back to OOP concepts. The later managerial round focused on customer work: how I would handle situations, manage relationships, and name a few Salesforce products…
- Salesforce Customer Success Engineer Interview Experience: HackerRank through techno-managerialSalesforce · Customer Success Engineer · Online Assessment · Jul 2026
My process had three direct rounds. First came an online HackerRank coding session focused on problem-solving. Then I had a technical round that covered Stack versus Heap, debugging a snippet to find the cause of a NullPointerException, and HTTP methods. The final step was described as techno-managerial. That fit the overall process: I expected to show technical grounding while also explaining ho…
- Salesforce Software Engineer interview: DFS and scalable-system designSalesforce · Software Engineer · Jul 2026
My process began with a recruiter screen and then a technical round built around a hard LeetCode-style DSA problem that leaned heavily on DFS. I spent the session working through the approach and tradeoffs while trying to keep my reasoning clear. After that, I had a high-level design interview about scalability and reliability. It pushed me beyond an immediate coding solution toward how a system…
