Rippling Interview Questions — Page 1

Rippling·Software Engineer·Technical Phone Screen

Apr 2026

Rippling full-stack interview with a grid/matrix problem that looked like a BFS warmup but had enough edge cases to keep you honest. The jagged row thing specifically tripped me up more than I expected.

Given a jagged matrix where rows can have different lengths and cells are either 1 or empty, find all maximally connected regions of 1s using 4-directional adjacency. For each connected region, return the bounding box coordinates in a column-letter/row-number format (like A2 or B3).

“I went straight to BFS for connected components which was fine, but the bounding box part slowed me down.”

View Post

Rippling·Software Engineer·Onsite - System Design / Architecture

Apr 2026

Rippling system design round, one big question that sprawled into like six sub-topics. Felt like they wanted to see how far you could go before you started hand-waving.

Design a user behavior tracking system that collects client and server-side events at scale, enriches them with contextual data like user profile, device info, geo, A/B variant, and session details, then makes that enriched data available for analytics, ML, and product teams.
How would you handle schema evolution for the event stream without breaking downstream consumers?
Walk through your approach to exactly-once delivery and deduplication in the ingestion pipeline.
How would you handle late-arriving events in a streaming pipeline, especially when they affect time-windowed aggregations?
What's your strategy for enriching events with A/B variant and session data in real time versus in batch?
How do you enforce PII controls and privacy requirements across the event pipeline?

“This question is basically five questions wearing a trench coat.”

View Post

Rippling·Software Engineer·Onsite - Coding / Algorithms

Apr 2026

Virtual onsite at Rippling for a software engineer role. The AI coding round had the Camel Cards problem, which is a puzzle-style question that shows up in competitive programming contexts. Not a typical leetcode grind session.

Solve the Camel Cards problem: implement a card hand ranking system where hands are compared by type (five of a kind, full house, etc.) and then by card value order.

“This one is pulled straight from Advent of Code so if you've done that before you'd recognize it immediately.”

View Post

Rippling·Software Engineer·Recruiter / HR Screen

Apr 2026

HR screen for a software engineer role at Rippling. Pretty standard stuff, they just wanted to hear about past projects.

Walk me through some of the projects you've worked on.

“Standard opener.”

View Post

Rippling·Software Engineer·Technical Phone Screen

Apr 2026

Rippling SWE coding round, got a card game problem (think poker hand ranking variant) and couldn't get it fast enough to pass all the test cases. Skipped AI tooling entirely which probably didn't help.

Given a set of card hands, rank them according to a custom hand-strength ruleset similar to poker. Handle all edge cases correctly and efficiently enough to pass a large suite of test cases.

“My solution worked logically but timed out on a bunch of the test cases.”

View Post

Rippling·Software Engineer·Onsite - System Design / Architecture

Apr 2026

Rippling system design round, one question the whole time. The problem sounds deceptively simple but the O(1) constraint on the flip history is where it gets real.

Design a system that tracks per-article thumbs-up and thumbs-down votes, where users can change their vote at any time. When querying an article's state, you must also return the last three vote-flip actions for that article in order, with O(1) time per query.

“The vote tracking part I got pretty quickly, just a map from user to current vote state.”

View Post

Rippling·Software Engineer·Onsite - System Design / Architecture

Apr 2026

System design round at Rippling for a software engineer role. The whole thing was basically one big question about building a social news feed, and it went deeper than I expected, covering write paths, read paths, caching, media delivery, the works.

Design a personalized, time-ordered social news feed system that shows each user posts from people they follow. Cover post creation, follow/unfollow, feed fetching, and basic ranking, at a scale of hundreds of millions of users with some accounts having millions of followers.
Walk through the write path end-to-end when a user creates a post, including how the post gets distributed to followers' feeds.
Walk through the read path when a user loads their home feed, including how you achieve low latency around 200ms.
How would you handle media storage and delivery for posts that include images or videos?
How would you incorporate ranking signals into the feed rather than serving it in pure reverse chronological order?

“This is a big one and I felt the scope creep pretty fast.”

View Post

Rippling·Software Engineer·Onsite - System Design / Architecture

Apr 2026

Rippling system design round for a software engineer role, and they went straight for the jugular with a full billing system for a food delivery platform. No warmup, no easy stuff, just 'design this and make the money balance.'

Design and implement a billing system for a food delivery platform, covering order pricing, driver payments, restaurant payouts, promotions, and end-of-order settlement across all parties.
How would you test that all money flows balance to zero across the customer, restaurant, driver, and platform after settlement?
How would you extend the system to support new promotion types or entirely different fee schedules without breaking existing logic?

“This one is massive.”

View Post

Rippling·Software Engineer·Technical Phone Screen

Apr 2026

Rippling SWE interview with a payroll system design question. Pretty focused session, one meaty problem the whole time, and they cared a lot about the complexity targets they gave you upfront.

Design and implement a payroll system for food delivery drivers that supports registering a driver with an hourly wage, computing pay for a given shift using start and end epoch timestamps, and tracking a running total across all drivers. Target O(1) for registration and pay computation.

“The complexity constraints were printed right there in the problem and i still fumbled around for a bit before realizing there was nothing clever to do.”

View Post

Rippling·Software Engineer·Onsite - Multi Round

Apr 2026

Rippling onsite for a Software Engineer role, two parts back to back: a full system design and then a short coding problem. The system design was meaty enough that I felt the coding part was almost an afterthought, but they clearly wanted to see both in one session.

Design a news aggregator that ingests articles from thousands of publishers and serves ranked feeds to users, including a homepage feed, topic feeds, and optionally a personalized feed.
Walk through your API design for both the ingestion side and the user-facing feed reads.
How would you handle deduplication of near-identical stories that come from many different publishers covering the same event?
A breaking news event suddenly triggers 500 articles from different sources within 60 seconds. What part of the system saturates first and how does each component absorb the spike?
If you increase the feed cache TTL to reduce read costs, what breaks and how do you preserve freshness for breaking news specifically?
Implement an article voting tracker where users can upvote or downvote articles. A repeat vote on the same article is a no-op, but changing your vote counts as a new action. Also support fetching the last three votes a user has made.

“The first thing I did was ask about read vs write ratio and freshness requirements, which felt right in hindsight.”

View Post