Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

41 stories

Likes earn the author +10 XP for the first 3 likes each day

RipplingAccount Executive
Reported Jul 2026

Rippling Account Executive Interview Experience: Structured mock call with managers

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…

HR Screen0
RipplingSoftware Engineer
Jun 2026

Designing a Google-News-Style System in a Phone Screen

A premium story — unlock it to read the full loop.

In progressTechnical ScreenPremium0
RipplingSoftware EngineerSenior+
Jun 2026

Deep HM Round on AI and Platform Projects, Then a Rejection

A premium story — unlock it to read the full loop.

RejectedOnsitePremium0
RipplingSoftware Engineer
Reported Jun 2026

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…

Technical Screen0
RipplingSoftware Engineer
May 2026

AI-Graded Phone Screen and a Zoom Screen-Share Meltdown

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
RipplingSoftware Engineer
May 2026

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…

Technical Screen0
RipplingSoftware EngineerSenior+
May 2026

Phone Screens Plus a Four-Part AI-Team Onsite Building a Live LLM Chatbot

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…

Onsite0
RipplingSoftware Engineer
Apr 2026

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…

RejectedOnsite0
RipplingSoftware Engineer
Apr 2026

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…

OfferOnsite0
RipplingSoftware Engineer
Mar 2026

A Fast-Food Payroll System Coded Live with GPT

Locked — open it to unlock the full story with XP.

In progressTechnical ScreenXP0
RipplingSoftware Engineer
Mar 2026

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…

Onsite0
RipplingSoftware Engineer
Mar 2026

How I Used AI-Enabled Coding in the Onsite

Locked — open it to unlock the full story with XP.

OnsiteXP0
RipplingSoftware EngineerSenior+
Mar 2026

An 11-Minute Late Start, a Chaotic Round, and a Recruiter Swap

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…

RejectedTechnical Screen0
RipplingSoftware Engineer
Feb 2026

Designing a Rule Engine for Corporate Card Spend Limits

Locked — open it to unlock the full story with XP.

Technical ScreenXP0
RipplingSoftware Engineer
Feb 2026

Rough System Design Round, Strong Manager Round, Then Rejected

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
RipplingSoftware Engineer
Jan 2026

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,…

Technical Screen0
RipplingSoftware Engineer
Jan 2026

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…

Technical Screen0
RipplingSoftware Engineer
Dec 2025

A Combative System Design Onsite Over Hotel Booking

Locked — open it to unlock the full story with XP.

OnsiteXP0
RipplingSoftware Engineer
Dec 2025

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…

OfferOnsite0
RipplingSoftware Engineer
Sep 2025

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…

In progressTechnical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP