Rippling L7 and Senior Onsites: 18 Experiences (Part 7 of 12)

Shared by janebeingjane ·
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

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

  1. Coding 1 (60 min).
    • Travel expense calculation problem with a follow-up (OOP focus).
  2. EM round (60 min).
  3. Coding 2 (60 min).
  4. System design (60 min).
    • A news feed backend; follow-ups on surviving failures, the trade-off between consistency and availability, alerting and growth.
  5. 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

  1. The debrief after the loop was positive, but the first team said no.
  2. 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.
  3. 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

  1. Phone screen, then a deep dive on past work.
  2. 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

  1. 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.
  2. Coding: a key-value store with get, set and delete, then begin, commit and rollback, then nested transactions.
  3. 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

  1. 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

  1. 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).
  2. Coding: driver delivery costs.
  3. API coding: a Quora-style API, started on a real local server and tested through its endpoints.
  4. System design: Google News.

126: Spreadsheet, top-N ads and a Flask API

Report date: Dec 18, 2024 · Role: Senior Software Engineer · Result: Rejected

  1. Coding: an in-memory spreadsheet with raw and computed values.
  2. System design: a service that returns the top N ads. Ranking signals, time windows and scale were not shared.
  3. 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

  1. Recruiter.
  2. 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).
  3. Onsite.

128: Senior: REST APIs in 90 minutes and an analytics design

Report date: Oct 30, 2024 · Role: SSE · Result: Pending

  1. DSA, then hiring manager.
  2. DSA (60 minutes): two questions; the second was only explained.
  3. Machine coding, 90 minutes: several REST APIs with tidy code, then a talk about running them in production. The domain was not named.
  4. 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

  1. A full SDE 3 loop: two DSA rounds, one LLD, one HLD and a manager round.
  2. 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

  1. Screening HLD.
  2. Hiring manager.
  3. HLD.
  4. DSA.
  5. DSA.

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

  1. HR.
  2. Frontend technical.
  3. LC-style.
  4. Behavioral/project.
  5. 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

  1. R1 DSA.
    • Currency conversion.
  2. R2 Hiring manager: Past projects, end to end.
  3. R3 system design.
  4. R4 LLD API design.
    • LLD/API design round testing design patterns.
  5. 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

  1. Coding: a key-value store with transactions.
  2. Hiring manager conversation before the onsite, friendly.
  3. API coding: add and get questions in a questions and answers API, on a real local server.
  4. System design: Google News.
  5. 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

  1. System design: Google News, passed.
  2. 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

  1. 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?
  2. Tech screen design.
  3. Onsite system design.
  4. Onsite DSA: A key-value store, then transactions.
  5. Hiring manager: Culture questions of the "tell me about a time" kind, and mentoring.
  6. 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

  1. 3 DSA.
    • Easy/medium DSA problems on graph traversal and stacks (not described).
  2. Behavioral.
  3. 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

  1. Screen 1 (hire): an Excel-like sheet, close to LeetCode 631.
  2. Screen 2 (hire): past projects and how they led them.
  3. Onsite 1 (strong hire): a key-value store with transactions held in memory.
  4. Onsite 2 (lean hire): a news aggregator plus its feed.
  5. 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.
  6. 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

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling Staff and SDE-2 Onsites: 21 Experiences (Part 8 of 12)
0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.