Rippling Design and Manager Rounds: 28 Experiences (Part 5 of 12)
- Company
- Rippling
- Reports
- 28 interview reports
- Level
- Full-time
- Stages
- Phone screen
Rippling system design phone screens and recruiter or manager rounds, 2024 to 2026: Google News, user event tracking, hotel booking and project talks.
At a glance
- Design screens: The news aggregator in 8 of 16 design screens, user event tracking in 4, hotel booking once.
- Staff and above: Staff candidates in entries 89, 82 and 83 had a design screen, and in entry 87 a design round with the hiring manager.
- Recruiter and manager rounds: Entry 96 covered introductions, a recent challenge and AI use; entry 99 asked about one end-to-end project.
Coverage: 28 reports, Jan 2024 to Oct 2026. Levels: Senior to Staff, plus reports with no level given. Places named: the U.S. and India.
Terms: OA = online assessment · HM = hiring manager · LLD / HLD = low-level (class) / high-level (system) design · VO = virtual onsite · DSA = data structures and algorithms · CodePair = HackerRank's shared coding pad.
In this series
- Part 1: overview, question tables by role, what to practise
- Part 2: delivery screens
- Part 3: delivery screens, rules and task screens
- Part 4: practical screens, music and key-value screens, no-task screens
- Part 5 (current): no-task screens, design screens, recruiter and manager rounds
- Part 6: senior loops
- Part 7: senior loops
- Part 8: senior loops, Staff loops, SDE-2 loops
- Part 9: SDE-2 loops, SDE-1 loops
- Part 10: no-level loops, History
- Part 11: History
- Part 12: frontend and mobile, data, History
What came up
Counts over the 16 design screens:
| Topic | Reports | Last seen |
|---|---|---|
| Google News-style aggregator design | 8 of 16 | Jun 2026 |
| Event tracking and analytics design (1 variant or unlinked) | 4 of 16 | Jun 2026 (report date) |
| Hotel booking design (1 variant or unlinked) | 1 of 16 | Jun 2026 (report date) |
Rows overlap: a report can count in more than one row.
Screens where no task was shared (continued)
77: Feedback that seemed to describe another session
Interview date: Aug 2025 · Report date: Aug 27, 2025 · Role: Senior Software Engineer · Result: No offer
- Coding: a problem in several parts. The feedback they got seemed to describe someone else's session.
78: A long OOD prompt, then an offer
Interview date: Aug 2025 · Role: Sr. SDE · Location: San Francisco · Result: Accepted offer
- Object-oriented build: the prompt was long, and one more part was added on top. They accepted an offer.
79: Maps and data structures on video
Interview date: Aug 2024 · Role: Senior Software Engineer · Location: United States · Result: No offer
- Recruiter call.
- Video coding (60 minutes): problems built on hash maps and similar structures; the task was not shared. Their tests passed, but there was no offer.
System design screens
80: A user-behavior tracking design screen
Interview date: Apr–Jun 2026 · Report date: Jun 28, 2026 · Role: Software Engineer · Result: Not known at report time
- Phone screen, system design: a user behavior tracking system (Design a Product Analytics System). They felt it went fine and had no news four days later.
81: Google News design where the candidate had to steer
Interview date: Jun 2026 · Report date: Jun 28, 2026 · Role: Software Engineer · Result: Passed
- System design phone screen: a news aggregator like Google News. The interviewer first had them look at the Google News product, then design it.
- The scope was wide and the interviewer did not steer, so the candidate had to ask, for example about crawling.
- Follow-ups: they proposed a coordinator, so what if that single machine fails (run several and round-robin; then how do they find each other, maybe ZooKeeper). How to spot hot topics. Why a relational or document database (either works if you explain it).
- Feedback: a big open question; one tip was to write news to the database first and build embeddings later. Passed.
82: A Staff design screen on hotel booking
Interview date: Apr–Jun 2026 · Report date: Jun 24, 2026 · Role: Staff Engineer · Result: Rejected the next day
- System design phone screen: a hotel booking system like Expedia, with search, ingesting many hotels and making a reservation.
- Three areas they expected to be probed: does search hit the database or a search index such as Elasticsearch, and why, and what is the search input (ask how far ahead dates can go); is the room entity a physical room or a room type; is booking synchronous or asynchronous.
- They felt fine but missed what the interviewer wanted.
83: A Staff design screen on user events
Interview date: Apr–Jun 2026 · Report date: Jun 2, 2026 · Role: Staff Engineer · Result: Passed
- System design tech screen: a user events tracking system (Design a Product Analytics System), matching what others had reported.
- They had built something similar at work and answered from that. Interview in the afternoon, pass email the next morning.
84: News design focused on freshness and scale
Interview date: Apr–May 2026 · Report date: May 30, 2026 · Role: Software Engineer · Result: Rejected
- System design phone screen: a news aggregator like Google News.
- The interviewer focused on building a personalized feed, scaling to users worldwide and keeping news fresh. They felt it went well but were rejected.
85: Staff: design an event system
Report date: May 22, 2026 · Role: Staff Software Engineer · Location: Bengaluru · Result: No offer
- Design.
- Design an event system (unspecified).
86: Staff: a system design phone screen
Report date: May 5, 2026 · Role: Staff · Result: Failed
- Phone screen: system design. The prompt was not shared, and they did not pass.
87: Staff design with the manager, then a downlevel
Report date: Mar 24, 2026 · Role: Staff (recommended Senior) · Result: Withdrew after downlevel
- System design with the hiring manager (one hour).
- They were then told to come back as Senior rather than Staff; the onsite on offer had two coding rounds plus a behavioral one. They withdrew.
88: Metrics monitoring with enrichment
Report date: Feb 26, 2026 · Role: Senior Software Engineer · Result: Rejected
- System design: a metrics monitoring system that also enriches the data. No further requirements were shared.
89: Staff: a personalized news aggregator first
Report date: Oct 14, 2025 · Role: Staff Engineer · Location: Bangalore · Result: Presumed rejected
- R1 HLD.
- Design a Personalized News Aggregation Platform: A news app where each person sees a feed shaped by their interests and the publishers they like. Scale given: about 5M writes a day and 100k reads a second. How they solved it: Polling publishers, RDS storage, Redis caching of top feeds, on-the-fly or pre-generated feeds.
90: Google News with a personal homepage
Report date: Jun 10, 2025 · Role: SSE
- System design.
- Design a Personalized News Aggregation Platform: Google News: a personal home page and crawling of many sites.
91: Google News, nothing else shared
Report date: Apr 7, 2025 · Role: Senior Software Engineer · Result: Not stated
- System design: Google News. No other round details were shared.
92: Senior Staff: news feed processing
Interview date: Jan 2025 · Role: Sr Staff Software Engineer · Location: San Francisco · Result: No offer
- System design (1 h).
- Design a Personalized News Aggregation Platform: Design processing for news feeds.
93: Event ingestion with fast today, slower history
Report date: Nov 23, 2024 · Role: Senior Software Engineer · Result: Rejected
- System design: ingest events such as add-to-cart and purchase (product analytics). Today's unique-user count must be fast; a two-month query may be slower. Every component, down to the load balancer, needed explaining.
94: Google News with no extra spec
Interview date: Apr 2024 · Role: Senior Software Engineer · Location: San Francisco · Result: No offer
- Design interview: Google News, with no further requirements at all.
95: A Google News phone screen
Report date: Apr 3, 2024 · Role: Senior Software Engineer · Result: Passed
- Phone screen, system design: Google News. Passed.
Recruiter and hiring manager rounds
96: A 30-minute recruiter call with the camera off
Interview date: Jul–Sep 2026 · Report date: Oct 2, 2026 · Role: Senior Software Engineer · Result: Rejected the next day
- Recruiter screen, 30 minutes, after an email from the recruiter. The recruiter joined five minutes late with the camera off.
- They were asked to introduce themselves and give their work history, and about their current team and role. Then came a recent challenge at work and how they solved it and how they use AI day to day. The last question was what they want at Rippling (they said bigger scope and more work built from zero).
- They asked about the pay range and the company. A rejection came the next day.
97: A recruiter who read from a list
Interview date: Jul–Sep 2026 · Report date: Sep 13, 2026 · Role: Software Engineer · Result: Rejected
- Recruiter call. An AI note-taker was running while the recruiter went through a list of prepared questions, which the résumé had already answered.
- The recruiter said the résumé would go to a manager screen. The candidate's follow-up email was never answered, and they were rejected. They shared no questions.
98: L7 offer: a manager walk-through of one project
Report date: Jul 10, 2026 · Role: Senior Software Engineer L7 · Location: Bangalore · Result: Offer
- Hiring manager: One project end to end: design, build choices and what was delegated.
99: A Senior Staff manager round on one platform project
Interview date: Apr–Jun 2026 · Report date: Jun 26, 2026 · Role: Senior Staff Engineer · Stage: Hiring manager · Result: Rejected
- Hiring manager round on recent projects, AI practice, influence across teams and motivation. The project deep dive dug into how it started, who worked on it, blockers, how it was judged, impact numbers and the hard technical parts.
- The questions began with their background, current role and fit, what they own now and its impact, and how they split their time. They were asked whether code written by a coding agent still counts as their own work, and whether in the last six months they had spread an AI tool or practice to a wider group (how you use AI). Then they picked an end-to-end project they led (project deep dive) and explained why it mattered and how a local need became a platform. The biggest pushback came next: how data, prototypes or architecture won people over. They described their scope, team size and key decisions, and how they designed onboarding, interfaces and data sync to avoid duplicate work and unclear ownership. They also covered how they used AI in the project, the final impact and how they judge success, and the hardest technical part.
- About 15 minutes went to the manager's product, so prepare deep questions of your own.
100: Staff process with twelve interviews
Interview date: Dec 2024 · Role: Staff Software Engineer · Location: United States · Result: No offer
- The plan was about twelve interviews, and the level was cut to Senior from Staff. No offer.
101: Question withheld after a two-week process
Report date: Jul 16, 2024 · Role: Senior Software Engineer · Result: No offer
- A two-week process run by the recruiter. The candidate kept the question private. No offer.
102: Recruiter and manager, then why Rippling
Report date: Jun 4, 2024 · Role: Senior Software Engineer · Result: No offer
- Recruiter (30 min).
- Hiring manager (30 min).
103: New York senior: one project question
Interview date: Apr 2024 · Report date: Jun 24, 2024 · Role: Senior Software Engineer · Location: New York · Result: No offer
- Phone conversation: Behavioral questions.
104: What have you built from scratch?
Interview date: Jan 2024 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer
- Screening: What they had built from scratch, where they lived, and why they were leaving.
Patterns across the reports
- Open scope. Entry 81 says the interviewer did not steer and the candidate had to ask; entry 84 focused on personalization, scale and freshness.
Common questions
What is the Rippling system design phone screen?
Google News in 8 of 16 design screens: crawl publishers, store articles and serve a personal feed (81, 84, 89, 90 and 91).
What does the Rippling recruiter call ask?
Entry 96 covered their work history, current team, a recent challenge, AI use and what they want at Rippling; entry 102 asked why they want to work at Rippling.
Keep practicing
- Google News-style news aggregator: see reports 81, 84 and 89.
- Walk me through a past project in depth: see reports 98, 99 and 103.
- User event tracking and analytics (Amplitude-style): see reports 80, 83 and 93.
- Rippling question banks, sign-in needed: coding, behavioral, system design and project coding.
- The Rippling interview guide, Rippling hiring insights and the Experience feed.
- More roundups: intern, new grad, no level and AI coding rounds.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.