Rippling Intern Onsite Interviews: 18 Experiences (Part 4 of 5)
- Company
- Rippling
- Reports
- 18 interview reports
- Level
- Internship
- Stages
- OA → Phone screen → Onsite
Rippling SWE intern onsites, 2023 to 2026: coding rounds, a project or résumé deep dive, and frontend, ML or design sessions.
At a glance
- Format: Entries 72 and 75 describe three sessions in a row, and entry 74 had behavioral, ML and technical rounds back to back. The campus loop in entry 67 added LLD and HLD rounds.
- Asked: Medians in 4 of 18 loops; word counts and top-K in 3; tree height in 1, task scheduling or ordering in 1 and shortest paths in 2.
- Behavioral: Entry 73 asked about daily AI use, and entries 72 and 78 had a résumé or project discussion; see the project deep dive and AI use questions.
Coverage: 18 reports, Nov 2023 to Oct 2026 plus 1 undated. Intern loops with named tasks: SWE, backend, full-stack, frontend and ML software interns. Places named: India and the U.S.
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. PPO = pre-placement offer.
In this series
- Part 1: overview, every question table, what to practise
- Part 2: OAs, recruiter and timing reports, no-task loops
- Part 3: screens
- Part 4 (current): onsites
- Part 5: History
What came up
12 of these 18 loops mention a project or résumé conversation.
| Topic | Reports | Last seen |
|---|---|---|
| Behavioral questions | 9 of 18 | Oct 2026 (report date) |
| Heaps, caches and sorted merges | 4 of 18 | Oct 2026 (report date) |
| Graphs, trees and dependency order (1 variant or unlinked) | 4 of 18 | Oct 2026 (report date) |
| Strings, parsing and word counts | 4 of 18 | Aug 2026 (report date) |
| Medians of sorted arrays and parsed lists | 4 of 18 | Dec 2025 (report date) |
| Frontend and JavaScript (named exercises and text mentions) | 3 of 18 | May 2026 (report date) |
| REST, JSON and URL-parsing tasks in the OA (2 variant or unlinked) | 2 of 18 | Jul 2026 (report date) |
Rows overlap: a report can count in more than one row.
Onsites and full loops
67: Campus loop: priority scheduler, Splitwise LLD, leave-management design
Report date: Oct 29, 2026 · Role: SDE Intern and performance-based PPO · Location: Bangalore · Result: Selected
- OA: They solved all three.
- OA: easy string, medium binary search, hard graph questions.
- Round 1 DSA.
- In-Memory Priority Task Scheduler: Build a scheduler kept in memory where tasks can be added, removed and run in priority order. Follow-ups: ties at the same priority, the cost of each operation, and what happens with millions of tasks. How they solved it: Java; explained data structures and complexities.
- Round 2 LLD: Shared expenses, Splitwise style.
- Design a Shared Expense Splitting Service: A Splitwise-style app: people, groups, splits that are equal or by percentage, and running balances. Follow-ups: simplifying debts and adding new kinds of split later. How they solved it: Classes then Java implementation; SOLID/design patterns discussed.
- Round 3 (system design, DSA and manager): A deep dive on a project. They were told the team uses Python. The last ten minutes covered Rippling's products and culture.
- Design a Multi-Tenant Employee Leave Management System: A leave system shared by many companies: staff, leave rules, approvals and balances. Follow-ups: the database schema, keeping each company apart, caching, requests that arrive together, and growth.
- One medium problem based on hash map and sliding window.
- Walk through your college projects: the architecture, why that database, the hard parts, and what you built yourself.
- Spring Boot and Java basics: the inside of a HashMap, threads, dependency injection, REST and common annotations.
68: Tree depth, then cutting the tree height
Report date: Oct 26, 2026 · Role: SWE Intern · Result: No offer
- OA: Multiple-choice questions on data structures and three medium coding problems.
- Technical.
- Limit an Organization Tree's Height: Compute tree node depth (easy), then efficiently reduce the tree's height (hard).
69: Word counts to top-K, then a distracted project round
Report date: Aug 27, 2026 · Role: SWE Intern · Location: India campus · Result: Rejected after round 2
- Round 1 (HackerRank): Three build-up questions, each with sample tests; they cleared it.
- Top K Frequent Words: Given a document as text with words, delimiters, newlines and whitespace, return the document length counting only words (discussed several ways). How they solved it: Discussed stringstream / accumulate / counter approaches.
- Top K Frequent Words: Follow-up on the same document: find the most frequently occurring word. How they solved it: HashMap.
- Top K Frequent Words: Follow-up: return the top k frequent words.
- Round 2: The interviewer seemed distracted, and they did not clear it.
70: An OA with a GET API task, then pair programming
Report date: Jul 20, 2026 · Role: SWE Internship · Result: No offer
- OA: ~5 questions: MCQ, REST APIs, LeetCode coding (API GET exercise).
- REST API GET-method exercise (HackerRank OA).
- HackerRank pair programming.
- Resume review.
71: From traversal to shortest paths
Interview date: Jul 2026 · Report date: Aug 2026 · Role: Backend SWE Intern, Winter 2027
- A 50-minute round that grew: DFS first, then a follow-up needing Dijkstra. The graph's rules were not shared.
- Team matching came about 12 hours after the virtual onsite, in late July, with roughly ten teams to rank.
72: Full-stack coding, web fundamentals and a résumé talk
Report date: May 1, 2026 · Role: Full Stack SWE Intern · Result: No team match
- A HackerRank invite on January 8 with seven or eight MCQ and coding questions.
- Screen: a string task that grew through four follow-ups, among them top-K frequent words as the data grew (Top K Frequent Words).
- Virtual onsite, three sessions in a row: two coding problems of medium difficulty; then web basics (HTML, CSS, JS); a technical résumé discussion.
- Late in the cycle, no team matched.
73: Offline tests, a parsing problem and an AI conversation
Report date: Dec 17, 2025 · Role: SDE Summer Intern · Location: India campus · Result: Selected
- Two offline shortlisting tests with medium-to-hard ad-hoc problems.
- Technical (about 1 hour): a hard variant set in Rippling's domain, mixing parsing and strings. They laid out brute force, better and best, discussed correctness, then coded while talking, debugged and got every test green. Later parts changed the input and the data structures.
- Hiring manager: how AI compares with earlier technology shifts, why problem-solving matters when AI generates code, daily AI use, and reasoning through hard bugs; also societies, hackathons and lessons from college.
- The offer came within hours.
74: An ML round that became convex-function search
Report date: Dec 6, 2025 · Role: MLE Intern
- First technical: a simplified currency-exchange question, like LeetCode 3387 (currency conversion practice).
- Final loop, back to back: 45 minutes behavioral (general questions), 60 minutes ML, 60 minutes technical with Median of Two Sorted Arrays.
- The ML session was about minimising a convex function you cannot see inside; they tried gradient descent, then a hint led to ternary search. The rest was résumé-based ML fundamentals.
75: A four-square frontend task, string splitting and general BQ
Interview date: Nov 12, 2025 · Report date: Dec 2, 2025 · Role: Full Stack Intern · Result: Rejected
- Applied Sep 20; a three-question OA Oct 23; a technical screen Nov 2 with Median of Two Sorted Arrays (LeetCode 4).
- Onsite, Nov 12, three sessions: frontend (JavaScript task queues,
varvslet, object binding, and drawing a four-square grid in HTML and CSS); a medium string task, splitting text on several delimiters, which felt easy; and behavioral, announced as a talk about a project but really general questions such as what they would bring to a manager and their five-year plan. They felt the last was their weakest.
76: Three screen tasks and self-written tests
Interview date: Jul 2025 · Report date: Aug 11, 2025 · Role: Winter 2026 Intern
- OA invite mid-June, done early July; a recruiter call within a week.
- Mid-July screen: an easy stack task, Merge Intervals with some preprocessing, and a harder stack task, with candidate-written test cases.
- The mid-July virtual onsite question was one they had seen before; they did not say which.
77: Frontend intern: React OAs, then JavaScript and teamwork
Report date: May 1, 2025 · Role: Frontend Developer Intern · Location: India · Result: Offer
- OA 1.
- React and TypeScript component questions and DSA problems (not described).
- OA 2: Harder React and TypeScript, plus a DSA or logic problem.
- Technical interview: Questions on projects and architecture, and on teamwork.
- If people on your team disagree, what do you do?
- Tell me about a group project and how the work was shared out.
- React and JavaScript basics: closures, the useEffect, useCallback and useMemo hooks, timers and the event loop, and making builds faster for deployment.
78: Backend strings, hints and a live project demo
Report date: Jan 20, 2025 · Role: Backend Software Intern · Location: Indian campus · Result: Selected
- August 10 OA (60 min): two array problems, easy and medium-to-hard; a shortlist came out the next day.
- August 12 technical (45 min): a string problem wrapped in a story, coded on their own laptop; follow-ups and test cases were hard, and the interviewer gave hints.
- HR (50 min), 15–20 minutes later: the stacks behind their projects, how they worked, what was hard and what they would improve, with a live GitHub demo, plus activities and a curriculum project. Five students were selected.
79: Top-K by phone, shortest paths onsite
Report date: Oct 15, 2024 · Role: SWE Intern, 2025 cohort · Result: Rejected after team calls
- Applied in July. The OA: an easy coding task, a fetch-and-parse API task, a geometry task and several MCQs. A behavioral screen about two weeks later.
- Phone screen: Top K Frequent Elements (LeetCode 347).
- Virtual onsite, weeks later: a single-source shortest-path coding round and a résumé deep dive.
- Several manager calls for team matching, then word that teams had filled, then a rejection. Recruiter replies took a week or more.
80: Merge K arrays before team matching
Interview date: Aug 2024 · Report date: Jan 3, 2025 · Role: SWE Internship · Location: San Francisco · Result: Accepted offer
- A recruiter call, a phone interview, an onsite of behavioral plus coding rounds, and then matching with managers. The coding task was merging K sorted arrays, rated medium.
81: Three weeks from OA to the final loop
Report date: Mar 4, 2024 · Role: SWE Internship · Location: San Francisco
- OA, a 30-minute recruiter call, a 60-minute technical, and finally a two-hour block of coding and résumé questions, all in about three weeks.
- Topics: grid-style problems and recursive currency conversion, without detail.
82: Median and a synonym task, plus an internship deep dive
Report date: Jan 24, 2024 · Role: Intern · Result: Waiting
- Across the screen and onsite: a synonym task and Median of Two Sorted Arrays (LeetCode 4); which round asked what was not said.
- The behavioral session dug into earlier internships. All three interviewers were kind.
83: Two-array median, then two parsed N-ary tree tasks
Interview date: Nov 14, 2023 · Report date: Nov 17, 2023 · Role: SDE Intern · Result: Rejected after the onsite
- Applied Sep 9; OA invite Sep 19; OA done Sep 27 with all tests passing.
- Recruiter call (Oct 12): difficulties in an earlier internship, the project they were proudest of, preferred teams.
- Technical screen (Oct 24): Median of Two Sorted Arrays, with a linear solution accepted, then the N-array median.
- Onsite (Nov 14): parse input lists into N-ary trees, then preorder traversal and the lowest common ancestor of the deepest leaves. Both were coded, but a bug took long to find and the second one passed just before time ran out. The other session covered the résumé, behavioral questions and the design process of their proudest project.
84: A campus OA with stack encryption, then comment search
Interview date: 2025–26 campus cycle (month not given) · Role: Software Developer Intern · Process: Campus
- OA, stack encryption: start with a source string and empty temporary and output strings. Either move the source's first character to the end of the temporary string, or move the temporary string's last character to the output, until both are empty. Find the lexicographically smallest output.
- OA, transmission cost: matching character pairs cost
sameTimeand partitions costpartitionTime; minimize the extra cost. The exact rules were not formalized. - Live coding: you get comments, each with an ID and some text; list the IDs of comments that hold a given word, then widen it to matches found inside longer words (Comment Word and Substring Search). Case, tokenizing and order were left open.
- HR followed. The candidate stressed OOP and explaining while coding. No result was given.
Patterns across the reports
- Project and résumé talks. 12 of 18 loops here mention a project or résumé conversation, and 5 link to the project deep dive question (67, 69, 72, 78 and 82).
- Back-to-back sessions. Entries 72, 74 and 75 ran sessions in a row.
Common questions
What is in the Rippling intern virtual onsite?
Entries 72 and 75 (full-stack interns) include HTML, CSS or JavaScript sessions next to coding.
Does Rippling ask interns about AI?
The campus hiring manager in entry 73 asked how AI compares with earlier technology shifts and how they use it daily.
Keep practicing
- Walk me through a past project in depth: see reports 67, 69 and 72.
- Median of Two Sorted Arrays: see reports 74, 75 and 82.
- Top K Frequent Words: see reports 69 and 72.
- 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: new grad, experienced SWE, 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.