Rippling L7 and Senior Onsites: 18 Experiences (Part 7 of 12)
- Company
- Rippling
- Reports
- 18 interview reports
- Level
- Full-time
- Stages
- Phone screen → Onsite
Rippling L7 and senior SWE onsites, 2024 to 2025: key-value store, spreadsheet, music player, Google News and Q&A API rounds.
At a glance
- Format: Entries 133 and 137 had a key-value store, entries 123 and 126 a spreadsheet, and entries 125, 133 and 137 a Q&A or Stack Overflow API.
- Asked: Delivery costs in 3 of 18 loops, Google News design in 8, the music player in 2, a travel expense task in 1, a key-value store in 6, a project deep dive in 7.
- Practise first: Delivery Cost Tracker, Song Play Analytics, Corporate Card Expense Rules and the news aggregator design.
Coverage: 18 reports, Jan 2024 to Jul 2025. Levels: Senior. 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: no-task screens, design screens, recruiter and manager rounds
- Part 6: senior loops
- Part 7 (current): 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 18 loops; rows overlap, since a loop can name more than one topic.
| Topic | Reports | Last seen |
|---|---|---|
| Google News-style aggregator design (1 variant or unlinked) | 8 of 18 | Jul 2025 (report date) |
| Project deep dive or presentation | 7 of 18 | Jul 2025 (report date) |
| Q&A or full-stack API coding (2 variant or unlinked) | 6 of 18 | Jul 2025 (report date) |
| Key-value store and variants (1 variant or unlinked) | 6 of 18 | Apr 2025 (report date) |
| Event tracking and analytics design (1 variant or unlinked) | 4 of 18 | Oct 2024 (report date) |
| Delivery cost tracker and variants | 3 of 18 | Jul 2025 (report date) |
| Spreadsheet (1 variant or unlinked) | 3 of 18 | Apr 2025 (report date) |
Rows overlap: a report can count in more than one row.
Senior onsite loops (continued)
120: Ten-year senior: five rounds, all positive
Report date: Jul 8, 2025 · Role: Senior Software Engineer
- Coding 1 (60 min).
- Travel expense calculation problem with a follow-up (OOP focus).
- EM round (60 min).
- Coding 2 (60 min).
- Delivery Cost Tracker: Driver delivery service with 2 follow-ups.
- System design (60 min).
- A news feed backend; follow-ups on surviving failures, the trade-off between consistency and availability, alerting and growth.
- Machine coding (90 min).
- Design and build a web API in 90 minutes, then questions on security, the choices made, parallel requests, tests and readiness for production.
121: L7 hire recommendation that stalled in matching
Interview date: Jun 2025 · Report date: Sep 29, 2025 · Role: SWE L7 · Result: Hire recommendation; team matching stalled
- The debrief after the loop was positive, but the first team said no.
- An extra hiring manager round and an extra coding round (for a follow-up they had forgotten) followed, and they were recommended for hire at L7.
- Then the hiring manager and the director left, and team matching stalled.
122: Seattle: food delivery costs in the onsite
Interview date: Jun 2025 · Role: Senior Software Engineer · Location: Seattle · Result: No offer
- Phone screen, then a deep dive on past work.
- Virtual onsite: two coding rounds plus a design round, with the full screen shared and AI allowed. One coding round asked them to log food deliveries and total their cost. No offer.
123: Spreadsheet, nested transactions and Google News at L7
Report date: Apr 10, 2025 · Role: L7, treated as senior · Result: Waitlisted
- Coding: an in-memory spreadsheet for a frontend team: integers of up to three digits, formulas with exactly two numbers added (like =2+8), an empty value to reset, and both raw and computed reads.
- Coding: a key-value store with get, set and delete, then begin, commit and rollback, then nested transactions.
- System design: Google News, sized at about a thousand publishers with up to a thousand articles each per day.
124: Senior SDE3 offer after six rounds
Interview date: Jan 2025 · Report date: Feb 28, 2025 · Role: Senior Software Engineer (SDE3) · Location: India · Result: Offer
- Six rounds: a screen, two hiring manager rounds, two DSA rounds and a system design. The questions were not restated. The result was an offer.
125: Music player, driver delivery, Quora API and Google News
Report date: Jan 10, 2025 · Role: Senior Software Engineer · Result: Passed
- Coding: song play analytics: add_song returns ids from 1, play_song records a play, print_analytics_summary sorts songs by unique listeners, and last_three_played_song_titles returns a user's three latest distinct songs (history A, B, A, C gives A, B, C).
- Coding: driver delivery costs.
- API coding: a Quora-style API, started on a real local server and tested through its endpoints.
- System design: Google News.
126: Spreadsheet, top-N ads and a Flask API
Report date: Dec 18, 2024 · Role: Senior Software Engineer · Result: Rejected
- Coding: an in-memory spreadsheet with raw and computed values.
- System design: a service that returns the top N ads. Ranking signals, time windows and scale were not shared.
- API coding: a Stack Overflow-like app in Flask (questions and answers API), then database schema, validation, auth, caching and scale.
127: Music player with a top-k limit
Report date: Dec 6, 2024 · Role: Senior Software Engineer · Result: No offer
- Recruiter.
- Technical screen.
- Song Play Analytics: Music player: add songs (ids from 1), record plays, print songs by distinct listeners, a user's last three songs, then limit summaries to k songs; beat O(N log N).
- Onsite.
128: Senior: REST APIs in 90 minutes and an analytics design
Report date: Oct 30, 2024 · Role: SSE · Result: Pending
- DSA, then hiring manager.
- DSA (60 minutes): two questions; the second was only explained.
- Machine coding, 90 minutes: several REST APIs with tidy code, then a talk about running them in production. The domain was not named.
- System design: a service shaped around Rippling, close to analytics, not named. The result was pending.
129: SDE 3 loop under NDA
Report date: Sep 25, 2024 · Role: SDE 3 · Location: India · Result: Rejected
- A full SDE 3 loop: two DSA rounds, one LLD, one HLD and a manager round.
- The candidate kept the questions private because of an NDA, and was rejected.
130: Senior offer: news, Amplitude-style events, KV, currency
Interview date: Aug 2024 · Report date: Aug 27, 2024 · Role: Senior Software Engineer · Location: Bengaluru · Result: Offer
- Screening HLD.
- Design a Personalized News Aggregation Platform: News aggregator like Google News: fetch from multiple publishers; custom feed by user interests and followed publishers.
- Hiring manager.
- HLD.
- Design a Product Analytics System: An Amplitude-style system that tracks user events and produces reports.
- DSA.
- Key-Value Store with Nested Transactions: Key-value cache driven by command strings (SET/GET/DELETE); follow-up: BEGIN... COMMIT/ROLLBACK transactions.
- DSA.
- Maximum Currency Conversion Along a Simple Path: Currency conversion given exchange-rate pairs (Google phone question style); follow-up: return the maximum achievable conversion rate rather than any path.
131: New York senior: frontend, LeetCode and design
Interview date: Aug 2024 · Report date: Oct 8, 2024 · Role: Senior Software Engineer · Location: New York · Result: No offer
- HR.
- Frontend technical.
- LC-style.
- Behavioral/project.
- Onsite: Coding, a frontend whiteboard and system design.
132: Currency, event analytics, API design, key-value store
Report date: Jul 3, 2024 · Role: Senior Software Engineer · Location: Bangalore · Result: Rejected
- R1 DSA.
- Currency conversion.
- R2 Hiring manager: Past projects, end to end.
- R3 system design.
- Design a Product Analytics System: Design an event analytics system like Amplitude.
- R4 LLD API design.
- LLD/API design round testing design patterns.
- R5: A key-value store.
- A key-value store (transactions not mentioned).
133: KV store, Quora API, Google News and currency
Report date: Jun 11, 2024 · Role: Senior Software Engineer · Result: Passed
- Coding: a key-value store with transactions.
- Hiring manager conversation before the onsite, friendly.
- API coding: add and get questions in a questions and answers API, on a real local server.
- System design: Google News.
- Coding: currency conversion. First a rate from source to target with one-way edges and no cycles; then several routes, return the best rate and its path.
134: Passed the design, then leveled at L6
Report date: Feb 16, 2024 · Role: Senior / L7 · Result: Rejected
- System design: Google News, passed.
- The recruiter then assessed them as SWE II (L6). A hiring manager project discussion followed (project deep dive), including the proudest or most complex project and what they would change.
135: L7 offer: news screen, events, KV, project talk
Interview date: Feb 2024 · Report date: May 1, 2024 · Role: Senior Software Engineer L7 · Location: Bengaluru · Result: Offer
- Recruiter screen (1 h): Why they were looking, their stack and experience, then how to build deployments and monitoring.
- How would you build a deployment pipeline, and how would you watch a live system?
- Tech screen design.
- Design a Personalized News Aggregation Platform: Build something like Google News that collects articles from many outlets.
- Onsite system design.
- Design a Product Analytics System: Amplitude-style event tracking: client SDK, servers, storage, queries and charts.
- Onsite DSA: A key-value store, then transactions.
- Key-Value Store with Nested Transactions: In-memory key-value store with save/delete, then commit/rollback transactions.
- Hiring manager: Culture questions of the "tell me about a time" kind, and mentoring.
- Project presentation.
136: Graph and stack problems, then a simple design
Interview date: Feb 2024 · Report date: Mar 7, 2024 · Role: Senior Software Engineer · Result: No offer
- 3 DSA.
- Easy/medium DSA problems on graph traversal and stacks (not described).
- Behavioral.
- Simple design.
137: Down-leveled after spreadsheet, KV, news and an API
Report date: Jan 3, 2024 · Role: Senior Software Engineer · Location: India · Result: Down-levelled to SDE-2 offer, declined
- Screen 1 (hire): an Excel-like sheet, close to LeetCode 631.
- Screen 2 (hire): past projects and how they led them.
- Onsite 1 (strong hire): a key-value store with transactions held in memory.
- Onsite 2 (lean hire): a news aggregator plus its feed.
- Onsite 3 (hire, 90 minutes): a Stack Overflow-style API built from data model to endpoints as working code in the first 45 minutes, then design questions in the second half.
- They were offered SDE-2 instead of Senior and declined.
Common questions
What did these Rippling senior onsites ask?
Key-value store: entries 133, 137 and 123. Spreadsheet: entries 123, 126 and 137. Q&A or Stack Overflow API: entries 125, 133 and 137. Google News: entries 133, 125, 123 and 137.
Keep practicing
- Walk me through a past project in depth: see reports 120, 130 and 131.
- Google News-style news aggregator: see reports 123, 125 and 130.
- Key-Value Store with Nested Transactions: see reports 123, 130 and 133.
- 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.