Continued from Part 1.

The earlier accounts include a two-array median extended to N arrays, live project demonstrations, and two detailed combined-offer reports from 2021–22.

Coverage: Part 2 continues the 42-experience Rippling software-intern series with 27 candidate timelines from 2025 back to 2019. It includes U.S. SWE internships, Indian campus/backend internships, one ML-software recruiter screen, and historical internship/full-time combined offers. Exact interview years are retained only where reported.

What came up

Arrays and sorted sequences appeared in eight of these 27 experiences. Seven mentioned graphs or trees. The detailed tree, cache and score-optimization rounds below belong to the historical 2021–22 accounts.

An experience may count in several rows. The denominator includes accounts without a disclosed technical topic.

27 detailed candidate timelines, loops, and screens

15: Offline assessments, parsing and a discussion about AI

Report date: December 17, 2025 · Role: SDE Summer Intern · Location: IIIT Allahabad campus · Result: Selected

Assessments: two offline coding assessments with medium-to-hard, less routine problems.

Technical, about one hour: a hard-question variation that also involved parsing and strings. The candidate briefly outlined brute force and a better option, then discussed the correctness of their strongest approach before coding. They explained the implementation aloud, debugged several issues and passed the test cases. Follow-ups changed input characteristics and explored how the approach would change.

Hiring manager: questions on AI's future, everyday AI use, debugging, college societies and hackathons. The candidate reported an offer within hours. The post does not specify the interview month.

16: A story-wrapped median in CodePair

Interview date: December 2025 · Report date: December 16, 2025 · Role: SDE-intern · Location: Bangalore Rural · Status: No offer recorded

The campus process took one day. In a 60-minute HackerRank CodePair interview, the candidate discussed brute-force and optimal approaches to the median of two sorted arrays, then coded and ran the solution. No additional story rules were preserved.

17: CodePair Tuesday, manager Wednesday

Report date: October 31, 2025 · Role: November-start SDE internship, from thread context

An independent commenter said their CodePair round happened on Tuesday and their manager round on Wednesday. They were waiting for a decision. They did not share the coding task or exact interview dates. Another person's OA description in the thread belongs to a different applicant.

18: Merge two arrays and describe a difficult challenge

Report date: October 25, 2025 · Role: SWE Intern · Status: No offer recorded

The candidate described a HackerRank live interview with a Software Developer III. Their task label was merging two sorted arrays, which they described as hard. They also received a behavioral question about their toughest challenge. No location or further algorithm contract was provided.

19: Parenthesis nesting in a 50-minute screen

Interview date: October 2025 · Report date: October 22, 2025 · Role: SWE Intern · Location: San Francisco · Status: No offer recorded

After applying online and passing the OA, the candidate had a first virtual technical with two questions in 50 minutes. They described an easy and a medium-hard task; one asked for a string's maximum parenthesis depth. The other prompt was not shared. The interviewer expected a self-introduction and an explanation of the code while it was being written.

20: OA, recruiter, then a reported pairing stage

Report date: October 13, 2025 · Role: SWE Intern · Location: New York · Status: No offer recorded

The online applicant described a HackerRank OA and recruiter questions about background and interest in Rippling. Pair coding was listed next in the process. The account does not establish a completed pairing round or disclose its question.

21: Two hiring-manager conversations after the virtual onsite

Interview date: September 2025 · Report date: December 29, 2025 · Role: SWE Internship · Location: New York · Result: Accepted offer

This referral application took about two months: OA → recruiter → technical interview → virtual onsite with technical and behavioral work → two hiring-manager rounds. The candidate described useful hints in technical rounds and quick advancement messages, sometimes within an hour. Their reported behavioral prompts were self-introduction and why Rippling. The technical problems were not shared.

22: The interviewer wanted a particular hash-map approach

Interview date: August 2025 · Report date: October 7, 2026 · Role: SDE Intern · Location: North Guwahati · Result: Rejected after round one

The campus candidate received a string problem. They described their own solution as O(n), but said the interviewer expected a particular hash-map approach with the same time complexity. The full task and the difference between those approaches were not given. A second technical was part of the overall process; the candidate did not reach it.

23: Two-array median, then N-array median

Interview date: July 2025 · Report date: August 18, 2025 · Role: SDE-intern · Location: Allahabad · Status: No offer recorded

The campus process took three days. The OA had a medium stack task and a hard design task, neither fully described. The first technical asked for the median of two sorted arrays, then extended the question to N sorted arrays. The account does not state required complexity, examples or the design prompt.

24: One completed part and one explained part

Report date: July 13, 2025 · Role: SWE Intern · Location: New York · Result: Did not advance

The recruiter discussed background, the resume, interest in Rippling and the remaining process. The first technical lasted one hour and used a hard problem in two parts. The candidate completed the first and explained an approach for the second, then did not move forward. The problem itself was not disclosed.

25: A campus SDE interview focused on prior web work

Report publication: June 2025 · Role: SDE internship · Location: IIT Kharagpur campus · Result: Internship obtained

The candidate described HackerRank OA → coding interview → HR. The technical discussion concentrated on earlier internships, web-development experience and the stacks used, alongside coding. The book's heading says AI engineer, but the candidate explicitly says they ultimately landed an SDE role. Its two pages are one continuous account. The interview month was not specified.

26: ML-software application ended after a nontechnical screen

Interview date: January 2025 · Role: Machine Learning software summer intern 2025 · Result: Rejected after recruiter screen

January 11: applied. January 18: completed the OA. January 22: received the scheduling invitation for the nontechnical interview.

In their January 29 post and update, the candidate listed self-introduction, why Rippling, knowledge of the company, and the work/project achievement they were proudest of. The interviewer explained the company and internship process. The candidate later confirmed rejection the next day, before a technical round. No OA, ML or live-coding prompt was disclosed.

27: Backend strings, hints and a live project demo

Report date: January 20, 2025 · Role: Backend Software Intern · Location: Indian campus · Result: Selected

August 10, OA: 60 minutes, two array problems, one easy and one medium-to-hard. Results arrived the next day; 38 students were shortlisted.

August 12, technical: a 45-minute story-based string problem, coded live on the candidate's laptop. Follow-ups and test cases caused difficulty, and the interviewer supplied hints.

HR, 15–20 minutes later: a 50-minute discussion of project stacks, workflow, challenges and improvements, including a live GitHub demonstration. The panel also asked about co-curricular activities and the third-year curriculum project. Five students, including the author, were selected. The post does not state the year of those August interviews.

28: Parsing and the median of combined sorted lists

Report date: October 3, 2024 · Role: SWE Internship · Location: San Francisco · Result: Rejected

The candidate described an OA followed by a DSA interview. Their question summary named string parsing and finding the median of the merge of two sorted lists. It did not retain the data format, examples or requested implementation.

29: Merge K arrays before team matching

Interview date: August 2024 · Report date: January 3, 2025 · Role: SWE Internship · Location: San Francisco · Result: Accepted offer

The process ran through a recruiter, phone interview, onsite behavioral/technical interviews and manager matching. The named coding task was merging K sorted arrays, described as medium. Part 1 links its matching practice question.

30: Three weeks from OA through the final loop

Report date: March 4, 2024 · Role: SWE Internship · Location: San Francisco

The candidate described an OA, a 30-minute recruiter conversation, a 60-minute technical and a two-hour technical/resume loop. Their question summary mentioned grid-style problems and recursive currency conversion, without enough mechanics to reconstruct either task.

31: Math and HTTP/JSON in the OA

Interview date: January 2024 · Report date: January 25, 2024 · Role: SWE Intern · Location: San Francisco · Status: No offer recorded

The report listed four stages: OA, behavioral, algorithm technical, and a frontend/backend-specific technical. Of the OA's four questions, two concerned math and one required HTTP requests and JSON parsing; the remaining task was not described. No exact later-round question was preserved.

32: Graph coding in a four-stage account

Report date: January 17, 2024 · Role: SWE Intern · Location: San Francisco · Status: No offer recorded

The candidate listed OA → behavioral → technical with two DSA questions → matching. Graphs were the disclosed coding topic. The report does not preserve the problems' inputs, outputs or follow-ups, or clearly establish completion of matching.

33: An OA spanning algorithms and REST

Report date: October 22, 2023 · Role: SWE Internship · Result: Rejected

The candidate named HackerRank for the OA and disclosed topological sorting, heaps, REST APIs and geometry. The full task statements, question count and later interview details were not available in the account.

34: Rejected after the HR screen

Interview/report period: December 2022 · Role: SWE Internship · Result: Rejected after HR

The candidate completed an OA with three coding questions and three MCQs, then a 30-minute HR conversation about background, the resume and the company. A technical and a two-hour final—one hour behavioral, one hour technical—were described as future steps. This candidate did not complete them.

35: A graph-traversal screen for Summer 2023

Report period: December 2022 · Role: Summer 2023 SWE Intern

A firsthand commenter described graph traversal in their first technical interview and said they did not reach the final round. They did not give a complete prompt or further stage details.

36: An eight-week U.S. loop

Interview date: November 2022 · Report date: October 1, 2023 · Role: Software Engineering Intern · Location: San Francisco · Result: Accepted offer

The candidate described OA → recruiter → one-hour phone technical → onsite technical and behavioral interviews. The overall process took eight weeks. They characterized the coding as medium-to-hard without naming the tasks.

37: Graphs after a mixed OA

Report date: October 18, 2022 · Role: Software Engineering Intern

The account listed a HackerRank OA with MCQs and coding, a recruiter stage, a graph-focused technical and a final round. It did not preserve a graph prompt or a detailed outcome.

38: Jump scores and weighted endpoint picks

Original report date: August 29, 2022 · Role: FTE plus six-month internship · Result: Selected

After the OA, the 45-minute jump-score and 60-minute endpoint-pick rounds each included projects. Part 1 preserves the approaches. There was no separate HR round.

39: Three trees and a complete LFU design

Original report date: November 29, 2021 · Role: Intern+FTE · Result: Selected

Four candidates reached the one-hour design round; two were selected, including the author. Projects, challenges and future improvements preceded LFU. Part 1 preserves the tasks.

40: Four coding topics across two rounds

Report date: February 13, 2021 · Role: SWE Internship · Result: Accepted offer

The candidate described two coding rounds with two string questions, one DP question and one graph question. The hiring-manager round was skipped. No complete task statements were retained.

41: A referral and three DSA interviews in 2019

Interview period: February–April 2019 · Role: Summer Intern · Location: India · Result: Offer

The candidate described a referral and three DSA interviews between late February and late March, with difficulty rising from easy toward medium/hard. The offer arrived in April. The account was published in September 2023; the interviews belong to the 2019 cycle. Exact coding prompts were not provided.

Patterns across the reports

1. The sorted-array median returned in separate interviews. Reports 16 and 23 both named the median of two sorted arrays in 2025; report 23 extended it to N arrays. Report 28 described parsing plus a median of combined sorted lists in 2024. Report 18's merge-two-arrays label is kept separate because it does not establish a median task.

2. A solved first part could lead to a new demand. Report 07 moved from DFS to Dijkstra; report 13 added four follow-ups to a string task; report 23 expanded two arrays to N. Report 38's older loop changed ordinary endpoint picks into weighted picks. These are separate question families with their own follow-ups.

3. Projects occupied substantial interview time. The 2026 full-stack loop in report 13 included a dedicated resume discussion; report 03 described a 45-minute project deep dive. Campus report 27 included a live GitHub demo, while report 25 focused on prior internships and web stacks. Their project conversations differed in both format and role.

4. Optimization expectations differed. In report 03, an interviewer accepted a less optimal approach after hearing the reasoning. In report 22, a candidate said an O(n) string solution was insufficient because the interviewer wanted a particular hash-map approach at the same complexity. Report 14 adds close questioning of individual library calls. The reports support those individual observations, not one universal scoring rule.

5. Team matching had different endings. Report 08 reached matching two days after the virtual onsite and received an offer; report 07 described a roughly 12-hour transition to matching, with no final offer established. Report 13 reached matching but found no team late in the cycle. Passing the technical stages did not produce the same ending in these three accounts.