Rippling SWE Interviews, No Level: 156 Experiences (Part 1 of 6)

Shared by janebeingjane ·
Company
Rippling
Reports
16 interview reports
Level
Unknown
Stages
OA → Phone screen

Rippling software engineer interviews, 2020 to 2026: reports that give no hiring level, from OAs and screens to onsite loops.

At a glance

Coverage: 156 reports, Feb 2020 to Nov 2026. A date is the interview date where the report gives one, otherwise the report date. Places named: the U.S., India, Australia, China and Poland.

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 (current): 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: onsite and full loops, History (2023 to 2026)
  • Part 6: History (2020 to 2023)

Questions we found

Counts cover the current reports in the six parts. A row counts only reports that named that exact question. History questions stay in their entries.

Coding (algorithms and object-oriented tasks): named by two or more candidates

Question Reports Last seen
Corporate Card Expense Rules 7 Oct 2026
Key-Value Store with Nested Transactions 6 Apr 2024
Delivery system (variant not stated) 5 May 2026 (report date)
Camel Cards 4 Sep 2026
Median of Two Sorted Arrays 4 Mar 2026 (report date)
Delivery Cost Tracker 3 Jun 2026 (report date)
Filter, Sort, and Deduplicate Scheduled Tasks 2 Nov 2026
Delivery Cost Tracker with Effective-Dated Rates 2 Oct 2026 (report date)
Article Vote Tracker 2 Sep 2026 (report date)
Best and Worst Camel Card Completions 2 Sep 2026
Stateful Log Transform and Search 2 Aug 2026
Corporate card expense rules (variant) 2 Apr 2026 (report date)
Median of two sorted arrays (variant) 2 Feb 2026 (report date)

Coding (algorithms and object-oriented tasks): named once

Question Reports Last seen
Most Segments That Sort the Array 1 Nov 2026 (report date)
Palindromic Paths to the Root 1 Nov 2026 (report date)
Card-ranking exercise (details not given) 1 Oct 2026
Dependency-Aware Task Scheduler 1 Sep 2026
First Character Seen Only Once 1 Sep 2026 (report date)
Balanced Bracket String Check 1 Sep 2026 (report date)
Article votes: last three switches 1 May 2026
Logger task (requirements not given) 1 Apr 2026 (report date)
Best Currency Round Trip Over Two Days 1 Mar 2026 (report date)
House Bounds in a Ragged Grid 1 Mar 2026 (report date)
Card game (details not given) 1 Mar 2026 (report date)
Expense-management system build 1 Mar 2026 (report date)
Trip Booking with the Earliest Free Driver 1 Feb 2026 (report date)
Steps to the Next Higher Value in a Circle 1 Dec 2025
Finish Order and Total Time for Dependent Tasks 1 Dec 2025 (report date)
Lowest common ancestor of a binary tree, with follow-ups 1 Oct 2025 (report date)
Concurrent dashers from timestamped events 1 Sep 2025
Limit an Organization Tree's Height 1 Aug 2025 (report date)
Median Across N Sorted Arrays 1 Jul 2025
Comment Word and Substring Search 1 Jul 2025
Lexicographically Minimum Stack Encryption 1 Jan 2025 (report date)
Longest Transfer Time in a Server Tree 1 Jan 2025
Find Minimum Time 1 Jan 2025
Maximum Currency Conversion Along a Simple Path 1 Jul 2024 (report date)
Key-value store with nested transactions (variant) 1 Apr 2024 (report date)
Closest Pair Among the Latest K Readings 1 Dec 2023

Low-Level Design (LLD/OOD)

Question Reports Last seen
Employee Resource Access Management 5 Dec 2025 (report date)
Resource manager (add and remove resources) 1 Feb 2026 (report date)
Food Order and Driver Dispatch (LLD) 1 Oct 2025 (report date)
Professional Network Core Domain (LLD) 1 Feb 2025

Project coding (APIs and full-stack features)

Question Reports Last seen
Schedule Future Employee Changes in an HR API 4 Nov 2026
Colors list: load more, then infinite scroll 3 Mar to Apr 2026
Employee app: form fields and a history model 1 Oct 2026 (report date)
Generic React Form Built From a Config 1 Aug 2025

Frontend / JavaScript

Question Reports Last seen
Frontend: build buttons and display images 1 Oct 2025 (report date)

System Design

Question Reports Last seen
Google News-style news aggregator 7 Oct 2026
User event tracking and analytics (Amplitude-style) 3 Nov 2026
Hotel reservation or booking system 2 Jul 2026

Behavioral (BQ)

Question Reports Last seen
Walk me through a past project in depth 8 Nov 2026
Which project are you most proud of? 2 Sep 2025
Tell me about a time when you provided critical feedback to… 1 Oct 2026
How do you judge whether a project succeeded? 1 Aug 2025 (report date)
A team project and how the work was split 1 May 2025 (report date)
A difficult challenge and how you solved it 1 Apr 2025 (report date)
How do you handle conflict in a team? 1 Feb 2024

Online assessments (OA)

01: OA with two coding questions: array segments and palindromic tree paths

Report date: Nov 6, 2026 · Role: SDE 1

  1. OA: Two coding questions listed.
    • Most Segments That Sort the Array: Given an integer array that may contain duplicates, split it into the maximum number of contiguous segments such that sorting each segment independently leaves the whole array sorted. Their approach: compare with a sorted copy using a running frequency balance.
    • Palindromic Paths to the Root: A tree with no edge directions, root 0, and one character on every node. For each query node q, look at the path from q up to the root and count the ancestors v for which the characters from q to v can be reordered into a palindrome. Their approach: a parity bitmask prefix, with counts of ancestor masks kept during a depth-first search.

02: Non-standard assessment where every part was completed

Report date: Apr 14, 2026 · Role: Backend engineer · Result: Rejected

  1. Assessment: Not LeetCode; all parts completed.

03: One-hour OA with two questions, all tests passed

Interview date: Aug 2025 · Report date: Oct 13, 2025 · Role: SDE1 · Result: Ghosted after OA

  1. OA (60 min): 2 questions, all tests passed.

04: OA with two questions, one fully solved and one nearly

Interview date: Aug 2025 · Report date: Aug 6, 2025 · Role: SDE-1 · Result: Pending

  1. OA: 2 questions; 1 full, other 13/15.

05: Assessment where the interviewer feedback felt misleading

Interview date: May 2025 · Report date: Sep 4, 2025 · Role: Software Engineer · Result: No offer

  1. Assessment: The candidate found the interviewer's feedback misleading.

06: Assessment with all tests passed and a quiet recruiter

Interview date: Feb 2025 · Report date: Feb 17, 2025 · Role: Frontend (level not stated) · Result: No response after assessment

  1. Assessment: All test cases passed, and the recruiter did not reply afterwards.

07: OA question about encrypting a string with a temporary string

Report date: Jan 26, 2025 · Role: not stated · Result: Passed 7/15 tests

  1. OA: Encryption string question.
    • Lexicographically Minimum Stack Encryption: Encrypt a string with help from a temporary string. Each step either takes the front character of the original and pushes it onto the back of temp, or takes the final character of temp and appends it to the output. Produce the lexicographically smallest output (for example dby to bdy). How they solved it: Multiset greedy, 7/15 tests.

08: Proctored OA: server tree transfer time and process-processor matching

Interview date: Jan 2025 · Report date: Feb 4, 2025 · Role: SDE 1

  1. OA (60 min; HackerRank, proctored, screen share and webcam): 2 medium-hard coding questions.
    • Longest Transfer Time in a Server Tree: Server network is a tree of g_nodes servers with unit-time edges; find the longest travel time between a pair of servers (the tree diameter). Samples given.
    • Find Minimum Time: N processes with sizes and m processors with capacities. A process fits a processor only if its size is no larger than the capacity; it takes 1 second, and afterwards the processor must rest 1 second prior to starting another. Return the least total time to finish every process, or -1 if that cannot be done. Samples given.

Recruiter and hiring manager conversations

09: Recruiter screen on resume, projects and decision trade-offs

Report date: Nov 2, 2026 · Role: Software Engineer · Result: No offer

  1. Recruiter screen.

10: Team match stage and impressions of the managers

Report date: Feb 3, 2026 · Role: Engineering (level not stated) · Result: Offer (declined)

  1. Team match: Matched with a team; impressions of managers demanding but not toxic.

System and low-level design screens

11: System design phone screen for a news aggregation service

Interview date: Aug 2026 · Report date: Sep 7, 2026 · Role: Software Engineer · Result: Rejected ~10 min after

  1. System design phone screen: News aggregator.

12: Design interview that ran thirty minutes over

Report date: Aug 8, 2026 · Role: Software engineer

  1. Design interview: Ran 30 min over; conversational interviewer.

13: Four-week process with a Google News-style aggregator design

Interview date: Jul 2026 · Role: Software Engineer · Result: No offer

  1. 4-week process.
  2. System design.

14: System design screen that ended fifteen minutes early

Report date: Jul 20, 2026 · Role: Software engineer · Result: Failed system-design screen

  1. System design screen: Interviewer barely engaged, ended 15 min early.

15: LLD round with a working design and notes on structure

Report date: Apr 25, 2026 · Role: Software engineering (level not stated) · Result: Rejected

  1. LLD: They got a design that worked, then heard feedback on how it was split up, how it was organized and the trade-offs.

16: Initial system design screen on a familiar question, breadth stressed

Report date: Apr 21, 2026 · Role: Software engineer · Result: Rejected

  1. Initial screen: System design, familiar question, breadth emphasized.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling No-Level Design, Screens: 30 Experiences (Part 2 of 6)
0 total reactions. Your reactions: none.

Comments

0

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