Rippling KV and Music Screens: 33 Experiences (Part 4 of 12)

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

Rippling phone screens on the music player, key-value store and spreadsheet, 2024 to 2026, plus screens where candidates kept the task private.

At a glance

  • Asked: Song play analytics in 6 reports, the key-value store with transactions in 5, a spreadsheet in 2.
  • Format: Entries 55 and 53 move from song plays to each user's last three songs; entry 127 added a limit of k songs on the summary.
  • No task shared: 13 candidates described only the format. Entry 71 had easy-to-medium coding with AI allowed; entry 67 had a late interviewer and entry 72 a spec with no design step.

Coverage: 33 reports, Feb 2024 to Oct 2026. Levels: SDE-2 to Staff, plus reports with no level given. Places named: India, the U.S., Canada and the U.K.

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: delivery screens
  • Part 3: delivery screens, rules and task screens
  • Part 4 (current): 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

Counts over the 20 screens here with a named task:

Topic Reports Last seen
Song play analytics (music player) 6 of 20 Dec 2025 (report date)
Key-value store and variants (1 variant or unlinked) 5 of 20 Mar 2026 (report date)
Spreadsheet (2 variant or unlinked) 2 of 20 Feb 2024 (report date)
Currency conversion 1 of 20 Jun 2024

Rows overlap: a report can count in more than one row.

Practical screens (continued)

44: Rules engine: 50 minutes of talk, 5 of code

Report date: Nov 28, 2025 · Role: SDE-2

  1. Coding: About 50 to 55 minutes of discussion and 5 of coding; the code had to run on the sample inputs.

45: Vote flips: the top three reversals

Interview date: Nov 2025 · Report date: Jan 15, 2026 · Role: Senior Engineer · Location: Bangalore · Result: Rejected

  1. Coding.
    • Article Vote Tracker: Vote management: users upvote/downvote articles; print the top 3 flips (vote reversals) and the linked articles.

46: Corporate card rules with Java starter code

Report date: Sep 16, 2025 · Role: Senior SWE Backend

  1. Screening: The task came with Java starter code.
    • Corporate Card Expense Rules: Sample rules: nothing above $250, at most $75 at restaurants, and no flights or entertainment. Managers pick which rules apply, and rules are saved through a separate CRUD service. Each expense is a map of strings (id, trip id, amount, type). Write evaluateRules(rules, expenses), choose what it returns, and list every flagged expense with its reason.

47: Expense rules in CodePair

Report date: Jun 3, 2025 · Role: Senior Software Engineer · Result: Rejected

  1. CodePair round: Expense rules.
    • Corporate Card Expense Rules: Validate rules against expenses (id, item, type, amount, seller type, seller name). Example rules: total over 175, restaurant over 45, no entertainment. Implement evaluateRule(rules, expenses) flagging failures.

48: Data pipeline steps, stuck on cycles

Report date: Oct 18, 2024 · Role: Mid-senior SWE · Result: Rejected at phone screen

  1. Phone screen: A pipeline task first, then processes that must run in dependency order, where they got stuck on cycles.

Music player, key-value store and other coding screens

49: Staff: transactions on an in-memory database

Report date: Mar 17, 2026 · Role: Staff Engineer

  1. Phone screen.

50: SDE3: music system, no AI, part 3 missed

Report date: Dec 19, 2025 · Role: SDE3 · Result: Rejected

  1. Coding: A music app in three parts. They could look up syntax but not use AI. They stored money as long rather than double in C++. Part 2 took 20 minutes and they had no idea for part 3.
    • Song Play Analytics: Music system in 3 sequential parts (the standard Rippling song-play analytics question). How they solved it: Parts 1-2 solved, part 3 not.

51: SWE 2: music player with follow-ups

Report date: Aug 18, 2025 · Role: SWE 2 · Result: Rejected after first technical round

  1. Recruiter.
  2. First round: Python with VS Code autocomplete; they used ChatGPT only for syntax.

52: Thread-safe cache, then the role changed

Interview date: Jul 2025 · Role: Senior Backend Engineer · Location: New York · Result: No offer

  1. Recruiter.
  2. Technical: A cache with time limits per operation that is safe across threads; passed.
    • Write a cache class that meets set time limits per operation and is safe across threads.

53: Music library in Java, out of time

Report date: Mar 11, 2025 · Role: SDE-2 · Result: Rejected

  1. Pre-screening coding (HackerRank): A music library in two parts, in Java. HackerRank gave a compile error with generics, they looked up syntax, and 55 minutes were gone before part 3.
    • Song Play Analytics: A music library: rank songs by how many different people played them, then return each user's three latest distinct songs. How they solved it: A priority queue gave them trouble, so they switched to a sorted list; at first they missed that plays count by unique users.

54: Music player OOP, follow-up not fully coded

Report date: Feb 25, 2025 · Role: Engineering (4 YOE) · Location: Bangalore · Result: Rejected

  1. Coding: Follow-up solved but not fully coded.
    • Song Play Analytics: An object-oriented implementation problem (the music player question) with a follow-up.

55: The exact music player prompt

Report date: Nov 26, 2024 · Role: Senior level, about ten years of experience · Result: Rejected

  1. Coding: song play analytics: incremental song ids, plays by user, a summary sorted by unique listeners, and each user's three latest distinct songs. State stays in memory, but millions of users and songs should shape the data structures.

56: SWE II: music analytics kept in memory

Report date: Nov 23, 2024 · Role: Software Engineer II

  1. Round 1: a music player kept in memory. addSong, playSong(songId, userId), and printAnalytics showing, for each song, how many different users played it, highest first; the candidate notes this was per day. Songs nobody played still show up.
  2. Extension: the last N songs a given user played. They had optimized code in time.

57: Key-value store to nested transactions

Report date: Nov 15, 2024 · Role: Senior Software Engineer · Result: Rejected

  1. Coding: a key-value store, then one transaction, then nested transactions. They were later told the opening was really for Staff.

58: Currency conversion rate

Interview date: Jun 2024 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer

  1. Recruiter (15 min).
  2. DSA.

59: A key-value store with a chain of follow-ups

Report date: Jun 14, 2024 · Role: Software Engineer II · Result: No offer

  1. Phone screen.
    • A key-value store with a chain of follow-ups.

60: A late edge case in the transactions store

Report date: May 28, 2024 · Role: SDE 2 · Result: Rejected

  1. Coding: a key-value database held in memory (read, write, remove), then transactions you open, commit and undo. One edge case broke near the end, and the verdict was a firm no.

61: Spreadsheet APIs in an OOP screen

Report date: Feb 26, 2024 · Role: Senior Software Engineer · Result: No offer

  1. Recruiter: Their earlier work and why they wanted to change.
  2. OOP technical screen.
    • Design APIs to insert into a spreadsheet and update cells (OOP).

62: Spreadsheet with cell references in 38 minutes

Report date: Feb 15, 2024 · Role: Senior Software Engineer · Result: Rejected

  1. Phone screen (~38 min coding): An Excel-style sheet. They were rejected because of how they structured the expression evaluation.
    • A spreadsheet with cell names like A1 or AA10 and no size limit. A cell holds a number or a formula such as 2+7, 4+9-8 or A1+B3, using only + and -. Write code that runs, with your own classes, and resolve the cell references.

63: Transactions with real tests

Report date: Feb 6, 2024 · Role: Senior SDE · Result: Passed

  1. Coding: a key-value store with transactions and tests that actually run. The trap they flagged: inside a transaction, write a marker such as None for a delete instead of deleting from an older snapshot. Test nested commit then outer rollback, delete and restore, set-delete-set, and commit or rollback with no open transaction.

Screens where no task was shared

64: Two of three parts may not be enough

Report date: Oct 19, 2026 · Role: Senior Software Engineer · Result: Implied not passed

  1. Technical screen: they finished two of three parts. Their view: at the senior level you are expected to finish all three, and AI helps you get there.

65: Clarify every requirement first

Interview date: Oct 2026 · Report date: Nov 9, 2026 · Role: Senior Software Engineer · Result: No offer

  1. A two-week process run by the recruiter.
  2. Practical coding task: their advice is to clear up every requirement before you write code. The task was not shared.

66: Seattle SWE II: timestamps and interruptions

Interview date: Sep 2026 · Report date: Oct 2, 2026 · Role: Software Engineer II · Location: Seattle · Result: No offer

  1. Recruiter: Questions on background, a project, and experience with AI.
  2. Screen (60 min; CoderPad): They were asked how timestamps are stored, and the interviewer interrupted often.

67: An interviewer who talked about himself

Report date: Aug 7, 2026 · Role: Senior SWE

  1. Technical phone screen: The interviewer came late and spoke about himself. AI was used. Only part 1 was finished and the call ended early, before code was pasted into HackerRank.

68: Senior or Staff: class-design coding first

Report date: Aug 4, 2026 · Role: Senior/Staff SWE · Result: Rejected

  1. First round: class-design coding that you implement yourself, not system design. They were rejected after it.

69: Build an API with AI, camera-off interviewer

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

  1. Technical phone screen: Build an API for a given problem with AI help; the interviewer kept the camera off.

70: Out of time on part three

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

  1. Phone screen. AI was on by default with no offer to opt out. The question itself was not named.
  2. They ran out of time on part 3 and could only explain the idea.

71: Easy LeetCode-style coding with AI allowed

Interview date: Jun 2026 · Report date: Jun 14, 2026 · Role: Senior Software Engineer · Result: No offer

  1. Coding: easy to medium, LeetCode-style, with AI allowed, plus a short talk about their current role.

72: A three-page spec in 25 minutes

Report date: May 6, 2026 · Role: Senior SWE

  1. AI phone screen: about 20 to 25 minutes to build against a three-page spec that demanded idempotency and locking. The interviewer then wanted to know why there had been no design step. The task itself was not named.

73: Rounding talk and a mis-pasted question

Report date: Apr 2, 2026 · Role: Senior Software Engineer · Location: Toronto · Result: No offer

  1. Coding: the question had been pasted in wrong, and the talk about rounding money was confusing. Their tests still passed. No offer.

74: SWE2: medium-hard coding

Report date: Mar 17, 2026 · Role: SWE2

  1. Coding: medium to hard, in line with the question lists others had shared. No task was named.

75: San Francisco senior: a 60-minute coding round

Interview date: Mar 2026 · Report date: Mar 31, 2026 · Role: Sr Software Engineer · Location: San Francisco · Result: No offer

  1. Recruiter call.
  2. Coding (60 minutes). A system design and a hiring manager round were planned next. No offer.

76: London senior: passed coding, then silence

Interview date: Nov 2025 · Report date: Dec 13, 2025 · Role: Senior Software Engineer · Location: London · Result: No offer

  1. Recruiter call.
  2. Coding: a realistic business system in the language they chose. They passed, then heard nothing more.

Patterns across the reports

  1. Distinct users, not plays. Entry 53 first missed that plays count by unique users; entry 55 sorts by unique listeners.
  2. Deletes inside transactions. Entry 63 flagged the trap: write a marker such as None for a delete inside a transaction, not a delete from an older snapshot.

Common questions

What is the Rippling music player question?

add_song, play_song(song, user) and a summary by unique listeners, then each user's last three songs (55), the last N songs (56) and a limit of k songs on the summary (127).

What is the Rippling key-value store question?

Read, write and remove (60), then begin, commit and rollback (60), then nested transactions (57 and 63).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesRippling Design and Manager Rounds: 28 Experiences (Part 5 of 12)
0 total reactions. Your reactions: none.

Comments

0

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