Rippling SDE-1 and SDE-2 Onsites: 14 Experiences (Part 9 of 12)

Shared by janebeingjane ·
Company
Rippling
Reports
14 interview reports
Level
Full-time
Stages
Phone screen → Onsite

Rippling SDE-1 and SDE-2 onsite loops, 2024 to 2026: key-value stores, graph problems, access design and project talks.

At a glance

Coverage: 14 reports, Feb 2024 to Apr 2026 plus 1 undated. Levels: SDE-1 to SDE-2. Places named: India and remote.

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: senior loops
  • Part 8: senior loops, Staff loops, SDE-2 loops
  • Part 9 (current): 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 14 loops; rows overlap, since a loop can name more than one topic.

Topic Reports Last seen
Key-value store and variants (2 variant or unlinked) 7 of 14 Jan 2025 (report date)
Song play analytics (music player) 5 of 14 Jan 2025 (report date)
Project deep dive or presentation 4 of 14 Jun 2025 (report date)
Spreadsheet (1 variant or unlinked) 4 of 14 Jan 2025 (report date)
Google News-style aggregator design 3 of 14 Jan 2025 (report date)
Delivery cost tracker and variants 1 of 14 —
Expense rules engine 1 of 14 —

Rows overlap: a report can count in more than one row.

SDE-2 onsite loops (continued)

159: L6: music, key-value store, spreadsheet, Google News

Report date: Jan 22, 2025 · Role: L6 · Result: Rejected

  1. R1 DSA.
    • Song Play Analytics: A music player: addSong(title) with ids counting up from 1, playSong(songId, userId), a printout of most played songs by distinct users, then getLastThreeSongs(userId) for distinct songs; one more follow-up existed.
  2. R2 Hiring manager: General behavioral questions.
  3. R3 DSA onsite.
  4. R4 DSA onsite: An Excel-style sheet.
    • In-Memory Spreadsheet Values: A spreadsheet: set(cell, value) where the value is a number or a formula such as =9+10 or =-1+-10+2. Reset(cell). Show each cell's stored text and its calculated result. Follow-up: references like =A1+10.
  5. R5 system design onsite.

160: Song analytics, then rounds at the office

Interview date: Jan 2025 · Role: Software Engineer II · Location: Bengaluru · Result: No offer

  1. DSA (60 minutes): a service like Spotify: create songs, log plays, show analytics and each user's last three songs.
  2. Manager (45 minutes).
  3. At the office: two more DSA rounds and a system design. No offer.

161: SDE-2 offer: music, transactions, spreadsheet, hotels

Report date: Oct 4, 2024 · Role: SDE-2 · Location: Bangalore · Result: Offer

  1. Screening: Part 1 done, part 2 nearly.
    • Song Play Analytics: A music library: rank songs by how many different users played them; then each user's three latest songs.
  2. Hiring manager.
  3. Coding.
  4. Coding: An Excel-style sheet.
    • In-Memory Spreadsheet Values: A spreadsheet: set(cell, value or an expression using + and -), show each cell's stored text and its calculated result; extension: references like =A1+5 or =A1. How they solved it: Cell map; lazy recursive evaluation.
  5. System design.
    • A hotel booking aggregator where the same hotels also sell through other aggregators, which the design must handle.
  6. Hiring manager (second position): A project deep dive.

162: SDE2: two coding rounds and a design

Report date: Aug 14, 2024 · Role: SDE2 · Location: India · Result: Rejected

  1. Two coding rounds and a system design. One coding round came back as no and the other as weak yes; design was a yes. Rejected.

163: Settle balances, music stars, transactions, scraper design

Report date: Aug 5, 2024 · Role: SDE 2 · Location: Bangalore · Result: Rejected

  1. Phone screen (HackerRank CodePair): It went well.
    • Minimum Account Settlements: From a list of transactions (from, to, amount), work out who owes whom and how much, with no need for the fewest payments; the follow-up asks for the fewest transfers. How they solved it: Greedy for follow-up.
  2. Hiring manager: Projects, why they wanted to switch, conflict, prioritizing work and estimating a sprint.
  3. DSA 1: Weak yes.
    • Song Play Analytics: Music analytics: addSong(id, title), playSong(songId, userId), printAnalytics by plays; follow-up: users can star and unstar songs, and return the last N starred songs a user played.
  4. DSA 2: A rude interviewer; no.
  5. HLD: A Google News scraper with its schema; yes.
    • Design a Personalized News Aggregation Platform: Google News-style service scraping thousands of publishers (each exposes latest 25 items); write schemas (publisher, user, category and publisher subscriptions, articles), dedup scraped articles, users subscribe to categories or publishers.

164: SWE II: key-value store with commit and rollback

Report date: Jun 18, 2024 · Role: Software Engineer II · Result: No offer

  1. Technical assessment.
  2. Hiring manager.
  3. Planned onsite: Planned: LLD coding, graph algorithms and system design.

165: SDE-2 offer: KV concurrency, spreadsheet, inversions

Interview date: Jun 2024 · Report date: Jun 8, 2024 · Role: SDE-2 · Location: Bangalore · Result: Offer

  1. R1 phone screen.
    • K-V store with getByKey, updateValueByKey, removeKey; follow-up: concurrency when two threads update the same key (reproduce then fix).
  2. R2.
    • In-Memory Spreadsheet Values: Spreadsheet like Google Sheets: set A1=1, sums like "1+2"; follow-up: multiplication and cell dependencies defined in any order (for example E2=A2+B2, A2=D1+E2). How they solved it: Topological sort and observer pattern.
  3. R3: Two questions.
    • Crossed User Pairs on One Date: A log that only grows, with (user_id, date, timestamp) rows. For one date, count pairs where the earlier timestamp belongs to the larger user_id (an inversion count).
    • K-th Amount a Payout Machine Can Give: A counting question close to LeetCode's k-th smallest amount made from single coin types. How they solved it: Approach after hint.
  4. R4 design.
    • Design a Following News Feed Service: Instagram-style photo uploads: database, APIs, caching, push versus pull fan-out, very popular accounts, growth, single points of failure, and alerts.
  5. R5 Hiring manager with director.

166: SDE 2 offer: graph, key-value store, sheet, design

Report date: Apr 25, 2024 · Role: SDE 2 (L6) · Location: Bengaluru · Result: Offer

  1. Problem solving: a graph question (not described).
  2. Hiring manager: projects from the résumé.
  3. Two coding rounds: an in-memory key-value store and an Excel-like sheet; no transactions or formula rules were mentioned.
  4. Two system design rounds, of the Instagram, BookMyShow or Uber kind; which one came up is not clear. They got an SDE 2 offer.

167: SWE II offer: nested transactions in the screen

Report date: Feb 28, 2024 · Role: Software Engineer II · Result: Accepted offer

  1. Recruiter call.
  2. Coding screen: a store of keys and values first; next, commit and rollback; last, nested transactions.
  3. Hiring manager.
  4. Final round: two coding sessions and a system design. They accepted an offer.

168: SDE-2 offer: delivery, music, rules platform, news

Role: SDE-2 / Software Engineer · Location: Remote · Result: Offer

  1. Technical screen: delivery cost tracking with add_driver, add_delivery(driver, start, end) and get_total_cost; the interviewer pushed on millions of deliveries and very frequent total queries, so the total is kept up to date on each write.
  2. Coding with product design: music analytics with add_song, play_song(user, song) and print_analytics, where details such as counting unique listeners came in one by one.
  3. Hiring manager: their résumé treated like a design doc: database picks, scaling and incidents in production.
  4. Rules design and coding: a platform that checks expense claims for hotels, travel, meals and equipment against company rules (caps, manager sign-off for travel, blocked vendors, limits per category), built so rules can change.
  5. HLD: Google News at large scale: pull articles in and clean them, order and tailor them per reader, and serve feeds fast. They got a verbal offer.

SDE-1 loops

169: SDE-1: topological sort, then shortest paths

Interview date: Apr 2026 · Report date: May 16, 2026 · Role: SDE-1 · Result: Role put on hold before HM round

  1. HR call (15 min): They talked about their background and when they could start.
  2. Coding (60 min).
  3. LLD round (60 min).
    • Graph problem solved with DFS first; follow-ups turned it into shortest paths (Dijkstra, then Bellman-Ford).
  4. Hiring manager: It was rescheduled again and again, and the role was put on hold.

170: SDE1: access and permissions design

Report date: Apr 14, 2026 · Role: SDE1 · Result: No offer

  1. OA on HackerRank (60 minutes): a medium-hard graph or backtracking problem and a medium DP or greedy one; every test passed.
  2. HR (15 minutes).
  3. DSA (over an hour): a string question of medium difficulty, with follow-ups.
  4. Design (60 minutes): access rights for employees and products: entities, APIs, roles that grant permissions, growth, parallel updates and caching. No offer.

171: SDE1: full OA score, then DSA and design

Report date: Mar 28, 2026 · Role: SDE1

  1. OA (60 minutes on HackerRank): full score.
  2. HR call.
  3. DSA round.
  4. HLD and LLD round on a system they did not name.

172: SDE-1 offer with an owned-project presentation

Report date: Jun 10, 2025 · Role: SDE-1 · Location: Bangalore · Result: Selected

  1. OA (60 min): Two DSA problems.
  2. R1 DSA (60 min).
  3. R2 LLD (60 min): A problem drawn from what Rippling builds.
  4. R3 Hiring manager (60 min): They presented a project they owned, using slides, and answered behavioral and mentoring questions.

Common questions

What do Rippling SDE-1 loops here look like?

Entries 172, 170 and 169 include an LLD or design round, and entry 170 an HR call.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling SWE Loops and History: 23 Experiences (Part 10 of 12)
0 total reactions. Your reactions: none.

Comments

0

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