Rippling No-Level Coding Screens: 37 Experiences (Part 3 of 6)

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

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

At a glance

  • This part: 37 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: 37 reports, Apr 2024 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 (current): 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)

Coding screens (continued)

47: Fifty-minute expense management system build, all tests passed

Report date: Mar 1, 2026 · Role: Software Engineer · Location: New York · Result: No offer

  1. Coding (50 min; HackerRank): Expense management system. Tests passed. Rejected next day.
    • Write an expense management tool in a 50-minute HackerRank session.

48: Phone interview on hourly delivery pay, with AI use encouraged

Report date: Feb 25, 2026 · Role: not stated

  1. Phone interview: LLM use encouraged; recruiter unreliable.
    • Delivery Cost Tracker: Delivery workers paid hourly: part 1 total paid to all workers; part 2 pay workers up to a time (include work finished before cutoff) and cache instead of recomputing.

49: Delivery payment phone interview, part two only explained

Report date: Feb 25, 2026 · Role: not stated

  1. Phone interview: Interviewer pushed alternative thinking.
    • A delivery payment question: part 1 was solved and part 2 was only explained.

50: Coding and LLD round where typing speed in Java mattered

Report date: Feb 2, 2026 · Role: not stated · Result: Rejected

  1. Coding/LLD: Speed needed to type all code in Java.

51: Hour-long screen covering only part one of camel cards

Interview date: Jan 2026 · Report date: Aug 24, 2026 · Role: Software Engineer · Result: Expects rejection

  1. Technical screen (~60 min): Camel cards part 1 only.
    • Camel Cards: Camel cards for two players with 4-card hands, cards labelled 1 to 9. Hand types rank four of a kind, two pair, three of a kind, one pair, then high card, and the list can grow. Ties are broken by comparing cards from right to left without sorting. Write evaluate(hand1, hand2) returning HAND_1, HAND_2 or TIE.

52: Phone screen LLD on food delivery with driver assignment

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

  1. Phone screen: a dictionary could stand in for the database.

53: Frontend interview building buttons and rendering different images

Report date: Oct 13, 2025 · Role: Fullstack (frontend focus)

  1. Interview.
    • Implement buttons and frontend features such as displaying and rendering different images.

54: Recruiter call, then designing and implementing an API

Report date: Oct 6, 2025 · Role: Software Engineer · Result: No offer

  1. Recruiter.
  2. Coding.
    • Design and implement an unspecified API.

55: Technical screen with AI turned off and the whole task solved

Report date: Oct 5, 2025 · Role: Software engineer · Result: Rejected

  1. Technical screen: They chose not to use AI and finished the main task together with its extension.

56: Pair programming on lowest common ancestor, plus behavioral talk

Report date: Oct 5, 2025 · Role: Software Engineer · Location: San Diego · Result: No offer

  1. Pair programming, behavioral.
    • LeetCode 236 (lowest common ancestor of a binary tree) with follow-ups.

57: No-AI screen with three expected questions and OOP classes

Report date: Oct 3, 2025 · Role: Software engineer

  1. Technical screen: No AI was allowed. Three questions were expected, built around object-oriented classes, with tests written for each answer. They ran out of time testing the last part.

58: Web fundamentals: a color list fed by an API, with paging and scroll

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

  1. Web fundamentals.

59: Recruiter call, then a coding round on improving time complexity

Interview date: Sep 2025 · Role: Full Stack Developer · Location: United States · Result: Accepted offer

  1. Recruiter.
  2. Coding/problem solving: Improve time complexity.

60: Counting concurrent dashers from timestamped events

Interview date: Sep 2025 · Report date: Aug 25, 2026 · Role: Software Engineer · Result: Passed

  1. Technical screen.
    • Count concurrent dashers from timestamped +1/-1 events. Follow-up: one dasher can hold several orders at once (count once). Ties: process -1 before +1 at equal times.

61: Reimbursement approval rules with group-level spending limits

Interview date: Sep 2025 · Report date: Aug 24, 2026 · Role: Software Engineer

  1. Technical screen.
    • Corporate Card Expense Rules: Approve or reject expense reimbursements with configurable rules. Follow-up: group-level limits (for example a trip total cap of $2,500) reject the whole group, and the rejected items are reported.

62: Rushed interviewer asking about proudest and hardest projects

Interview date: Sep 2025 · Role: Frontend Developer · Location: San Jose · Result: No offer

  1. Interview: Rushed interviewer.

63: Coding task in stages, with every follow-up and extra passing

Report date: Aug 28, 2025 · Role: not stated · Result: Rejected (feedback appeared to reference another candidate)

  1. Coding: a task split into stages with follow-ups; every stage and the extras passed.

64: First web fundamentals round: build a dynamic React form

Interview date: Aug to Sep 2025 · Report date: Aug 29, 2025 · Role: Frontend Engineer · Result: Rejected after first round

  1. Web fundamentals (first round): Build a React form whose fields change dynamically. Interviewer seemed satisfied. Rejected 2 days later.

65: OOP heap problem and criticism for AI use

Report date: Aug 14, 2025 · Role: Software engineer · Result: Rejected at technical screen

  1. Technical screen: An object-oriented problem that used heaps. They were criticized for their use of AI.
    • An introductory object-oriented exercise that used heaps; follow-ups were expected.

66: Exact string search in a list, then substring matching

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

  1. Coding: String lookup variations.

67: Expense rule engine offered as an API, only part one finished

Report date: Jun 14, 2025 · Role: not stated

  1. Coding: 3 parts, only part 1 done.
    • Corporate Card Expense Rules: Client companies reach an engine for expense rules through an API: managers add rules (for example entertainment max $250, any expense max $300, trip max $1000). Given rules and expenses (id, trip id, amount, type, vendor type, vendor name) flag violated rules per expense. Interviewer focused on rule modelling and response body. How they solved it: Only part 1 of 3 finished.

68: Coding round: the basics and 80% of the follow-up done

Report date: Jun 11, 2025 · Role: not stated · Result: Rejected

  1. Coding: The basics and 80% of the follow-up were done.

69: Org chart review, a teamwork question and standard algorithms

Report date: May 30, 2025 · Role: Software Engineer · Location: San Francisco · Result: No offer

  1. Recruiter: Org chart review.
  2. Technical: Standard algorithms.
  3. Behavioral question (round not stated).

70: Interview with a real-life frontend coding question

Interview date: Mar 2025 · Role: Software Engineer · Location: San Francisco · Result: No offer

  1. Interview: a coding question drawn from real frontend work.

71: Coding round where one follow-up was done in time

Report date: Mar 19, 2025 · Role: Software engineer

  1. Coding: One follow-up was done. A second follow-up was to be tried only if time allowed.

72: Interview question comparing JS with JSX

Interview date: Mar 2025 · Role: Frontend Developer · Location: Bengaluru · Result: Accepted offer

  1. Interview.
    • How JS differs from JSX.

73: Coding round with only a single follow-up completed

Report date: Mar 11, 2025 · Role: Software engineer · Result: Rejected

  1. Coding: they got through a single follow-up.

74: Technical screen: solution and extension finished, tests passing

Report date: Mar 10, 2025 · Role: Software engineer · Result: Rejected

  1. Technical screen: finished the solution and its extension, the tests passed, and they optimized it.

75: Technical phone screen where the task was building a React app

Interview date: Oct 2024 · Role: Software Engineer · Location: New York · Result: No offer

  1. Technical phone screen: Build a React app.

76: Live React screen: component, state and a cursor-paginated API

Interview date: Jul 2024 · Role: Frontend Engineer · Location: United States · Result: No offer

  1. Recruiter.
  2. Live React screen.

77: Phone round on currency conversion solved with DFS

Report date: Jul 12, 2024 · Role: not stated

  1. Phone round: Used DFS.

78: Frontend round on JavaScript fundamentals

Report date: Jun 25, 2024 · Role: Frontend SWE

  1. Frontend round: JavaScript fundamentals.

79: Round one key-value store with commit, rollback and nested transactions

Report date: Apr 30, 2024 · Role: Software engineer · Result: Rejected

  1. Round 1.
    • Key-value store with nested transactions (commit/rollback).

80: Coding round on designing an Excel sum formula

Report date: Apr 30, 2024 · Role: Software engineer · Result: Rejected

  1. Coding: build the sum formula feature of an Excel-style sheet.

81: Live coding on their own laptop, in an IDE

Report date: Apr 30, 2024 · Role: Software engineer

  1. Live coding: They coded on their own laptop in an IDE, and the problem did not resemble LeetCode questions.

82: Key-value store with undo stack, forty minutes in total

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

  1. Phone screen: Same key-value question. Stack of operations for undo. 40 min total.

83: Transactional store screen, unsure if writes show before commit

Interview date: Apr 2024 · Report date: Apr 25, 2024 · Role: not stated · Result: Expected rejection

  1. Phone screen: Misread whether writes propagate before commit.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling No-Level Screens and Loops: 18 Experiences (Part 4 of 6)
0 total reactions. Your reactions: none.

Comments

0

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