Rippling Older SWE Interviews: 11 Experiences (Part 11 of 12)
- Company
- Rippling
- Level
- Full-time
- Stages
- Phone screen → Onsite
The oldest Rippling software engineer reports, 2020 to 2021: employee records, tree DP, early design rounds and fast hiring decisions.
At a glance
- Then: Entry H25 names an alien dictionary variant, entries H27 and H28 employee records, and entry H29 a design round on Aerospike versus Redis.
- Designs: Entries H15, H12 and H30 name a news or social feed design.
Coverage: 11 more experienced software engineer reports from before November 2023, kept for context. Part 10 holds the newer History reports. These reports are not counted in the overview tables.
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: 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 (current): History
- Part 12: frontend and mobile, data, History
History (continued)
H22: A distracted phone screen
Interview date: Nov 2021 · Role: Senior Software Engineer · Location: San Francisco · Result: No offer
- Phone screen: the interviewer was distracted, and the candidate kept the task private. No offer.
H23: Toronto: alien dictionary onsite
Interview date: Aug 2021 · Report date: Sep 15, 2021 · Role: Senior Software Engineer · Location: Toronto · Result: No offer
- Coding screen (1 h).
- EM, product demo (1 h).
- Onsite (3 h): Two coding rounds and a design round; they felt the database-choice discussion fell short.
- Letter Order from a Sorted Word List: Derive the character order of an alphabet from an ordered word list (alien dictionary).
H24: JSON processing with basic math
Interview date: Aug 2021 · Report date: Aug 18, 2021 · Role: Senior Software Engineer · Location: San Francisco · Result: No offer
- Phone screen coding (~40 min): JSON processing with basic math.
- Employee Salary Report by Group: Process JSON data with basic mathematical operations (aggregation).
H25: Tree DP and a modified alien dictionary
Report date: Aug 4, 2021 · Role: SDE (3 YOE) · Location: India · Result: Offer
- DS/Algo.
- DP on an N-ary tree (hard).
- Letter Order from a Sorted Word List: A changed version of the alien dictionary problem.
H26: Backend-driven UI in the design round
Interview date: Jul 2021 · Report date: Jul 23, 2021 · Role: Senior Software Engineer · Location: San Francisco · Result: No offer
- Two programming rounds.
- System design: the requirements kept changing, including a UI driven by the backend. No offer.
H27: Employee JSON, impersonation and click counts
Interview date: Jul 2021 · Role: Senior Software Engineer · Location: Bengaluru · Result: No offer
- Coding.
- Employee Salary Report by Group: Object-oriented code that aggregates employee records given as JSON, such as the average salary.
- Design.
- Design Read-Only User Impersonation: Let support staff impersonate a test user preserving the real experience while enforcing read-only access.
- Design a Product Analytics System: Take in events at scale and answer clicks per hour for the last day; how the SDK behaves when servers are down or traffic spikes.
H28: Employee records: min, max and average
Report date: Mar 31, 2021 · Role: Senior Software Engineer · Location: New York · Result: No offer
- Coding.
- Employee Salary Report by Group: Read employee records (JSON/POJO) and compute attribute aggregates such as min, max and average, with extra scenarios.
H29: A design round on Aerospike versus Redis
Report date: Mar 25, 2021 · Role: Engineering (senior, 7 YOE) · Location: Bangalore · Result: Unresolved
- Earlier rounds: went well.
- Final design round: a comparison of Aerospike and Redis, and questions on what Kafka should do in the design. The result was still open when they wrote it up.
H30: News feed, event workflows and a rectangle canvas
Interview date: Dec 2020 · Report date: Jan 15, 2022 · Role: Senior Software Engineer · Result: Rejected
- System design: a news feed (news aggregator practice).
- System design: store events, analyze them in real time and trigger workflows: A succeeding starts B, A failing starts C, and both B and C start D (durable work orchestration).
- Coding: draw rectangles on a matrix canvas, move them and handle overlap.
H31: Decisions within six hours
Report date: Sep 19, 2020 · Role: Senior Software Engineer · Result: No offer
- The whole process took about a week, and each stage decision came within about six hours, based on scorecards. No offer.
H32: Bengaluru senior offer in two weeks
Interview date: Jul 2020 · Report date: Sep 17, 2020 · Role: Senior Software Engineer · Location: Bengaluru · Result: Accepted offer
- All interviews within two weeks: algorithm problems where you write real code. They accepted an offer.
Keep practicing
- Employee Salary Report by Group: see reports H24, H27 and H28.
- Letter Order from a Sorted Word List: see reports H23 and H25.
- Rippling question banks, sign-in needed: coding, behavioral, system design and project coding.
- The Rippling interview guide, Rippling hiring insights and the Experience feed.
- More roundups: intern, new grad, no level and AI coding rounds.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.