Rippling No-Level Design, Screens: 30 Experiences (Part 2 of 6)

Shared by janebeingjane ·
Company
Rippling
Reports
30 interview reports
Level
Unknown
Stages
Phone screen

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

At a glance

  • This part: 30 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: 30 reports, Oct 2025 to Nov 2026. A date is the interview date where the report gives one, otherwise the report date. Places named: the U.S., India and Australia.

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 (current): 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)

System and low-level design screens (continued)

17: First LLD round on a corporate card rules engine

Report date: Mar 1, 2026 · Role: not stated

  1. First round (LLD).

18: LLD on employee access with expected grant validation checks

Report date: Dec 22, 2025 · Role: not stated

  1. LLD: Interviewer wanted validation/authorization checks on grant.

19: Personalized news aggregator HLD

Report date: Oct 14, 2025 · Role: not stated · Result: Rejected

  1. HLD.

Coding screens (continued)

20: No-AI screen on a task manager with an unstated duplicate rule

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

  1. Technical screen: No AI chosen. Task management parts 1-2. Interviewer insisted on unstated duplicate requirement.
    • Filter, Sort, and Deduplicate Scheduled Tasks: Tasks have an id, description, due date (-1 means none), priority flag, created date, assignee, done flag and parent task id. Part 1: write addTask with validation and printTasks, which prints unassigned, not-done tasks with priority first, then earlier due date (none last), then earlier created date. A task with a parent prints with the parent id and description. Part 2: tasks also hold child ids, and printing shows the children under the same rules. Part 3 was not seen; the candidate guessed topological order.

21: AI coding round building from scratch with an AI assistant

Report date: Oct 27, 2026 · Role: Software engineer

  1. AI coding round: Built from scratch with Claude. Not LeetCode-style. Interviewer uncooperative.

22: Phone screen on delivery billing with rate history and rounding

Report date: Oct 23, 2026 · Role: Software Engineer

  1. Technical phone screen: Delivery billing with rate history, dedup, rounding.
    • Delivery Cost Tracker with Effective-Dated Rates: A delivery billing tracker: add_driver(id, hourly rate), record_delivery(delivery_id, driver_id, start, end), get_total_cost() as a string with two decimals, and update_driver_rate(id, rate, effective_time). Repeated delivery ids are ignored. A delivery uses the rate active when it started, and rate changes never alter recorded deliveries. Overlapping deliveries are billed on their own. Deliveries over 3 hours are ignored, and only the final total is rounded.

23: AI-assisted screen on a delivery cost dashboard with rate updates

Interview date: Oct 2026 · Report date: Oct 14, 2026 · Role: Software Engineer · Result: In progress

  1. Technical screen: AI assistant.
    • Delivery Cost Tracker with Effective-Dated Rates: A delivery cost tracker with add_driver, record_delivery(delivery_id, driver_id, start, end), get_total_cost() as a string with two decimals, and update_driver_rate(id, rate, effective_time). Repeated delivery ids and deliveries over 3 hours are ignored. The rate at delivery start applies; earlier deliveries stay unchanged. Amounts are summed as integers.

24: Two-week recruiter process and an OOD phone screen without AI

Interview date: Oct 2026 · Report date: Oct 21, 2026 · Role: Software Engineer · Location: San Francisco · Result: No offer

  1. Recruiter-led, 2 weeks.
  2. Phone screen: OOD coding. Declined optional AI. Environment lacked integrated assistant.

25: Article votes screen: last three flipped articles

Report date: Sep 22, 2026 · Role: Software Engineer · Result: Finished part 1 only

  1. Technical screen: Article votes.
    • Article Vote Tracker: Add articles and record up and down votes. Detect when a user flips a vote, and return the last 3 distinct articles that user flipped. Follow-up: handle a very large flip history.

26: Task scheduler phone screen where AI was used late

Interview date: Sep 2026 · Report date: Oct 10, 2026 · Role: Software Engineer · Result: Rejected

  1. Phone screen: Switched to AI late.
    • Dependency-Aware Task Scheduler: A task scheduler: dependencies come before their dependents, priority or importance attributes affect the order, and tasks are filtered by criteria before output.

27: Sixty-minute screen on poker-style hands and best or worst completion

Interview date: Sep 2026 · Report date: Oct 1, 2026 · Role: Software Engineer · Result: In progress

  1. Phone screen (60 min): AI option chosen; 2 parts.
    • Camel Cards: Two hands of 5 cards, with 7 hand types that carry weights. Write evaluate(hand1, hand2) with a class design.
    • Best and Worst Camel Card Completions: Cards can be missing from a hand. Return its best and worst completions, for example 99 gives 99999 at best and 99321 at worst. Brute force was accepted, and a complexity analysis was asked for.

28: Technical screen with AI tools that did not go well

Report date: Sep 11, 2026 · Role: Software engineer · Result: Failed technical screen

  1. Technical screen with AI help: they failed it.

29: Coding round with a unique-character search and bracket checking

Report date: Sep 4, 2026 · Role: Software Engineer · Location: United States · Result: Offer accepted

  1. Initial call.
  2. Technical coding: Valid parentheses.
  3. Behavioral.

30: Phone screen with a camera-off interviewer and interrupted intro

Report date: Sep 4, 2026 · Role: Software Engineer · Location: United States · Result: Rejected

  1. Technical phone screen: Interviewer camera off, interrupted intro; unnamed problem solved optimally.

31: Referral DSA round on a graph solved with union-find

Interview date: Aug 2026 · Role: SDE 1 · Location: Bengaluru · Result: No offer

  1. DSA: Graph problem with DSU; referral.
    • Graph problem solved with Disjoint Set Union (approach, code, complexity).

32: Logger with handlers, then keyword search over stored messages

Interview date: Aug 2026 · Report date: Oct 10, 2026 · Role: Software Engineer

  1. Technical screen: Own IDE+AI, screen shared, HackerRank; 3 parts.
    • Stateful Log Transform and Search: A logger with independent handlers: remove a configured string, truncate to N characters, uppercase, and store without printing. Talk through a design pattern that makes new handlers easy to add.
    • Stateful Log Transform and Search: Search stored log messages by keywords and return the messages that match any keyword. Matching is case-sensitive, ignores punctuation and splits words on spaces; a message is returned once. Then optimize it.
    • Stateful Log Transform and Search: Discussion: punctuation handling, fuzzy matching, speeding up a production logger without a database or cache, and very high log volume.

33: Interview implementing an API with time lost on small requirements

Report date: Aug 13, 2026 · Role: Software Developer · Location: Sydney · Result: No offer

  1. Interview: Time lost on minor requirements.
    • Implement an API for an unspecified system.

34: Design-style phone screen with a nearly silent interviewer

Report date: Jul 28, 2026 · Role: Software engineer · Result: Feared failure

  1. Phone screen: Design-style; interviewer nearly silent.

35: First round opted out of AI, expense rule engine question

Report date: Jun 6, 2026 · Role: not stated

  1. First round: Opted out of AI.

36: Java phone screen on delivery costs with exact decimals

Report date: May 16, 2026 · Role: Software engineer · Result: Did not finish follow-ups

  1. Phone screen: Java, no AI. Delivery costs. Interviewer insisted on 2-decimal output.
    • Work out what each driver's deliveries cost, printing exactly two decimals.

37: Phone screen on votes per article and last three switches

Interview date: May 2026 · Report date: May 22, 2026 · Role: Software engineer · Result: Awaiting

  1. Phone screen: No AI option. Votes question. O(1) base.
    • Each article collects upvotes and downvotes, and a user may change their vote. For every user, return the three latest changes of vote. Follow-up: derive each article's score at the end of the day from the vote counts. How they solved it: Base O(1); follow-up O(n^2) then O(n) idea.

38: Delivery cost LLD screen stuck on a one cent difference

Report date: May 15, 2026 · Role: Software engineer · Location: Australia · Result: Rejected

  1. Phone screen: A low-level design task on delivery cost, written in Java with AI. They got stuck on a difference of 0.01. The base part was done, and the first extension was only specified.
    • A delivery cost calculation, with exact decimal output enforced.

39: Technical screen where the interviewer nitpicked code formatting

Report date: May 15, 2026 · Role: Software engineer · Result: Offer

  1. Technical screen: The interviewer picked at code style, and the candidate put those fixes off for later.

40: Screen on running expense rules, favoring OOP over if-else

Interview date: May 2026 · Report date: Sep 6, 2026 · Role: Software Engineer

  1. Technical screen: OOP over if/else.
    • Corporate Card Expense Rules: Run every rule against every expense (id, item, type, amount, seller type, seller name) and report violations. Example rules: total no more than 175, restaurants no more than 45, no entertainment. Use evaluateRule(rules, expenses) with a rule interface that is easy to extend.

41: Coding round extending a given class, with AI allowed

Report date: May 12, 2026 · Role: Software Development Engineer (SDE) · Result: No offer

  1. Coding 1: Implement functions in a given class and successive enhancements; AI allowed.

42: Technical screen with no question details given

Report date: Apr 22, 2026 · Role: Software engineer · Result: Passed technical screen

  1. Technical screen.

43: Interview where assumptions were changed during the solution

Report date: Apr 22, 2026 · Role: Software engineer

  1. Interview: Interviewer gave assumptions then reversed them mid-solution.

44: Phone screen on a corporate card expense rules engine

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

  1. Phone screen.
    • Corporate card expense rules engine.

45: Phone screen built around a logger problem

Report date: Apr 14, 2026 · Role: Software engineer

  1. Phone screen.
    • A logger-themed problem, with no other requirements stated.

46: Phone screen on corporate card rules evaluated over expenses

Report date: Apr 14, 2026 · Role: Software engineer

  1. Phone screen.
    • A corporate card rules task. The expenses are string maps. Choose the output type, then write evaluateRules(rules, expenses). The rules: a restaurant limit of 75 or less, a ban on airfare and on entertainment, a single expense of 250 or less, a trip total of 2000 or less, and meals of 200 or less per trip. The rule kinds are bans, per-expense maximums, trip totals, totals by expense type and vendor limits.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling No-Level Coding Screens: 37 Experiences (Part 3 of 6)
0 total reactions. Your reactions: none.

Comments

0

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