Rippling SWE Loops and History: 23 Experiences (Part 10 of 12)

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

The last Rippling onsite loop with no level given, then software engineer reports from Jan 2022 to Oct 2023: key-value stores and spreadsheets.

At a glance

  • Current loops: 2 more current loops close the list.
  • History: 21 reports from before November 2023 follow: the key-value store in 4, the spreadsheet in 1 and the alien dictionary in 1 of them.

Coverage: 2 current loops and 21 older reports. History is not counted in the overview tables; it continues in Part 11.

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: SDE-2 loops, SDE-1 loops
  • Part 10 (current): no-level loops, History
  • Part 11: History
  • Part 12: frontend and mobile, data, History

Loops with no level given (continued)

173: Backend onsite with a full-stack admin feature

Interview date: Jul–Sep 2026 · Report date: Oct 23, 2026 · Role: Backend SDE · Result: Rejected

  1. Behavioral round: a project deep dive using slides they had made beforehand. The questions that followed were practical.
  2. System design: Google News, drawn on HackerRank's built-in whiteboard. The candidate suggests trying that whiteboard before the interview. The talk centred on trade-offs and on how each part fails.
  3. Web API round: the interviewer handed over a full-stack internal admin tool, with frontend and backend code. The candidate used AI to understand it, then built a feature where a web form takes an upcoming change plus a time, and the system applies the change at that time (Schedule Future Employee Changes). They wrote both ends with AI help, tested the result, and finished with a talk about concurrency.
  4. The candidate applied for a backend role and still did frontend work. The recruiter's prep file linked a mock interview. When one round overran, it cut into the next.

174: Delivery, a manager script, document review design

Interview date: Jan 2025 · Report date: Jan 23, 2025 · Role: Software Engineer (5.5 YOE) · Location: Bengaluru · Result: Rejected after onsite coding 1

  1. Phone screen: the delivery cost tracker: drivers with hourly rates, deliveries in epoch seconds, add a driver, add a delivery and get the total owed; then pay up to a time and return what is unpaid; a third part was only discussed and is not remembered.
  2. Manager round from a script the recruiter had shared: mentors and people you mentored, and what works and what you would change at your job.
  3. Onsite design: Rippling customers upload documents for an internal audit team, and every document must be reviewed by its own deadline.
  4. Onsite coding: song plays: rank songs by different listeners, then each user's three latest songs, and the cost when three becomes any k. Rejected after this round.

History (before November 2023)

H01: Staff: design screen, then an API on your laptop

Report date: Oct 23, 2023 · Role: Staff Engineer · Result: Cleared screening; final unstated

  1. Design screen, then hiring manager screen; both cleared.
  2. Loop: system design, a talk on one of their projects, and a web API built in an hour and a half on your own laptop, so have it set up. The API's domain was not shared.

H02: Command-string database, synonyms, currency, hotels

Interview date: Oct 2023 · Report date: Dec 12, 2023 · Role: Senior Software Engineer · Location: Bangalore · Result: Rejected

  1. Screening LLD.
  2. LLD, DSA: Reducing queries under synonyms.
    • With synonym pairs and queries of several words, treat synonyms as one word and cut the queries down to the fewest distinct ones (for example, get and bring, or water and liquid).
  3. DSA.
  4. HLD: The interviewer was quiet.
    • A hotel booking system, including many bookings at the same moment.

H03: Same spreadsheet twice, then a hiring committee no

Interview date: Sep 2023 · Report date: Sep 9, 2023 · Role: L6 · Location: Bangalore · Result: Rejected by hiring committee

  1. Screening: Excel-style formulas.
    • Spreadsheet formulas like =A1+B1 given cell values; focus on data structures, production-quality code, error handling.
  2. Onsite coding 1: The same Excel question again, then a cache with transactions.
  3. HLD.
  4. Hiring manager: Business context and projects.
  5. Onsite coding 2.
    • Currency conversions with costs as a DAG (for example [USD, INR, 80]): is A to B possible and what is the minimum-cost path.

H04: A HackerRank key-value store

Report date: Aug 30, 2023 · Role: Senior Software Engineer · Result: Not stated

  1. Coding, 60 minutes on HackerRank: a key-value store with transaction support.

H05: Data store with limited commits

Report date: Aug 18, 2023 · Role: Senior Software Engineer · Location: San Francisco office · Result: Rejected

  1. Phone screen (60 minutes): about 10 to 15 minutes on the hardest, most interesting work in their current job, then about 40 minutes of coding.
  2. The task: a data store with create, read, update and delete that returns values or clear errors; part 2 adds begin, commit and rollback; part 3 adds limits, so commit(t) applies just the earliest t open transactions. They got through parts 1 and 2 with some failures and were rejected.

H06: Staff recruiter screen on leveling and full stack

Interview date: Jul 2023 · Role: Staff Software Engineer · Location: Canada · Result: No offer

  1. Recruiter screen: a possible down-level, three days a week in the office, and whether they would work across the whole stack.

H07: Delivery speed came up with a senior manager

Interview date: Mar 2023 · Report date: Apr 15, 2023 · Role: Senior Software Engineer · Result: No offer

  1. Recruiter call.
  2. Technical screen with design.
  3. Senior manager conversation: mostly about how fast projects ship. No offer.

H08: Senior Staff: recruiter talk, then the team moved on

Interview date: Mar 2023 · Role: Sr Staff Software Engineer · Location: San Francisco · Result: Declined

  1. Recruiter: A product presentation, then two technical screens were proposed, but the team moved on.

H09: One manager hour on projects and stack

Interview date: Sep 2022 · Report date: Oct 6, 2022 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer

  1. Hiring manager (about an hour): their projects, their stack and what a normal day looks like. No reply after that.

H10: Alien dictionary variant in the phone screen

Report date: Sep 2, 2022 · Role: Senior SDE · Location: USA

  1. Phone screen: They could not finish.
    • Letter Order from a Sorted Word List: Words sorted in an unknown custom order: print any order of all seen characters consistent with the list, or -1 if invalid (alien dictionary).

H11: L7 offer, questions not shared

Report date: Aug 5, 2022 · Role: Senior Software Engineer L7 · Location: Bangalore · Result: Offer

  1. DSA 1: a medium problem they had not seen before.
  2. DSA 2: close to questions earlier candidates had shared.
  3. Two design rounds.
  4. Hiring manager: their current work and a demo of the product. They got an L7 offer and turned it down.

H12: Paint canvas, social feed and metrics design

Interview date: Jul 2022 · Report date: Oct 27, 2022 · Role: Senior Software Engineer · Location: Bangalore · Result: Rejected in last round

  1. LLD.
  2. HLD.
  3. HLD.
    • Design a metrics system.
  4. DS (HackerRank): They do not remember the task, and the editor closed at 50 minutes.

H13: Employee importance with a missed follow-up

Interview date: Jun 2022 · Report date: Jul 3, 2022 · Role: SDE-2 · Result: Rejected

  1. R1 coding.
    • Team Cost Under a Manager: Variation of LeetCode Employee Importance (sum over a manager's subordinate tree); follow-up not remembered.

H14: L6 offer across five rounds

Interview date: Jun 2022 · Report date: Jul 2, 2022 · Role: L6 (SDE-2) · Location: Bengaluru · Result: Offer

  1. Five rounds: DSA, system design, a hiring manager round with a DSA question, a second hiring manager round and HR. Only topics were shared. The result was an L6 offer.

H15: L6 offer: JSON API, feeds, org trees, metrics

Report date: Apr 24, 2022 · Role: L6 · Result: Offer

  1. API design.
    • Small problem grown into API design: accept complex JSON input, validate so bad input cannot break the API, solve the problem; then extend with a design pattern.
  2. System design.
  3. Problem solving.
    • Org chart: count a manager's direct reports, then find the shared manager of two people.
    • Weighted org tree: choose nodes with no two directly connected (parent/child) and optimize the weight sum (candidate says 'minimum weights' branch).
  4. System design.
  5. System design.
    • Design an analytics system ingesting continuous streams from services to produce near-real-time performance metrics.
  6. Hiring manager.

H16: A 45-minute problem that stayed unclear

Interview date: Apr 2022 · Report date: Apr 22, 2022 · Role: Senior Software Engineer · Location: New York · Result: No offer

  1. Coding (45 minutes): a hard problem that stayed unclear to them. No offer.

H17: An ATM algorithm in 2022

Interview date: Mar 2022 · Report date: Mar 10, 2023 · Role: Senior Software Engineer · Result: No offer

  1. Initial screen.
  2. Technical screen.
  3. Algorithms.
    • Design an algorithm for an ATM.
  4. System design.

H18: Game of Life

Interview date: Mar 2022 · Report date: Mar 5, 2022 · Role: Senior Software Engineer · Result: No offer

  1. Coding.

H19: Two designs and a LeetCode hard

Interview date: Mar 2022 · Role: Senior Software Engineer · Location: New York · Result: No offer

  1. Two system design rounds and a coding round at LeetCode-hard level. No offer.

H20: SWE II: an API you lead in pair programming

Interview date: Mar 2022 · Role: Software Engineer II · Location: Canada · Result: Declined offer

  1. Recruiter.
  2. Technical screen.
  3. Product walkthrough.
  4. VO.
    • Build an API while you drive a pair-programming session.

H21: The team with the best average score

Interview date: Jan 2022 · Report date: Feb 1, 2022 · Role: Senior Software Engineer · Result: No offer

  1. Two rounds: The interviewers criticized how extensible the code was.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling Older SWE Interviews: 11 Experiences (Part 11 of 12)
0 total reactions. Your reactions: none.

Comments

0

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