Rippling Staff and SDE-2 Onsites: 21 Experiences (Part 8 of 12)

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

Rippling Staff and SDE-2 (L6) onsite loops, 2023 to 2026: delivery, music and rules coding, Google News design and manager rounds.

At a glance

Coverage: 21 reports, Nov 2023 to Aug 2026. Levels: SDE-2 to Staff. Places named: the U.S., India and the U.K.

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 (current): 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 21 loops; rows overlap, since a loop can name more than one topic.

Topic Reports Last seen
Delivery cost tracker and variants (1 variant or unlinked) 5 of 21 Jul 2026 (report date)
Google News-style aggregator design 5 of 21 Jul 2026 (report date)
Project deep dive or presentation 5 of 21 Jul 2026 (report date)
Expense rules engine 4 of 21 Jul 2026 (report date)
Song play analytics (music player) (1 variant or unlinked) 3 of 21 Oct 2025 (report date)
Task manager filter and sort (1 variant or unlinked) 1 of 21 Mar 2026
Key-value store and variants (1 variant or unlinked) 1 of 21 Mar 2025

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

Senior onsite loops (continued)

138: Five interviews including a simple API

Interview date: Nov 2023 · Role: Senior Software Engineer · Location: San Francisco · Result: No offer

  1. Five interviews: two LeetCode-style rounds, a deep dive on one project, a common system design question, and a small API to build plus short technical questions. No offer.

Staff and Senior Staff loops

139: Passed the loop, then the role disappeared

Report date: Aug 4, 2026 · Role: Senior/Staff SWE · Result: Passed loop; position removed; other team no fit

  1. Coding screen, system design, a second coding round and a project deep dive, all passed.
  2. Then the role was removed. A match with another team was tried, but it was not a fit.

140: Senior Staff offer after a long onsite

Interview date: May 2026 · Role: Senior Staff Software Engineer · Location: San Francisco · Result: Accepted offer

  1. Phone screen.
  2. System design review (one hour).
  3. Hiring manager.
  4. Onsite (five or more sessions): design, coding, two reviews of past projects, lunch with the team and a talk with a senior leader. They accepted an offer.

141: Staff in New York: design and manager rounds

Report date: Feb 16, 2026 · Role: Staff Software Engineer · Location: New York · Result: No offer

  1. Several rounds, mostly system design and manager conversations. No offer.

142: Not hard, but the clock was tight

Report date: Feb 4, 2026 · Role: Senior engineer L7/L8 · Result: Rejected

  1. Full loop: the questions were not hard, but the time was tight. Rejected.

143: L7 or L8: SOLID code in 45 minutes

Report date: Feb 2, 2026 · Role: Senior engineer L7/L8 · Location: Bangalore · Result: Rejected

  1. Onsite coding: clean, extendable object-oriented code (SOLID) in 45 minutes. They did not finish the extensions and were rejected.

144: Staff: screen, manager, onsite

Report date: Oct 31, 2025 · Role: Staff Software Engineer · Result: No offer

  1. Technical screen, hiring manager, then the onsite, where one interviewer did not seem to pay attention. No offer.

145: Google News homepage with a scraper

Report date: Jun 10, 2025 · Role: Staff/Senior SWE · Location: India

  1. System design.
  2. Manager/project.

SDE-2 onsite loops

146: London SDE2: positive loop, then a policy change

Report date: Jul 31, 2026 · Role: Software Engineer 2 / SDE2 · Location: London · Result: Positive onsite + team match; not hired after international-recruitment policy change

  1. Onsite: two coding rounds, one system design and a manager round; feedback came the next day and was positive.
  2. Extra manager round for team matching. They still did not get an offer because the company changed its policy on hiring from abroad.

147: Three coding rounds, Google News and a manager deep dive

Interview date: Apr–Jun 2026 · Report date: Jul 7, 2026 · Role: SDE 2 (L6) · Result: Not stated

  1. Coding 1: an object-oriented food delivery cost system. Methods included recordDelivery, payUpTo and addDelivery. The interviewer looked for tidy classes, sensible data structures and the best time and space.
  2. Coding 2: a rule evaluation engine. Each expense has an id, trip id, amount, vendor name and vendor type, and you write evaluate(rules, expenses). Sample rules: a ban on some categories, a total cap per trip and an entertainment cap. The point was a design that can grow.
  3. Coding 3: an article system with addArticle, upvoteArticle, downvoteArticle and printLastKFlippedArticles. The point was picking the right data structure for quick updates.
  4. System design: a Google News-style aggregator. First how articles get in: a crawler over many domains, scheduling, removing duplicates, parsing, storage, failures and updates to articles. Then what the feed must do: build it, rank it, tailor it to the reader, cache it, page it and scale it.
  5. Hiring manager: a deep dive on a past project's architecture and decisions, challenges, ownership and impact, and why they wanted to switch. AI was allowed in the coding rounds.

148: SDE II: two mediums that had to run

Interview date: May 2026 · Role: Software Development Engineer (SDE) II · Location: New York · Result: Declined offer

  1. Two medium questions in the LeetCode style, each with extra parts. The code had to run, with tests and edge cases. They got an offer and declined it.

149: Onsite feedback stuck for ten days

Report date: Apr 22, 2026 · Role: SDE 2 · Result: Second-round feedback delayed

  1. Onsite round 1: cleared.
  2. Onsite round 2: all tests passed, but the interviewer had not sent feedback after more than ten days.

150: SDE II offer: rule engine DSL and Google News

Interview date: Apr 2026 · Report date: Aug 25, 2026 · Role: Software Engineer (SDE II) · Result: Offer

  1. Recruiter.
  2. Technical screen: Done by hand, on a question others had reported, with both follow-ups.
  3. Onsite coding: A rule engine in OOP style, where they built a small DSL.
  4. Onsite system design.
  5. Onsite project presentation.

151: Five rounds, one coding round not finished

Report date: Mar 31, 2026 · Role: SDE 2 · Location: Bangalore · Result: Rejected

  1. Five rounds in all: coding, hiring manager, coding, coding, then HLD.
  2. They passed four of them. In the fourth round (coding) they could not get a working solution in time, and that round decided the rejection.

152: Bangalore SDE2 offer: delivery, rules, tasks, Google News

Interview date: Mar 2026 · Report date: Apr 14, 2026 · Role: SDE2 · Location: Bangalore · Result: Offer

  1. Recruiter screen: your projects, what you did yourself and how you measured success.
  2. Technical screen: the delivery cost tracker.
  3. Hiring manager: past projects and behavioral questions.
  4. Onsite 1: tasks that depend on other tasks; first print the list in a set format, then a follow-up on the dependency graph that they did not remember.
  5. Onsite 2: the expense rules engine other candidates also reported.
  6. Onsite 3: a Google News-style aggregator design. They got an offer.

153: SDE 2 offer: delivery, songs, temp email, movie booking

Report date: Oct 19, 2025 · Role: SDE 2 · Result: Offer

  1. Technical phone screen.
  2. Hiring manager.
  3. Onsite coding 1: Tracking song plays.
    • Song Play Analytics: Users have playlists; track which songs were played and how many times, most played songs overall, and each user's 3 most recent songs.
  4. Onsite system design.
    • Design a Durable Disposable Email Service: Design a temporary email service: users create an address that receives mail for 5 hours, then mail is purged. High load. Anonymity. Deep dive on encryption, random address generation, mail and attachment storage.
  5. Onsite coding 3.

154: Hard questions, slow replies

Interview date: Oct 2025 · Role: SDE-2 · Location: New York · Result: No offer

  1. Hard LeetCode-style questions, and slow replies between rounds. No offer.

155: SDE-2 selected: arrays, graphs and a long design

Report date: Jul 26, 2025 · Role: Software Engineer 2 · Result: Selected

  1. Coding screen: A three-part arrays and hash-map problem; two parts were required.
  2. Hiring manager.
  3. Final coding 1: A second three-part problem on arrays and maps.
  4. Final coding 2: A harder problem; the best solution used graphs.
  5. System design (~100 min): Schemas, indexes, SQL versus NoSQL, scale and observability.

156: SDE 2 offer: delivery, music, rules and Google News

Report date: Jun 16, 2025 · Role: Software Engineer (SDE 2) · Location: India · Result: Offer

  1. Technical screening.
    • Delivery Cost Tracker: Delivery cost tracking in 3 parts: add_driver, add_delivery(driver, start, end), get_total_cost. Pay_up_to_time, get_cost_to_be_paid. Analytics get_max_active_drivers_in_last_24_hours(currentTime). How they solved it: Part 3 discussed only.
  2. Onsite 1.
    • Song Play Analytics: Music analytics: add_song, play_song(user, song), print_analytics by unique users; print_recently_played(user) and (user, k) unique songs.
  3. Onsite 2 Hiring manager: HR had shared a list to prepare from.
  4. Onsite 3.
    • Corporate Card Expense Rules: Check expenses against company rules: a total cap, caps by seller type, and banned expense types, with rules modelled as data rather than code.
  5. Onsite 4.

157: SDE-2 loop with mixed coding results

Report date: May 16, 2025 · Role: SDE-2 · Result: Pending

  1. Phone screen (coding): they rated themselves hire to strong hire.
  2. Hiring manager round.
  3. Onsite coding 1: only the first part was finished.
  4. Onsite coding 2: every follow-up was finished.
  5. Onsite system design. No result yet when they wrote it up.

158: Song analytics, KV store and drivers

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

  1. They were asked about three things: a song analytics app in the style of Spotify, a store of keys and values, and a system for managing drivers and their delivery costs. No offer.

Common questions

What do these Rippling Staff loops show?

Entry 140 included two reviews of past projects and a senior-leader talk; in entry 87 the Staff candidate was offered Senior instead.

What do these Rippling SDE-2 onsites include?

Entries 156 and 152 include a Google News design; entry 153 a temporary email design; entries 156, 153 and 152 a hiring manager round.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling SDE-1 and SDE-2 Onsites: 14 Experiences (Part 9 of 12)
0 total reactions. Your reactions: none.

Comments

0

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