Rippling No-Level Onsite Loops: 24 Experiences (Part 5 of 6)

Shared by janebeingjane ·
Company
Rippling
Reports
23 interview reports
Level
Unknown
Stages
Onsite

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

At a glance

  • This part: 24 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: 24 reports, Oct 2023 to Mar 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: coding screens, onsite and full loops (2023 to 2026)
  • Part 5 (current): onsite and full loops, History (2023 to 2026)
  • Part 6: History (2020 to 2023)

Onsite and full loops (continued)

102: AI-allowed phone screen, then onsite coding rounds with fast feedback

Report date: Mar 15, 2026 · Role: Software Engineer (level not stated) · Location: San Francisco · Result: Offer

  1. Phone screen (AI coding): Any AI allowed; copy code into HackerRank.
    • A question on the cost of food deliveries.
  2. Onsite coding rounds (AI): OOD-style; feedback fast.
    • A card game question.

103: Onsite AI round ranking poker hands with a partial-hand follow-up

Interview date: Mar 2026 · Report date: Aug 25, 2026 · Role: Software Engineer

  1. Onsite AI coding.
    • Camel Cards: Rank two poker-style hands given as string arrays and return the winner.
    • Best and Worst Camel Card Completions: Follow-up: cards can be missing from the hands. Decide win, loss, tie or unknown from the partial hands, by reasoning about the best and worst way to complete each one.

104: OA, then DSA, resource manager LLD and a median variant

Report date: Feb 23, 2026 · Role: SDE-1 (0-2 years) · Location: Bangalore · Result: Rejected

  1. OA: Not described.
  2. R1 DSA.
    • Trip Booking with the Earliest Free Driver: Travel class: add drivers with hourly rates. Book trips by start and end time, choosing the driver who is free soonest. Work out each trip's cost and the running total. Extension: the fewest drivers required at one moment.
  3. R2 LLD.
    • Resource manager: add resources, remove resources, manage them efficiently.
  4. R3 DSA.
    • A twist on the median problem for two sorted arrays.

105: Onsite where nearly everything was solved within the time

Interview date: Feb 2, 2026 · Report date: Feb 4, 2026 · Role: not stated · Result: Awaiting; felt 50-50

  1. Onsite: Almost everything solved within time.

106: OA with a next greater element twist, then onsite median and LLD

Interview date: Dec 2025 · Report date: Jan 14, 2026 · Role: SDE-1 · Result: Ghosted after onsite

  1. OA.
  2. Onsite.
    • A problem in the family of the two-sorted-arrays median.
  3. LLD.

107: Two-problem DSA round on task dependencies, then access management LLD

Report date: Dec 11, 2025 · Role: SDE-1

  1. R1 DSA (60 min): Two problems.
    • Finish Order and Total Time for Dependent Tasks: Given tasks as [id, duration] and dependencies [a, b] meaning a goes before b, return how long the entire job takes plus the sequence in which the tasks finish. The second problem in the round was similar to Parallel Courses.
  2. R2 LLD (60 min).
    • Employee Resource Access Management: Employee access management: employees, resources, access types READ/WRITE/ADMIN; grant_access, revoke_access (None revokes all), retrieve_access(employee, resource), retrieve_resources(employee).

108: OA, median of sorted arrays with k lists, then project round

Interview date: Dec 9 to 10, 2025 · Report date: Dec 12, 2025 · Role: Campus software role (intern/FTE not stated) · Location: India campus · Result: Rejected

  1. OA (55 min used): 2 medium-hard DSA.
  2. R1 DSA.
    • Median of Two Sorted Arrays: Median of two sorted arrays (different approaches up to binary search); follow-up: median across k sorted lists using binary search.
  3. R2 project/managerial.

109: Phone screen on delivery system, manager chat, three onsite rounds

Interview date: Oct 2025 · Report date: Jun 22, 2026 · Role: Software engineer (level not stated) · Result: Rejected

  1. Phone screen.
    • Delivery Cost Tracker: Driver delivery system: addDriver(id, hourlyRate), assignDelivery(id, start, end), getTotalCost(); follow-ups payUptoTime(time) to pay deliveries that finished earlier than that time, and getUnpaidCost().
  2. Department screen (Hiring manager).
  3. Onsite R3 machine coding.
    • Article Vote Tracker: Article voting system: addArticle, upvote, downvote, getLast3Flips (a flip = user reverses an earlier vote); follow-ups getArticlesByScore (up minus down, sorted) and getUserLastVote(userId).
  4. Onsite R4 machine coding.
  5. Onsite R5 system design.

110: Coding screen, manager round, then onsite coding and system design

Interview date: Oct 2025 · Report date: Nov 12, 2025 · Role: Software Engineer · Location: San Francisco · Result: Accepted offer

  1. Coding screen.
  2. Hiring manager: Behavioral and project deep dive.
  3. Onsite: 2 coding and system design.

111: Delivery cost question in round one, then department and onsite rounds

Interview date: Sep 2025 · Report date: Sep 19, 2025 · Role: not stated · Result: Rejected due to one bad round

  1. R1 data structures and algorithms (an elimination round).
    • Delivery system: drivers with multiple deliveries. Compute cost. Follow-ups not reached.
  2. R2 department discussion/Hiring manager.
  3. R3-R4 onsite coding.
  4. R5 HLD.

112: Graph coding round, map coding round and a behavioral round

Interview date: Sep 2025 · Role: Software Engineer · Location: India · Result: No offer

  1. Coding 1.
    • Coding round 1 on graphs; coding round 2 on maps (problems not described).
  2. Coding 2: Maps.
  3. Behavioral.

113: HR chat on project success, then a sixty-minute coding round

Report date: Aug 25, 2025 · Role: Software Engineer · Result: No offer

  1. HR (45 min).
  2. Coding (60 min): LeetCode-style.

114: Same LLD and median question, with a linear time solution

Interview date: Aug 2025 · Report date: Aug 15, 2025 · Role: SDE I · Result: Pending

  1. LLD.
  2. DSA: O(n+m).

115: OA, recruiter call, onsite median question and access management LLD

Report date: Aug 11, 2025 · Role: SDE I · Result: Rejected

  1. OA (60 min; HackerRank): 2 medium-hard, not remembered.
  2. Recruiter call: Comp, notice, standard behavioral.
  3. Onsite DSA 1: Interviewer wanted better than O(log n).
    • Median of Two Sorted Arrays: Median of two sorted arrays. How they solved it: Brute force then O(log) solution; interviewer wanted more.
  4. Onsite LLD.
  5. Extra DSA.
    • Limit an Organization Tree's Height: Two arrays named managers[] and reportees[] give each reportee i's manager, with employee 1 as CEO; find how deep the farthest employee sits (the org tree height). Follow-up: limit the height to h by moving anyone below level h so they report straight to the CEO (their own subtrees stay intact), holding the CEO's direct reports to the smallest possible number. How they solved it: Greedy for follow-up.

116: Median salary over sorted lists, then recruiter and manager rounds

Interview date: Jul 2025 · Report date: Aug 7, 2025 · Role: Software Engineer · Location: San Francisco · Result: No offer

  1. Recruiter.
  2. Coding (60 min).
    • Median Across N Sorted Arrays: Each team has a list of employee strings (salary, name, designation) ordered by salary from high to low. Find the median salary across two such lists, then extend to n teams. The code had to pass tests.
  3. Hiring manager.

117: Recruiter, technical screen, then conventional scalable system design

Report date: Jun 16, 2025 · Role: Software Engineer · Result: No offer

  1. Recruiter.
  2. Technical screen.
  3. Onsite: Conventional scalable system design.

118: Recruiter, technical assessment and two team and leadership talks

Report date: Apr 9, 2025 · Role: Software Engineer · Result: No offer

  1. Recruiter.
  2. Technical assessment.
  3. Two team/leadership interviews.
  4. Behavioral question (round not stated).

119: A six-round process with no questions described

Report date: Mar 26, 2025 · Role: Software engineer · Result: No response after six rounds

  1. Six rounds.

120: Stack and topological sort DSA, then a professional network LLD

Interview date: Feb 2025 · Role: SDE-1 Backend Developer · Location: Bengaluru · Result: No offer

  1. DSA.
    • Problems of medium and hard difficulty in DSA, around stacks and topological sort; details not shared.
  2. Machine coding/LLD: LLD of a professional networking site.

121: Coding assessment, OOP, two hard problems and Java garbage collection

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

  1. Coding assessment.
  2. OOP questions.
    • Describe how garbage collection works in Java.
  3. A pair of hard coding problems.

122: Technical and HR rounds on projects and internship experience

Interview date: Jun 2024 · Report date: Aug 28, 2024 · Role: Software Development Engineer (SDE) · Location: New Delhi · Result: No offer

  1. Technical.
  2. Technical/HR: Projects and internship experience.

123: Coding, a system design round and an API round with mixed feedback

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

  1. Coding: Solved with 2 follow-ups.
  2. System design: Told to skip APIs/data models, then marked down for it.
  3. API round: Good review.

124: Short note about clearing the loop

Report date: Nov 24, 2023 · Role: Software engineer · Result: Offer rescinded after clearing interviews

  1. Loop: Cleared.

History (before November 2023) (continued)

H01: Data store screen using a write-ahead log, no nesting

Report date: Oct 25, 2023 · Role: not stated

  1. Phone screen: Same data-store question. WAL approach. No nested transactions per interviewer.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling No-Level Older Reports: 31 Experiences (Part 6 of 6)
0 total reactions. Your reactions: none.

Comments

0

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