Rippling No-Level Screens and Loops: 18 Experiences (Part 4 of 6)

Shared by janebeingjane ·
Company
Rippling
Reports
18 interview reports
Level
Unknown
Stages
Phone screen → Onsite

More Rippling software engineer interview reports that give no hiring level, 2023 to 2026.

At a glance

  • This part: 18 reports with the question links and round notes for each.
  • Where the tables are: Part 1 has the question tables for the whole series.

Coverage: 18 reports, Nov 2023 to Nov 2026. A date is the interview date where the report gives one, otherwise the report date. 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 · OOD = object-oriented design · SD = system design · DSU = disjoint-set union · FE / BE = frontend / backend · DS/Algo = data structures and algorithms · CodeSignal / CoderPad = online coding platforms.

In this series

  • Part 1: OAs, recruiter and hiring manager conversations, system and low-level design screens (2025 to 2026)
  • Part 2: system and low-level design screens, coding screens (2025 to 2026)
  • Part 3: coding screens (2024 to 2026)
  • Part 4 (current): coding screens, onsite and full loops (2023 to 2026)
  • Part 5: onsite and full loops, History (2023 to 2026)
  • Part 6: History (2020 to 2023)

Coding screens (continued)

84: Transactional store screen, missed emptying the transaction stack

Report date: Apr 13, 2024 · Role: not stated · Result: Rejected

  1. Phone screen: Key-value question; they missed the loop that empties the transaction stack.

85: Phone screen where a transactional key-value store had to run

Report date: Apr 7, 2024 · Role: not stated

  1. Phone screen.

86: Emailed OA, then a half-hour phone call on projects and conflict

Interview date: Feb 2024 · Report date: Mar 9, 2024 · Role: Front End Developer · Location: New York · Result: No offer

  1. OA (emailed).
  2. Phone (30 min).

87: Key-value store with transactions: commit, rollback and a single nesting level

Interview date: Feb 2024 · Role: Software Engineer · Location: Seattle · Result: No offer

  1. Recruiter.
  2. Technical.
    • Key-Value Store with Nested Transactions: Make a store of keys and values that supports transactions: commit and rollback, plus plain writes made when no transaction is open; then allow a transaction inside a transaction, one level deep.
  3. Manager.

88: Two DSA rounds, one on smallest difference in a moving window

Interview date: Dec 2023 · Role: Software Engineer · Location: Bengaluru · Result: Accepted offer

  1. 2 DSA rounds: Competitive-programming oriented.

89: Transactional key store with one transaction at a time

Report date: Dec 6, 2023 · Role: not stated

  1. Phone screen: Same question, simple case: one transaction at a time.

90: Technical screen with easy to medium algorithm questions

Report date: Nov 4, 2023 · Role: Software engineer · Result: Passed technical screen

  1. Technical screen: LeetCode-style questions of easy to medium level.

Onsite and full loops (continued)

91: Onsite: scheduled field updates, project slides, analytics design

Interview date: Nov 2026 · Report date: Nov 5, 2026 · Role: Software Engineer

  1. Onsite AI coding: Frontend+backend scheduled field updates.
    • Schedule Future Employee Changes in an HR API: In an employee-management app, let users schedule field updates for future dates. Show them in history by reusing the history table. Respect employment dates. Merge same-day updates field by field. Follow-ups: backdating, reliable activation, concurrency, idempotency, error handling.
  2. Project presentation, behavioral: Slides. Interviewer disengaged. Ended early.
  3. System design.
    • Design a Product Analytics System: Design product analytics for ~1B events/day: ingestion and enrichment, minute-level dashboards, warehouse for long-range analysis, p99 under 500 ms for last-week queries; follow-ups: out-of-order events, dedup, latency.

92: Onsite AI round adding effective-dated changes to an employee app

Report date: Oct 28, 2026 · Role: SDE

  1. Onsite AI development round: Extend an employee UI and backend with changes that take effect on a set date. The code used Hibernate with Employee and EmployeeHistory models. An AI edit erased code.
    • In an existing employee app (form fields name, address, salary, position. Employee and EmployeeHistory models), add scheduled future-dated changes (for example becomes manager on a date, salary changes on a later date) persisted in the DB. Discuss applying changes at read time vs a nightly job. How they solved it: Proposed a future-edits table; later thought EmployeeHistory should be reused.

93: Rules engine screen, then metrics design, AI coding and project talk

Interview date: Oct 2026 · Report date: Oct 30, 2026 · Role: Software Engineer · Result: Passed screen; onsite likely failed AI coding

  1. Phone screen (AI coding).
    • Corporate Card Expense Rules: An expense rules engine. Follow-ups: millions of expenses against 10k rules (batching, aggregating), storing results and notifying customers, and compound rules that refer to other compound rules.
  2. Onsite system design.
    • Design a Product Analytics System: A metrics aggregation system for user events (about 1M events, 10K event types): per-day counts, location added from the client IP, and complex queries such as US clicks over 3 months.
  3. Onsite AI coding (web API).
    • Schedule Future Employee Changes in an HR API: An HR system with employee records and history. Schedule future-dated changes, for example a title change next month. The worker approach was rejected. Apply changes at read time so newer changes are not overwritten by older ones.
  4. Onsite project deep dive: 3-page slides.

94: Onsite with future-dated salary changes, news design and project talk

Interview date: Oct 2026 · Report date: Nov 11, 2026 · Role: Software Engineer · Result: Rejected

  1. VO AI coding.
    • Schedule Future Employee Changes in an HR API: An HR app that applies edits right away. Add future-dated changes (for example a salary change with an effective date) across frontend, backend and database; discuss applying on read versus on write.
  2. VO system design.
  3. VO project deep dive with director.

95: Card ranking with AI, then scheduled changes, metrics and manager round

Interview date: Oct 2026 · Report date: Nov 5, 2026 · Role: Software Engineer · Result: Rejected after manager round

  1. Phone screen: Passed.
    • A card-ranking exercise, solved with an AI assistant and unit tests.
  2. VO coding.
  3. VO system design.
  4. VO manager.

96: Three coding rounds, a high-level design and a manager round

Report date: Sep 5, 2026 · Role: Software Engineer · Result: No offer

  1. 3 coding rounds.
  2. HLD.
  3. Hiring manager.

97: News design, manager chat, hotel design, AI task scheduling onsite

Interview date: Jul 2026 · Report date: Aug 25, 2026 · Role: Software Engineer · Result: Expects rejection after onsite SD

  1. Phone screen system design: Passed.
  2. Hiring manager chat: Past project; passed.
  3. Onsite system design: Struggled on DB queries.
    • Design a hotel booking system.
  4. Onsite project deep dive.
  5. Onsite AI coding.

98: Delivery cost coding, hotel booking design and project deep dive

Report date: Jun 12, 2026 · Role: Software Engineer · Result: Rejected

  1. Coding.
  2. System design.
    • Design a hotel booking system like Expedia: requirements, APIs, data model, scaling, consistency, no double booking.
  3. Hiring manager / project deep dive.

99: Logger screen, camel cards, Google News design and a third round

Interview date: Apr 2026 · Report date: Aug 24, 2026 · Role: Software Engineer · Result: Rejected

  1. Phone screen AI coding.
    • Stateful Log Transform and Search: A logger with four features applied before printing: remove a string, truncate, capitalize, and store without printing. Then discuss searching the stored messages.
  2. Onsite AI coding: Camel cards.
  3. Onsite system design.
  4. Onsite round 3: Not described.

100: Coding-heavy process: median, currency conversion, house bounding boxes

Report date: Mar 25, 2026 · Role: Software Engineer · Result: No offer

  1. Coding-heavy process: The report names three problems.

101: Frontend loop: MCQ OA, React machine coding, DSA and manager

Interview date: Mar to Apr 2026 · Report date: May 9, 2026 · Role: Software Development Engineer, Full Stack (SDE1) · Result: Offer accepted

  1. OA (120 min): 5 frontend MCQs and 3 JS/React coding.
  2. Recruiter (25 min).
  3. React machine coding (60 min).
  4. DSA (60 min).
    • Three problems about graphs and dynamic programming: one hard one and a pair rated medium-hard.
  5. Hiring manager (45 min): FE/BE dev, system design basics, AI, projects, teamwork.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling No-Level Onsite Loops: 24 Experiences (Part 5 of 6)
0 total reactions. Your reactions: none.

Comments

0

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