Rippling Delivery Cost Screen: 21 Experiences (Part 2 of 12)

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

Rippling delivery cost tracker phone screens, 2025 to 2026: drivers, timed deliveries, a live total, then pay-up-to-time and peak-driver follow-ups.

At a glance

  • The task: Add drivers with hourly rates, record deliveries with start and end times, and keep a total cost for a dashboard that updates live. Then pay everything up to a time and report the unpaid cost. Part 3 asks for the peak number of drivers active at once: entry 06 gives a 24-hour window, and entries 05 and 25 only discussed it.
  • Format: Entry 08 was a 60-minute round. Entry 09 says that with AI, the three parts are expected.
  • Where it goes wrong: Money precision in entries 10 and 05, payUpTo in O(n) when a faster method was wanted in entry 12, and running out of time before part 3 in entry 09 and while coding part 3 in entry 06.
  • Practise first: Delivery Cost Tracker, then Delivery Cost Tracker with Effective-Dated Rates.

Coverage: 21 reports, Jul 2025 to Oct 2026. Levels: SDE-2 to Senior, plus reports with no level given. Places named: the U.S., the U.K., India and France.

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

The 21 reports here are the delivery cost exercise or a version of it.

Topic Reports Last seen
Delivery cost tracker (base version) 16 of 21 Oct 2026
Effective-dated rates 2 of 21 Oct 2026
Delivery task, variant not stated 2 of 21 Oct 2025
Driver balance tracker (a related task) 1 of 21 Mar 2026

Each report counts once, so the rows add up to 21.

Delivery cost phone screens

01: Delivery costs with effective-dated rates, HackerRank AI

Interview date: Oct 26, 2026 · Report date: Oct 31, 2026 · Role: Senior Software Engineer · Location: USA · Result: Rejected

  1. Recruiter screen: Completed.
  2. Technical phone screen (60 min; HackerRank with its built-in AI helper, GPT by default, Ask and Edit modes): One interviewer plus a shadow. Python. No starter code, so they wrote their own classes and checks in main(). They were still debugging the rate change with effective timestamps when time ran out on optimization.
    • Delivery Cost Tracker with Effective-Dated Rates: Food delivery cost question (multi-part): drivers, deliveries and total cost. A later part adds updating a driver's rate with an effective timestamp that changes how deliveries are costed. Then discuss optimization. How they solved it: Implemented base parts. Debugged rate-update. Discussed optimization but did not finish verifying.

02: Effective-dated delivery rates in Python

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

  1. Technical screen (HackerRank, AI allowed, no template): Python, with AI allowed and no template.
    • Delivery Cost Tracker with Effective-Dated Rates: Model driver rates, deliveries and costs (Unix timestamps): rate updates effective at a timestamp affecting delivery costs, historical rate queries, tests. Follow-ups: why float rounded to 2 decimals is wrong for money; make total-cost query O(1).

03: Delivery payments without AI

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

  1. HR screen.
  2. Technical screen (45 min): They chose no AI, since choosing AI would have meant a harder question.
    • Delivery Cost Tracker: Driver payments: add_driver(id, hourly rate), record_delivery(id, start, end), get_total_cost(), pay_up_to(time) without double paying on repeated or earlier calls, get_total_cost_unpaid().

04: Delivery billing in cents with Codex

Interview date: Oct 2026 · Report date: Oct 14, 2026 · Role: Software Engineer · Result: Not known at report time

  1. AI coding screen in their own IDE with a coding agent (Codex), screen fully shared.
  2. The delivery cost billing question. They finished two parts.
  3. To avoid rounding trouble, they stored each amount as hourly cents times seconds and turned it into decimals only for the final cost.

05: London SDE 2: delivery costs and money rounding

Report date: Jul 4, 2026 · Role: SDE 2 / SWE-2 · Location: London · Result: Pending at report time

  1. Technical phone screen: They used Copilot. The interviewer asked why BigDecimal rather than float or double, wanted exact cents, and flagged a bug between 0.005 and 0. They pasted the code into HackerRank at the end.
    • Delivery Cost Tracker: Three base calls (add a driver, add a delivery, total cost), then pay_upto_time and get_total_unpaid_cost, then the peak number of drivers working at once over the past day, discussed only. The interviewer asked how real payment systems store and round money. How they solved it: Base and payment follow-ups coded; analytics explained verbally.

06: Three delivery parts, the last one only explained

Interview date: Apr–Jun 2026 · Report date: Jun 25, 2026 · Role: Software Engineer · Result: Rejected a week later

  1. AI coding phone screen (they kept AI on). The delivery system in three parts.
  2. Part 1: addDriver, recordDelivery and getTotalCost. The interviewer asked how start and end times are handled.
  3. Part 2: payUpTo and getTotalCostUnpaid, built on part 1's data.
  4. Part 3: in a 24-hour window, the most drivers delivering at the same time. They explained an approach but ran out of time to code it.

07: Delivery costs with Cursor, three parts

Report date: Jun 23, 2026 · Role: Senior Engineer

  1. AI-assisted coding round: They could hand the prompt to Cursor if they copied the code back to HackerRank and cleared local files and chat afterwards. They switched to a faster model for the follow-ups.
    • Delivery Cost Tracker: The usual Rippling delivery cost exercise, in three coding parts. How they solved it: Talked through approach before prompting AI.

08: A 60-minute AI round on delivery payments

Interview date: Apr–Jun 2026 · Report date: Jun 5, 2026 · Role: Software Engineer · Result: Waitlisted

  1. AI-assisted coding, 60 minutes: design and build an in-memory delivery cost and payment system with add_driver(driver_id, hourly_rate), record_delivery(driver_id, start_time, end_time), get_total_cost(), pay_up_to(pay_time) and total_cost_unpaid().

09: Same question with or without AI

Interview date: Apr–Jun 2026 · Report date: Jun 2, 2026 · Role: Software Engineer · Result: Rejected

  1. First phone screen. The interviewer said the question is the same with or without AI; only the grading changes.
  2. The courier cost question: each courier has an hourly rate; build addDriver, recordDelivery(driverId, startTime, endTime) and getTotalCost. The interviewer asked how the times are handled. Follow-up: given a time, pay everything before it, plus a function for the unpaid cost.
  3. Time ran out before part 3. With AI, all three parts are expected.
  4. Tip: Zoom screen sharing from the browser misbehaved when switching to the AI window, so use the Zoom app.

10: Delivery costs where double beat BigDecimal

Interview date: Apr 15, 2026 · Report date: Jul 7, 2026 · Role: SDE-2 · Location: India · Result: Rejected

  1. Phone screen (coding): The delivery question. The interviewer, a frontend engineer, insisted on double rather than BigDecimal, and rounding went wrong at the end. AI was optional.
    • Delivery Cost Tracker: Driver delivery cost question (the often reported Rippling driver delivery problem); money precision was the sticking point. How they solved it: Wanted BigDecimal, was told to use double, precision errors at end.

11: Driver balances, cached totals, then merge intervals

Interview date: Mar 2026 · Report date: Apr 2026 · Role: Senior Software Engineer · Result: Rejected

  1. Technical screen, no AI: a driver balance tracker that returns the total balance. Because the total may be called inside a loop, keep a cached sum and update it by each change instead of rescanning. Follow-ups were about caching and prefix sums.
  2. Then a separate problem: merge intervals, with no special boundary rules.

12: payUpToTime in O(n) when binary search was wanted

Report date: Mar 5, 2026 · Role: SDE-2 · Result: Not selected

  1. Round 1: PayUpToTime done O(n), interviewer expected binary search.
    • Delivery Cost Tracker: Delivery payment system: addDriver(id, hourlyRate), recordDelivery(id, start, end) with cost = duration x rate, getTotalCost(); follow-ups payUpToTime(t) for deliveries with end <= t without reprocessing, getTotalUnpaidCost(). How they solved it: O(n) payUpToTime; interviewer wanted binary search.

13: Delivery costs with an O(1) total

Report date: Feb 26, 2026 · Role: Senior SWE · Location: Bay Area · Result: Rejected

  1. Phone screen: Part 1 gave a total cost in O(1) and all tests passed; part 2 paid up to a time with a loop, and the interviewer accepted that.
    • Delivery Cost Tracker: Drivers and deliveries cost service: addDriver, addDelivery(start, end), getTotalCost() in optimized time; then payUpToTime(t) to settle costs up to t and getCostToBePaid(). How they solved it: Running total. Linear scan for payments. Rejected anyway.
    • Delivery Cost Tracker: Clarified later by the candidate: overlapping deliveries are each paid in full (no interval merging), and the rate belongs to the driver.

14: A streaming delivery dashboard

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

  1. First round, object-oriented coding: roughly half an hour to code and half an hour of questions.

15: Delivery tracking without AI, one rounding slip

Report date: Oct 6, 2025 · Role: Senior Software Engineer · Result: Rejected

  1. Algorithmic programming round: AI was optional and they opted out. They solved it in about 35 minutes using double, with a small rounding error, and were rejected three days later.
    • Delivery Cost Tracker: Delivery tracking system: addDriver, addDelivery, payUpToTime; costs need precision at 1-second granularity. How they solved it: Used double; small rounding error.

16: A delivery payments LLD, follow-ups included

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

  1. Coding screen: an object-oriented payment system for deliveries, plus follow-ups. The report did not say which delivery variant it was.

17: Delivery with Copilot, more follow-ups expected

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

  1. HR screen.
  2. Coding round with Copilot on: the delivery cost exercise in several parts. Part 1 and a single follow-up passed. Much of the time went into reshaping the interviewer's tests for their own time format, and the feedback was that more follow-ups were expected.

18: Two delivery parts with a priority queue

Report date: Aug 31, 2025 · Role: SDE-2 · Result: Pending at report time

  1. OA: Taken while they were on the SDE-1 track; not described.
  2. Recruiter call.
  3. Phone screen: Parts 1 and 2 of the delivery cost task; the interviewer cared about object-oriented design and room to extend.
    • Delivery Cost Tracker: Drivers/deliveries cost service: addDriver, addDelivery(start, end), getTotalCost() optimized; then payUpToTime(t) and getCostToBePaid(). How they solved it: Running total; priority queue on epoch times for payments.

19: The full food delivery prompt

Report date: Aug 25, 2025 · Role: SDE2

  1. Round 1 DSA: The whole food delivery prompt was written out for them.
    • Delivery Cost Tracker: A cost dashboard for food delivery. addDriver(id, hourlyRate): each delivery is paid at that rate, and one driver may run deliveries at the same time. recordDelivery(id, start, end): times accurate to one second, no delivery longer than three hours, and you choose the time format. getTotalCost() feeds a dashboard that updates live. Part 2: payUpTo(payTime) settles deliveries that finished by payTime, and getTotalCostUnpaid() returns the rest. No threads needed; clean object-oriented code expected.

20: Paris SWE II: truck delivery costs and payments

Interview date: Jul 2025 · Report date: Nov 19, 2025 · Role: Software Engineer II · Location: Paris · Result: No offer

  1. HR.
  2. Live coding.

21: The base delivery exercise and all its parts

Interview date: Jul 2025 · Report date: Sep 4, 2025 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer

  1. Coding, AI allowed: the basic delivery system with all of its sub-parts, in a short slot. Which delivery variant it was is not clear.

Patterns across the reports

  1. Questions about the money type. Entry 05 was asked why BigDecimal over float or double; entry 10 was told to use double and then hit a rounding error; entry 15 used double and noted a small rounding error.

Common questions

What is the Rippling delivery cost question?

A driver payments service: add_driver(id, hourly_rate), record_delivery(id, start, end), get_total_cost(), then pay_up_to(time) and get_total_cost_unpaid() (19 and 08), and the peak number of active drivers (05, 06 and 25).

Should I use float or BigDecimal in the Rippling delivery question?

Entry 10 was told to use double; entry 05 was asked why BigDecimal and entry 04 stored integer cents.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling Rules and Task Screens: 22 Experiences (Part 3 of 12)
0 total reactions. Your reactions: none.

Comments

0

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