Rippling No-Level Older Reports: 31 Experiences (Part 6 of 6)

Shared by janebeingjane ·
Company
Rippling
Level
Unknown
Stages
Phone screen → Onsite

More Rippling software engineer interview reports that give no hiring level, 2020 to 2023.

At a glance

  • This part: 31 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: 31 reports, Feb 2020 to Oct 2023. A date is the interview date where the report gives one, otherwise the report date. Places named: the U.S., China, India 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: 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 (current): History (2020 to 2023)

History (before November 2023) (continued)

H02: Recruiter call, Two Sum, behavioral, then team matching

Interview date: Oct 2023 · Role: Software Engineer · Location: United States · Result: Declined offer

  1. Recruiter (30 min).
  2. VO: 1 behavioral and 2 technical.
  3. Team matching.

H03: HR call, CodeSignal OA, then trees, recursion and grids with manager

Interview date: Oct 2023 · Role: Software Engineer · Location: San Francisco · Result: No offer

  1. HR.
  2. CodeSignal OA.
  3. Coding, manager.
    • Medium/hard problems covering trees, recursion and 2D arrays (not described).

H04: Phone screen with four parts, manager chats and two onsite coding rounds

Report date: Apr 30, 2023 · Role: Software Engineer · Result: Offer

  1. Recruiter: Current work, goals and why Rippling.
  2. Technical phone screen (about 1 hour): Four building parts, all done.
  3. Two engineering manager chats: Engineering culture and testing approach, and a team match.
  4. Onsite coding 1.
    • Manipulate a data structure encoding toy employee data to produce results, with progressively harder follow-ups.
  5. Onsite coding 2: The area was unfamiliar and it went badly.
  6. Onsite system design: Architecture and failure under load, with two interviewers.
  7. 15-minute recruiter debrief.

H05: Manager talk, two coding rounds and a news recommendation design

Interview date: Apr 2023 · Role: Software Engineer · Location: Shanghai · Result: Stopped after SD

  1. Manager discussion.
  2. 2 coding.
  3. System design.
    • The design of a recommendation system for news, with focus on working out which stories are popular.

H06: Phone screen on a port manager with an O(log n) get

Report date: Mar 27, 2023 · Role: not stated

  1. Phone: Port manager; interviewer pushed space-limited O(log n) get.
    • Network Bridge Port Allocator: Network bridge firmware with N ports: get() returns a free port and marks it busy (None if none), free(id) releases it (idempotent). Follow-up: device is memory-limited, keep a bit array but make get() O(log n).

H07: Spreadsheet library round with raw versus computed cell views

Report date: Feb 5, 2023 · Role: not stated

  1. Coding: Same excel library question and view raw or aggregated values.
    • In-Memory Spreadsheet Values: Spreadsheet library. Users can view a cell either as computed value or raw formula. Code extensible for more operations.

H08: Object-oriented JavaScript, closures, promises, this binding and React lifecycle

Interview date: Dec 2022 · Role: Frontend Developer · Location: India · Result: Declined offer

  1. Interviews.
    • Questions on object-oriented JavaScript, closures, promises, call, bind and apply, and the React lifecycle.

H09: Manager screen, live OO coding and whiteboard system design

Interview date: Aug 2022 · Role: Software Engineer · Location: Warsaw · Result: No response

  1. Manager screen: Coding and behavioral.
  2. Live OO coding.
  3. Whiteboard system design.

H10: Canvas shapes screen: two parts coded, two explained

Report date: Jul 9, 2022 · Role: not stated · Result: Uncertain

  1. Phone screen: Same canvas question. Parts 1-2 coded. Parts 3-4 explained.
    • Layered Rectangle Canvas: Canvas shapes question with part 4: multiple overlaps and moves (track which shape shows after a move).

H11: Manager product demo, then system design plus a medium problem

Interview date: Jun 2022 · Role: Software Development Engineer · Location: United States · Result: Accepted offer

  1. Hiring manager product demo.
  2. One round mixing system design with a medium LeetCode problem.

H12: OA, then onsite rounds: a behavioral one and two technical ones

Interview date: Apr 2022 · Role: Software Engineer · Location: United States · Result: No offer

  1. OA.
  2. Onsite: Behavioral and 2 technical (LeetCode hard/medium).

H13: Onsite machine coding: drawing and moving shapes on a board

Interview date: Apr 2022 · Report date: Apr 29, 2022 · Role: not stated · Result: Rejected

  1. Onsite coding.
    • Layered Rectangle Canvas: N x m board with display(), draw(char, size, x, y) and move(char, newPos); most recently drawn shape wins overlaps and moving keeps the original draw priority.

H14: JavaScript round: currying, debounce and output-prediction snippets

Interview date: Mar 2022 · Report date: Aug 5, 2024 · Role: Frontend Engineer · Result: Did not advance

  1. Round 1: JS snippets where you predict the output, touching on context, hoisting, this and closures.

H15: Five rounds: employee aggregation, canvas, rollups, substrings, matrix sums

Interview date: Mar 2022 · Report date: May 8, 2022 · Role: not stated · Location: Bangalore · Result: Rejected

  1. Screening LLD: Employee aggregation.
    • Employee Salary Report by Group: From employee records, show the salary total for each department. Then widen it so the grouping key and the aggregate (min, mean) can be anything. Also implement filter-by.
  2. LLD and data-structure design.
    • Layered Rectangle Canvas: Maintain a two-dimensional canvas on which rectangles are drawn and moved through draw() and move(). Cover moves that push a rectangle past the grid edge, and then a grid with no bounds.
  3. HLD.
    • Design a Product Analytics System: Design a system that rolls events up into aggregates: client SDKs batch events, idempotent retries, server stores 15m/1h/1d rollups.
  4. DS/Algo.
    • Count Repeated Substrings: Count substrings that repeat inside a string (related to LeetCode's longest duplicate substring).
  5. DS/Algo (extra).

H16: Incremental bank account class, director talk, onsite design and coding

Interview date: Mar 2022 · Role: Software Engineer · Location: New York · Result: No offer

  1. Recruiter.
  2. Incremental class coding.
  3. Director/product.
  4. Onsite: System design and 2 coding.

H17: Phone screen medium solved cleanly in fifteen to twenty minutes

Report date: Mar 6, 2022 · Role: Software engineer · Result: Rejected

  1. Phone screen: LeetCode medium. Candidate disclosed seeing it. Optimal bug-free solution in 15-20 min.

H18: Phone screen with a medium problem solved optimally

Report date: Mar 6, 2022 · Role: Software engineer · Result: Rejected

  1. Phone screen: LeetCode medium solved optimally.

H19: Three-question assessment, a recruiter conversation and three virtual onsites

Interview date: Jan 2022 · Role: Software Engineer · Location: San Francisco · Result: Accepted offer

  1. Online assessment: three questions on HackerRank.
  2. Recruiter conversation.
  3. Virtual onsite: three interviews.

Topics named without a stage: Snakes and Ladders solved with breadth-first search (Fewest Dice Rolls to the Last Square), token limiting with a token bucket, and a tree question.


H20: Segment trees in a 90-minute assessment, then a 2D canvas round

Interview date: Dec 2021 · Role: Software Engineer · Location: Bengaluru · Result: No offer

  1. Assessment (90 min).
    • Timed test with problems of easy and medium level plus a segment-tree one (BFS, sorting, segment trees).
  2. Coding: 2D canvas create/move.

H21: Online test, then an interview on a tree question

Interview date: Nov 2021 · Role: Software Development Engineer · Location: India · Result: No offer

  1. Online test.
  2. Interview.
    • A tree question, with no further description.

H22: HR, technical and manager calls, then an onsite with coding and design

Interview date: Sep 2021 · Role: Software Engineer · Location: United States · Result: No offer

  1. HR call.
  2. Technical round (1 hour).
  3. Manager call.
  4. Onsite: two coding parts and a design part.

Topics named without a stage: a rate limiter built on a bucketing algorithm, and shortest distance with breadth-first search.


H23: Post-order tree phone screen, demo, then design and grid coding

Report date: Jul 5, 2021 · Role: not stated · Location: US · Result: No offer

  1. Phone screen (CoderPad).
    • Tree question solved with post-order traversal.
  2. Demo: Manager product demo.
  3. VO system design.
    • Typical 'design Twitter' style system design.
  4. VO coding.
  5. VO coding.
    • Stream-processing question where all data fits in memory.

H24: Design interview with a scripted, prescriptive interviewer

Report date: Apr 1, 2021 · Role: Software engineer · Location: Bangalore

  1. Design: Scripted, prescriptive interviewer.

H25: System design with an unusual prompt and slow clarification

Report date: Mar 25, 2021 · Role: Software engineer · Location: Bangalore · Result: Rejected

  1. System design: Unconventional prompt; interviewer took 30 min to clarify.

H26: Final design round with a misunderstood solution and cloud services

Report date: Mar 25, 2021 · Role: Software engineer · Location: Bangalore · Result: Negative design feedback

  1. Final design: The interviewer misread the candidate's solution and the AWS services it used.

H27: JavaScript output questions, interval merging and flat records to a hierarchy

Interview date: Sep 2020 · Report date: Nov 22, 2020 · Role: Software Engineer - Front End · Location: Bengaluru · Result: Declined offer

  1. JS/HTML/CSS.
    • Predict-the-output questions on hoisting, inheritance, this and scope, plus arrow functions and CSS specificity and positioning.
  2. Algorithms/JS: Infinite scroll.
  3. Technical Hiring manager.

H28: DSA interview that ran twenty minutes over

Interview date: Sep 2020 · Report date: Sep 26, 2020 · Role: Front End Developer · Location: Bengaluru · Result: No offer

  1. Interview: DSA; ran 20 min over.

H29: HR call, then three video rounds with string manipulation

Report date: Aug 30, 2020 · Role: Software Engineer · Result: No offer

  1. HR.
  2. 3 video technical.
    • Unspecified string-manipulation problem.

H30: Two DSA rounds, the second a redo with two mediums

Interview date: Jun 2020 · Report date: May 7, 2021 · Role: not stated · Result: Rejected

  1. DS/Algo 1: Medium then hard in last 20 min.
  2. DS/Algo 2 (re-do): Two mediums.

H31: Frontend round on event loop order, box-sizing and React refs

Interview date: May 2020 · Role: Front End Developer · Location: Bengaluru · Result: Declined offer

  1. HR.
  2. Coding: Box-sizing, event-loop ordering, scope, higher-order components, refs.
    • Predict the order of synchronous logs, setTimeout and an already resolved promise. CSS box-sizing. React higher-order components and refs.

H32: Onsite event scheduling problem with follow-up changes

Interview date: Feb 2020 · Report date: Feb 19, 2020 · Role: Software Engineer · Location: Bengaluru · Result: No offer

  1. Onsite.
    • Event scheduling problem with follow-up changes.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

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