Rippling SDE-1 and SDE-2 Onsites: 14 Experiences (Part 9 of 12)
- 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
- Format: Entries 169, 170 and 165 include an LLD or design round, and entry 165 a manager round with a director.
- Asked: Delivery costs in 1 of 14 loops, Google News design in 3, the music player in 5, a travel expense task in 1, a key-value store in 7, a project deep dive in 4.
- Practise first: Delivery Cost Tracker, Song Play Analytics, Corporate Card Expense Rules and the news aggregator design.
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
- 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.
- R2 Hiring manager: General behavioral questions.
- R3 DSA onsite.
- Key-Value Store with Nested Transactions: A store of keys and values with get, set and delete. Then transactions you open, commit and undo (one level first). Then nested transactions.
- 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.
- R5 system design onsite.
- Design a Personalized News Aggregation Platform: Design Google News.
160: Song analytics, then rounds at the office
Interview date: Jan 2025 · Role: Software Engineer II · Location: Bengaluru · Result: No offer
- DSA (60 minutes): a service like Spotify: create songs, log plays, show analytics and each user's last three songs.
- Manager (45 minutes).
- 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
- 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.
- Hiring manager.
- Coding.
- Key-Value Store with Nested Transactions: A key-value store, then transactions on top of it.
- 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.
- System design.
- A hotel booking aggregator where the same hotels also sell through other aggregators, which the design must handle.
- 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
- 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
- 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.
- Hiring manager: Projects, why they wanted to switch, conflict, prioritizing work and estimating a sprint.
- 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.
- DSA 2: A rude interviewer; no.
- Key-Value Store with Nested Transactions: In-memory cache add/get/delete for string keys; follow-up BEGIN/COMMIT/ROLLBACK transactions (delete edge cases probed).
- 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
- Technical assessment.
- Key-Value Store with Nested Transactions: In-memory key-value store get/set, extended with commit/rollback.
- Hiring manager.
- 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
- R1 phone screen.
- K-V store with getByKey, updateValueByKey, removeKey; follow-up: concurrency when two threads update the same key (reproduce then fix).
- 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.
- 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.
- 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.
- 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
- Problem solving: a graph question (not described).
- Hiring manager: projects from the résumé.
- Two coding rounds: an in-memory key-value store and an Excel-like sheet; no transactions or formula rules were mentioned.
- 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
- Recruiter call.
- Coding screen: a store of keys and values first; next, commit and rollback; last, nested transactions.
- Hiring manager.
- 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
- 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.
- 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.
- Hiring manager: their résumé treated like a design doc: database picks, scaling and incidents in production.
- 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.
- 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
- HR call (15 min): They talked about their background and when they could start.
- Coding (60 min).
- Finish Order and Total Time for Dependent Tasks: A graph task that came down to topological sort.
- LLD round (60 min).
- Graph problem solved with DFS first; follow-ups turned it into shortest paths (Dijkstra, then Bellman-Ford).
- 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
- OA on HackerRank (60 minutes): a medium-hard graph or backtracking problem and a medium DP or greedy one; every test passed.
- HR (15 minutes).
- DSA (over an hour): a string question of medium difficulty, with follow-ups.
- 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
- OA (60 minutes on HackerRank): full score.
- HR call.
- DSA round.
- 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
- OA (60 min): Two DSA problems.
- R1 DSA (60 min).
- R2 LLD (60 min): A problem drawn from what Rippling builds.
- 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
- Song Play Analytics: see reports 159, 160 and 161.
- Key-Value Store with Nested Transactions: see reports 159, 161 and 163.
- Walk me through a past project in depth: see reports 161, 165 and 168.
- 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.