Rippling Senior SWE Onsite Loops: 15 Experiences (Part 6 of 12)

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

Rippling senior SWE onsite loops, 2025 to 2026: AI coding rounds, Google News design, a project presentation and practical OOP tasks.

At a glance

  • Format: Entry 105 had two AI coding rounds, a system design and a project deep dive; entry 108 had a monorepo coding round, a system design and a project presentation; entry 107 is a full-stack role.
  • Asked: Delivery costs in 2 of 15 loops, Google News design in 5, the music player in 2, a travel expense task in 3, a key-value store in 0, a project deep dive in 6.
  • Practise first: Delivery Cost Tracker, Song Play Analytics, Corporate Card Expense Rules and the news aggregator design.

Coverage: 15 reports, Sep 2025 to Nov 2026. Levels: Senior. Places named: India and the U.S.

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

What came up

Counts over 15 loops; rows overlap, since a loop can name more than one topic.

Topic Reports Last seen
Project deep dive or presentation 6 of 15 Nov 2026 (report date)
Google News-style aggregator design 5 of 15 Nov 2026 (report date)
Q&A or full-stack API coding 5 of 15 Nov 2026 (report date)
Expense rules engine 3 of 15 Aug 2026 (report date)
Task manager filter and sort 2 of 15 Nov 2026 (report date)
AI usage questions 2 of 15 Nov 2026 (report date)
Delivery cost tracker and variants 2 of 15 Nov 2025 (report date)

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

Senior onsite loops

105: AI coding twice, then Google News and a three-slide project talk

Interview date: Oct–Nov 2026 · Report date: Nov 16, 2026 · Role: Senior Software Engineer · Result: Rejected

  1. Phone screen (AI coding on HackerRank): the task list exercise that filters, sorts and removes duplicate tasks. They explained the plan first and let the AI write the code. Passed.
  2. Onsite AI coding: an HR system where one function had to change so that edits can take effect on a future date (Schedule Future Employee Changes). They explained, implemented and ran the tests. The interviewer asked which design they preferred; they had stored a snapshot per date. They think this round sank them.
  3. System design: a news aggregator like Google News. Traffic numbers, data structures, a deep dive, the database choice and how each service handles failure.
  4. Project deep dive: up to three slides on one large project, ideally built from zero. Questions on why each design and its trade-offs. Two behavioral questions came at the end: did the project involve mentoring new people, and how did you use AI in it.
  5. The candidate felt most questions had been reported by others before.

106: Senior: coding cleared, manager round did not

Report date: Nov 15, 2026 · Role: Senior Software Engineer · Result: Rejected after HM round

  1. First coding round: cleared. The candidate says studying the questions earlier candidates had shared made the difference.
  2. Hiring manager: it did not go well; they felt the two of them were not aligned, and the loop ended there.

107: A React screen, AI reimbursement rules and a frontend feed

Report date: Aug 6, 2026 · Role: Senior Full Stack Engineer · Result: Rejected

  1. Coding screen: React. They remembered only that they wrote React; no prompt details survived.
  2. AI coding: a company reimbursement and approval evaluator (corporate card expense rules). Afterwards they felt a class-only model was too rigid and rules should be data, perhaps JSON, so they can change without code. That is their own guess, not company feedback.
  3. Frontend system design: a Facebook- or X-style news feed: rich text, mentions and hashtags, hover cards, data models, paging, offline mode, list virtualization and performance.
  4. Department screen, prepared with about three pages.

108: Monorepo task: employee edits that start later

Report date: Jul 20, 2026 · Role: Senior SWE · Result: Rejected

  1. Screen: Cursor with an AGENT.md file, tasks handed out one by one, and a follow-up on whether the design would hold up when spread across machines.
  2. Onsite coding: a zipped monorepo (backend, frontend, seeded database). The task was to make employee edits start on a later date in the database and show them in the UI. They delivered the API changes and unit tests, not the UI.
  3. Onsite design: a news aggregator, drawn inside HackerRank.
  4. Hiring manager: a project presented like a promotion case.
  5. Feedback call (15 minutes). Rejected.

109: A senior backend loop with an AI task scheduler

Interview date: Jul 2026 · Report date: Sep 2026 · Role: Senior Backend Engineer · Result: Rejected

  1. Coding, 60 minutes, AI expected: tasks have a description, due date, priority, done flag and optional parent id. Remove duplicates by description and due date, drop done tasks, sort by the given priority rules, and put each child right after its parent (Filter, Sort, and Deduplicate Scheduled Tasks). They sorted the survivors, grouped children by parent and expanded once. The round also judged how they directed and checked the AI.
  2. Hiring manager, 60 minutes. It opened with a self-introduction, then their proudest project with deep follow-ups. Next: how they made operations idempotent and how they set and watch SLAs. Then a technical decision they changed midway and a design a coworker pushed back on. Last: what they would keep or leave from their current company and why Rippling. They felt a generic answer to the last one hurt. Asking how senior work is judged got the manager to explain the rubric.
  3. System design, 60 minutes: a Google News-like aggregator that pulls publisher APIs and serves a personal feed of metadata only. Follow-ups: how often the scheduler runs, when it stops, articles in many categories, feeds that grow without limit, and third-party outages and rate limits. Their design: poll workers, article and category tables, change data capture into a queue, a feed updater, Redis sorted sets per publisher and category, and a feed service that merges and dedupes.

110: Bengaluru senior: rules, camel cards, news, infinite scroll

Interview date: Jun 2026 · Report date: Aug 29, 2026 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer

  1. HR: work history, how they use AI and examples of leading.
  2. LLD with AI encouraged: the corporate card rules engine; the candidate had to own the design.
  3. Manager screen: project details, experience with financial data and design choices.
  4. LLD: Camel Cards, ranking poker-like hands.
  5. System design: Google News, with deep follow-ups on Debezium internals, cache expiry and eviction, and how Kafka consumers rebalance.
  6. Frontend: in React, show colors from a paged API, first behind a button that loads the next page and then by loading on scroll.

111: Seattle senior: coding, behavioral and a deep dive

Report date: Apr 30, 2026 · Role: Senior Software Engineer · Location: Seattle · Result: No offer

  1. Phone screen.
  2. Onsite: coding, behavioral and a project deep dive. No offer.

112: Senior loop with references at the end

Report date: Apr 29, 2026 · Role: Senior Software Engineer · Result: No offer

  1. Coding screen, then two coding rounds, a system design, a product design round with a project presentation, and a behavioral round.
  2. Two or three references were asked for at the end. No offer.

113: Claude solved the phone coding

Interview date: Apr 2026 · Role: Senior Software Engineer · Location: New York · Result: Declined offer

  1. HR call.
  2. Phone coding: LeetCode-style with AI allowed; Claude solved it.
  3. Onsite: coding, plus a design round.
  4. Project deep dive, then team matching. They got an offer and declined it.

114: Recruiter, technical and design, inattentive interviewer

Report date: Apr 1, 2026 · Role: Sr. Software Engineer · Result: No offer

  1. Recruiter call.
  2. Technical round: the interviewer did not seem to pay attention.
  3. System design. No offer.

115: Delivery, music, Google News and a Q&A API

Report date: Nov 20, 2025 · Role: Software Engineer, senior target · Result: Passed

  1. Coding: the delivery cost question: drivers have rates, deliveries have start and end times; record deliveries and work out earnings, then pay up to a time without paying twice, and find when the most drivers were active at once. This version had a fourth part whose details were not kept.
  2. Project presentation with three to five slides (project deep dive).
  3. Coding: song play analytics.
  4. System design: Google News.
  5. API coding: a Quora-style questions and answers API run on a real local server. AI was allowed in this loop.

116: San Francisco senior offer: coding and product design

Interview date: Nov 2025 · Report date: Dec 8, 2025 · Role: Senior Software Engineer · Location: San Francisco · Result: Accepted offer

  1. Technical phone screen.
  2. Manager.
  3. Onsite: Two coding rounds and a product design round.

117: Last three vote switches in O(1)

Interview date: Oct 2025 · Report date: Nov 26, 2025 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer

  1. Five technical rounds that leaned on LLD and HLD.
  2. One of them: an article service that remembers, for each user, the three latest times they switched between like and dislike, with every operation in O(1).

118: Hotel reservation, a Q&A API and song analytics

Report date: Sep 26, 2025 · Role: Senior SDE · Result: TBD at report time

  1. System design.
    • An Expedia-style booking site: find rooms for given dates and a place, book them, and pull room availability from outside hotels.
  2. Web question.
    • Build an In-Memory Community Q&A API: On starter code that runs locally, write the data models and endpoints for a Stack Overflow-style Q&A site, then talk about scaling and sharding.
  3. Coding.
    • Song Play Analytics: Add songs, record which user played which song, print songs ordered by how many different people played them, and return the last three different songs a user played.

119: Senior: strong hire on delivery, no hire on booking design

Report date: Sep 16, 2025 · Role: Senior Software Engineer · Result: Rejected

  1. R1.
    • Delivery Cost Tracker: The delivery cost exercise with extra parts, as a system that tracks what deliveries cost.
  2. R2 manager: Questions on SLAs and how work was divided; strong hire.
  3. R3 onsite: Lean hire.
  4. R4 onsite.
    • Design a booking system (HLD).
  5. R5 onsite: Questions on scale and security; the result was a hire or a strong hire.

Common questions

How many rounds is the Rippling senior SWE onsite?

Entries 119 and 120 list five rounds, with an API round in entries 119 and 120.

What is the Rippling senior project deep dive?

Entry 105 asked for up to three slides on one project, then why each design and its trade-offs.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling L7 and Senior Onsites: 18 Experiences (Part 7 of 12)
0 total reactions. Your reactions: none.

Comments

0

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