READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 111 of 153
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — A News Aggregator Design Followed by a Fast Rejection
The system design phone screen used the news aggregator problem from the question bank, and all of the questions were standard. I had prepared this problem carefully, so I thought my answer went well. I also answered every follow-up, and the interviewer seemed satisfied with my responses. Even so, I received a rejection about ten minutes after the interview ended. The result and its timing left m…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — A Poker OOD Question I Didn't Practice For
Just finished a fresh Rippling phone screen, so let me write it up while it's still fresh. The question was an OOD problem based on a poker game — I pasted the full prompt below. Going into this interview I mainly grinded Delivery Cost System and Expense Rules System OOD. I did see this Poker question when I was collecting interview reports beforehand, but I only skimmed through the approach once…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — An AI-Assisted Coding Round on Poker Hand Comparisons
Continuing from my last post. Round 1 One of the interviewers asked upfront whether I wanted the AI-assisted question or the non-AI one. I picked AI. Question 1 The problem was similar to comparing two poker hands: you're given a bunch of rules for ranking hands, the input is two string arrays, and the output is user1 or user2. I started by stating a few assumptions and clarifications, then analy…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — An AI Coding Edge Case with Filtered Parent Tasks
This AI coding phone screen ended in rejection. Sending the problem directly to an AI could miss an important edge case: if a parent is filtered out, its child task should be filtered out as well. One test case for that behavior was: The fourth task was unrelated and should remain in the result, while the parent and grandchild should not appear because the grandparent was filtered.
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — An Extensible Expense Rule Engine
In the Rippling phone coding interview, I was given a set of expenses and rules. I needed to run every rule against every expense and identify each rule that the expense violated. An expense looked like this: Example rules included: Total expense should not be greater than 175. A restaurant seller should not have an expense greater than 45. An entertainment expense should not be charged. The meth…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Coding a Reimbursement System With Group Limits
The interviewer said the question was the same as what's already on the forums — build an expense reimbursement system that can freely apply different approval rules to decide whether someone's submitted expense meets the requirements and can be paid out. I also got to the second part of the question: after you've built a reimbursement approval system, can you further group reimbursements by some…
Interview experiences · Rippling
Rippling Software Engineer interview experience: coding, system design, and AI use
My loop followed the familiar structure of several coding rounds followed by broader rounds. I completed three coding rounds, then a high-level system design round, and finished with a hiring-manager round. AI was allowed in the process, which made it feel different from stricter interview settings. The work meant solving coding problems in sequence, switching to system design, then meeting the h…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Delivery Billing and Rounding Decisions
The author describes a Rippling recruiter screen followed by an hour-long HackerRank technical interview where AI assistance was encouraged. The recruiter discussed project impact, responsibilities, motivation, AI-tool use, and practical job requirements. The coding exercise tracked delivery costs using driver rates that could change over time. Important requirements included ignoring duplicate d…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Explaining an Expense Rules Engine Before Using AI
The author reports passing Rippling’s first AI-assisted interview, which used an expense-policy evaluation exercise. Their approach began with discussing requirements and edge cases, then outlining classes and basic functions while explaining design decisions. This initial work took more than 20 minutes. Only afterward did the author ask AI to complete implementation details within that structure…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Extensible Five-Card Poker Evaluation
Write a simplified version of Texas Hold'em. Given two five-card hands, compare them and determine the winner. The design needed to use object-oriented principles, pay attention to code style, and be extensible. Game Rules Goal: Compare two five-card hands, hand_1 and hand_2, and determine the winner. Card values: 9 is the highest value and 1 is the lowest. There are no letter cards such as ace,…
Interview experiences · Rippling
Rippling Software Engineer interview experience: financial precision coding
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.…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Missing the One Case the Forum's Writeup Left Out
It's the courier question that's already up on the forum, and the forum write-up was already very detailed! But there's one thing it left out: the same dasher can take multiple orders at the same time. When I was practicing beforehand I hadn't considered that case, and I hadn't seen it mentioned on the forum either, so when the third, concurrent follow-up came out, I had to think about it for a b…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — One-Hour AI-Assisted Phone Screen on Camel Cards
The phone screen was one hour, and the question was one of the ones people have already posted about: Camel Cards. I picked the option where the AI helps write the code. A hand has 5 cards, and there are 7 hand types in total, each with its own weight, ordered from strongest to weakest. Part one: first I read the problem and made clear that I would create 1 abstract class HandType and 1 class Han…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Onsite AI Coding Round with Live Prompting
Recruiter reached out to me on LinkedIn. They scheduled a phone screen first — system design, on a news aggregation system. The interviewer was very nice. A week later they told me I'd passed. Then they scheduled a chat with the hiring manager about my project. A week later they told me I'd passed that one too. Onsite was two days, three rounds. System design: they asked me to design a hotel syst…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Onsite System Design on a Metrics Monitoring System, Passed
Unlike what I've seen in other write-ups on the forums, I don't know if they changed the question or if there are now two system design question pools for the onsite (Google News / a metrics monitoring system) — I got the monitoring system one. The gist was: collect some user behavior data, like installs / user clicks / etc, and it needed both a real-time view and collection of raw events for a b…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Phone Screen and Onsite Reject, Struggling With the AI-Coding Rounds
First round phone screen: I picked AI coding, and it was the logger question that's been posted on the forum. Roughly: the first question was to implement the following functionality, where each feature could be triggered and then print out the logger: Removes all occurrences of a configured string before printing. Truncates the message to a max number of characters before printing. Capitalizes t…
Interview experiences · Rippling
Rippling Software Engineer Interview Experience — Three Onsite Rounds and the Fastest Feedback I've Seen
I'm giving back to the forum. It took me 6 months of searching, but I finally landed an offer. I have 3 years of experience and interviewed for an SDE II role. Recruiter Pretty standard: why are you looking for a new opportunity, why Rippling, an introduction to the company, and then questions about sponsorship needs. Coding For the coding round, you can choose to use AI or write the code by hand…
Interview experiences · Rippling
Rippling Software Engineer interview: intern assessment in 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…
Interview experiences · Rippling
Rippling Software Engineer interview: referral and familiar questions
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.
Interview experiences · Rivian
Rivian Backend Engineer interview with delayed feedback and missing follow-ups
I went through a frustrating, logistics-heavy interview process for a Software Engineer role. The difficulty felt average, and communication was often delayed or missing. The recruiter or HR screen covered basic engineering questions, production-line and equipment questions, and behavioral topics. The hiring manager meeting included more role-fit questions, after which communication slowed down.…
Interview experiences · Rivian
Rivian Senior Software Engineer Interview Experience — Sensors, Camera Failures, and a False-Positive Case Study
A recruiter contacted me, and I then interviewed with the hiring manager for an autonomous-vehicle systems role. The interview lasted one hour and began with brief introductions from both of us. The manager then gave me a set of driving capabilities and asked how I would choose the types and placement of sensors needed to support those capabilities. Next, I was asked about the external failure mo…
Interview experiences · Rivian
Rivian Software Engineer Interview Experience: OOP problem and delayed progression
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…
Interview experiences · Rivian
Rivian Software Engineer interview: nearly a month waiting for feedback
My recruiter and the early rounds went smoothly. The recruiter was responsive and welcomed my questions, so the first part of the process was easy to navigate. After the second interview, the tone shifted because of what happened afterward. I waited almost a month to hear back about the rejection. When I asked for feedback, I didn't receive any, and no one gave me useful pointers about what speci…
Interview experiences · Rivian
Rivian Software Engineer interview: project discussion and high-voltage experience
My screening was laid-back and centered mostly on my resume and projects. I talked through my previous work, and the first interview went into more detailed technical questions related to one of my projects. I was also asked about my high-voltage experience. There were some additional technical questions, but they weren’t overly complicated. It felt like they were checking whether my past work tr…