real interview stories, told over a cup of tea ♡
Rippling 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
33 results
- Delivery Cost Calculation with an AI AssistantRippling · Software Engineer · Technical Screen · Oct 2026In progress
I did the Rippling technical screen last week. It was online coding with an AI assistant. The problem was the Delivery Cost calculation that has shown up here before (the calculate_compensation version). Summary of the problem: a food delivery platform pays drivers per delivery, and the cost is duration × that driver's hourly rate. You implement a dashboard system whose core is a single number, t…
- Phone Screen Where You Choose Whether to Use AIRippling · Software Engineer · Senior+ · Technical Screen · Oct 2026
This was the first technical interview after HR screen. The interviewer asked me do I want to use AI or not, and said if I picked AI I would get a harder question. I chose not to use AI and this was the question I needed to solve in 45 minutes: Design a delivery-driver payment system add_driver(driver_id, usd_hourly_rate) — register a driver with an hourly rate. record_delivery(driver_id, start_t…
- Pluggable Logger Phone Screen, Rejected After Using CursorRippling · Software Engineer · Technical Screen · Oct 2026Rejected
Ran into a new question. / Your task is to build a simple logging tool for an application. The core requirement is that the Logger should support several different log handlers, and it should be easy to add new log handlers in the future without modifying the core Logger class. Implement these first: Filter handler: before printing, remove all occurrences of a (configurable) string from the log m…
- An Onsite Where the Coding Round Expected You to Use AIRippling · Backend Engineer · Senior+ · Onsite · Sep 2026Rejected
Interviewed for a Senior backend role in July. Round 1 — Coding (60 min), AI use explicitly allowed The interviewer (Data Cloud team) opened by saying directly: "The environment has an AI assistant set up, use it the way you normally would at work, just don't let it make every decision for you." Problem: task scheduler. You're given a batch of tasks (description / due date / priority / completed…
- Article Vote TrackerRippling · Software Engineer · Technical Screen · Sep 2026
Got the Article Vote Tracker question. Part 1 involved adding articles, recording up/down votes, detecting vote flips, and returning the last 3 unique flipped articles. The follow-up asked how to handle a very large flip history. The key optimization is to maintain only the last 3 unique flipped article IDs per user instead of storing the complete history. I completed Part 1 but did not proceed t…
- Delivery Billing and Rounding DecisionsRippling · Software Engineer · Technical Screen · Sep 2026
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…
- Explaining an Expense Rules Engine Before Using AIRippling · Software Engineer · Technical Screen · Sep 2026
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…
- One-Hour AI-Assisted Phone Screen on Camel CardsRippling · Software Engineer · Technical Screen · Sep 2026In progress
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…
- Task Scheduler Phone Screen, AI Optional, RejectedRippling · Software Engineer · Technical Screen · Sep 2026Rejected
Sharing my Rippling phone screen. Phone screen, first round (coding): The problem was something like a task scheduler, but the requirements were very complicated and there were a huge number of conditions. It's not hard, but the details explode. Roughly: Tasks have dependencies, and when outputting I had to output the dependency first and then the task itself. Tasks have various attribute require…
- A News Aggregator Design Followed by a Fast RejectionRippling · Software Engineer · Technical Screen · Aug 2026Rejected
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…
- AI-Assisted Logger Handler Screen on HackerRankRippling · Software Engineer · Technical Screen · Aug 2026
I used my own AI + IDE. The problem was on HackerRank and I shared my screen the whole time. I got the logger problem. Part 1 A logger has handlers. Each handler is independent. Handler types: Remove all occurrences of a configured string, then print. Truncate to N characters, then print. Uppercase the whole message, then print. Store the message in an internal array without printing. Discuss the…
- An AI Coding Edge Case with Filtered Parent TasksRippling · Software Engineer · Technical Screen · Aug 2026Rejected
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.
- 30-Minute Recruiter Chat, Rejected the Next DayRippling · Software Engineer · Senior+ · HR Screen · Jul 2026Rejected
I got a reach-out email from their recruiter and we scheduled a 30-minute quick chat. The HR person was 5 minutes late, but it was no big deal, I've seen this a lot. After she joined she said she wouldn't turn her camera on, and told me I didn't have to either. Then we got started. Intro and work experience She first asked me to introduce myself, and I went over my work history. Then she asked me…
- Onsite AI Coding Round with Live PromptingRippling · Software Engineer · Onsite · Jul 2026
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…
- Rippling Account Executive Interview Experience: Structured mock call with managersRippling · Account Executive · HR Screen · Jul 2026
I applied and received a quick, positive response that let me choose a meeting time. The process began with a recruiter screen covering why I wanted sales, why Rippling, what the company does, and how my prior experience fit the role. I then spoke with hiring managers and reached a role-play mock-call stage. That portion was more structured and role-specific, and I did the mock call with managers…
- Rippling Account Executive interview: advanced process followed by recruiter silenceRippling · Account Executive · Other · Jul 2026No response
My process began normally and I made it through several rounds. Near the end, it became clear they were not moving forward. The recruiter said they would contact me that day or the next, then I heard nothing. After multiple interviews and getting fairly far, the lack of follow-through bothered me. I can understand that an early process may be slow or ambiguous, but this silence came after I was a…
- 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…
- Rippling Software Engineer interview experience: coding, system design, and AI useRippling · Software Engineer · Technical Screen · Jun 2026
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…
- An Extensible Expense Rule EngineRippling · Software Engineer · Technical Screen · May 2026
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…
- Phone Screens Plus a Four-Part AI-Team Onsite Building a Live LLM ChatbotRippling · Software Engineer · Senior+ · Onsite · May 2026
I interviewed with Rippling's new AI department, which has 3 teams and an already-launched product. Their main product is an internal chat agent system that can integrate with hundreds of integrations on top of employee data to answer all kinds of questions. Recruiter - 30 minutes. Talked about which project of mine stood out to them, my involvement in it, and whether I had led any projects of my…
- Phone Screen and Onsite Reject, Struggling With the AI-Coding RoundsRippling · Software Engineer · Onsite · Apr 2026Rejected
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…
- Three Onsite Rounds and the Fastest Feedback I've SeenRippling · Software Engineer · Onsite · Apr 2026Offer
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…
- An 11-Minute Late Start, a Chaotic Round, and a Recruiter SwapRippling · Software Engineer · Senior+ · Technical Screen · Mar 2026Rejected
The interviewer was 11 minutes late. I was actually about to just leave the call and email the recruiter to say they were a no-show, but they showed up at the very last moment. After joining, there was no intro or behavioral portion at all — they went straight into technical. Right off the bat they asked whether I wanted an AI or non-AI technical round, and I picked non-AI. Then the interviewer j…
- An AI-Assisted Coding Round on Poker Hand ComparisonsRippling · Software Engineer · Onsite · Mar 2026
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…
- A Poker OOD Question I Didn't Practice ForRippling · Software Engineer · Technical Screen · Jan 2026
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…
- Extensible Five-Card Poker EvaluationRippling · Software Engineer · Technical Screen · Jan 2026
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,…
