Rippling Frontend, Mobile, Data: 18 Experiences (Part 12 of 12)

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

Rippling frontend, mobile and data engineering interviews, 2021 to 2026: config-driven React forms, infinite scroll, JavaScript utilities and ETL design.

At a glance

  • Frontend coding: A form built from a config or schema in 4 of 12 current frontend reports (185 and 180); also infinite scroll in entry 181, a job board in entry 177 and an approval table in entry 175.
  • JavaScript: Memoize async calls in entry 181 and mapLimit in entry 182.
  • Data engineering: A batch ETL design from MongoDB to Redshift in entry 187.

Coverage: 18 experienced reports: 12 current frontend and mobile, 1 data engineering, and 5 older frontend and mobile reports in History. Job titles are kept as reported.

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: History
  • Part 12 (current): frontend and mobile, data, History

What came up

Counts over the 12 current frontend and mobile reports:

Topic Reports Last seen
Config- or schema-driven forms (1 variant or unlinked) 4 of 12 Jul 2025
Lists, paging and infinite scroll (1 variant or unlinked) 2 of 12 Oct 2025
JavaScript utilities 2 of 12 Mar 2025 (report date)

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

Frontend and mobile engineers

175: A React expense-approval table

Report date: Aug 19, 2026 · Role: Senior Software Engineer · Result: No offer

  1. React phone screen (60 min).

176: Frontend senior: an easy React task, a tough room

Interview date: Aug 2026 · Report date: Aug 24, 2026 · Role: Senior Software Engineer (frontend) · Result: No offer

  1. React coding: an easy, standard exercise, but the interviewer felt hostile. No offer.

177: A job board UI in a senior frontend screen

Interview date: Jul 2026 · Report date: Jul 9, 2026 · Role: Senior Frontend Software Engineer · Location: Sunnyvale · Result: No offer

  1. Frontend coding: build a job board UI, much like a popular practice exercise of that name. No offer.

178: React Native list built on FlatList

Interview date: Oct 2025 · Role: Senior Software Engineer (React Native) · Location: Bengaluru · Result: No offer

  1. Hands-on React Native coding: FlatList use, speed, paging and pull to reload.
    • A React Native list built on FlatList: making it fast, paging, and pull down to reload.

179: Staff full-stack: a schema-driven React task

Interview date: Jul 2025 · Role: Staff Full-Stack Engineer · Location: New York · Result: No offer

  1. Recruiter.
  2. Live React/JS coding.
    • Live React/JavaScript schema-driven challenge (likely schema-to-form).

180: A generic form, asked again a year later

Report date: Apr 18, 2025 · Role: Senior Software Engineer · Result: No offer

  1. Technical: The same exercise as a year before: a generic form.
  2. Another technical.

181: Senior frontend: async memoize and infinite scroll

Report date: Mar 10, 2025 · Role: Senior Frontend Engineer · Location: India , WFH · Result: Not selected

  1. Coding: Two frontend tasks, with no web searching allowed.
    • Memoized Async Lookups with Shared Pending Calls: Write a memoize helper for async functions that report results through callbacks: turn the arguments into a cache key and handle errors. Then: finish without a success callback, and memoize async work using neither promises nor callbacks. How they solved it: Done in ~5 min. Promise answer. Interviewer wanted a specific other answer.
    • Colors List with Load More, Then Infinite Scroll: React task: read existing code, call a cursor-paginated API and render items with a load-more button. Scale-ups: implement infinite scroll; do it without adding a scroll event listener. How they solved it: Scroll-based fetch; mentioned IntersectionObserver.

182: Senior frontend: memoization and mapLimit

Report date: Jan 24, 2025 · Role: Senior Software Engineer (frontend), downleveled to SDE2 · Result: Stopped by mutual decision

  1. Initial round: Their projects and how fast their web pages ran.
  2. Rescheduled round: Deeper memoization, mapLimit, and a question on data that keeps arriving.
    • Implement advanced memoization (JavaScript).
    • Run Tasks with a Concurrency Limit: Implement mapLimit: run an async mapper over inputs with at most N in flight.
    • A question on data that keeps arriving (no more detail).

183: Senior frontend: a team-product design round

Report date: Aug 16, 2024 · Role: Senior Frontend Developer · Result: No offer

  1. Coding, then a data structures round.
  2. System design: on the team's own product, close to LLD; it was asked a second time.
  3. Hiring manager. No offer.

184: Full stack SWE II: stores, React form, Unsplash design

Report date: Jun 27, 2024 · Role: SWE II (full stack, frontend focus) · Location: US · Result: Not selected

  1. Recruiter.
  2. Technical phone screen: Strong hire.
  3. Hiring manager 1: A 45-minute talk on architecture; no hire, citing a team match issue.
  4. Hiring manager 2: Strong hire.
  5. VO web fundamentals: No hire.
  6. VO coding: They were given the same store task again, said so, and got currency conversion instead; hire.
  7. VO FE system design: Design Unsplash using the RADIO framework; no hire.

185: A form built from configuration

Interview date: Apr 2024 · Report date: Apr 24, 2024 · Role: Senior Software Engineer - Frontend · Location: New York · Result: No offer

  1. Experience discussion.
  2. HackerRank coding.

186: React Testing Library tests

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

  1. Long process.
    • Write basic React Testing Library tests.

Data engineering

187: Senior data engineer: batch ETL design and graph DP

Report date: May 2, 2024 · Role: Senior Data Engineer · Result: Rejected

  1. Screen: one easy SQL and one easy Python question.
  2. Hiring manager: the tools they use.
  3. Talk with a VP.
  4. Project deep dive with a senior data engineer: a big project they finished.
  5. System design with a staff data engineer: a batch job that moves data from MongoDB into Redshift.
  6. Coding: two problems on graphs and DP, between medium and medium-hard. Rejected.

History (before November 2023)

H33: Senior frontend: modal, memoize and currying

Interview date: Jul 2022 · Role: Senior Frontend Engineer · Location: United States · Result: Withdrew after manager stage

  1. Recruiter.
  2. JS interview (90 min).
    • Dismiss a modal on outside click.
    • Memoization with call counts; two currying implementations.
    • Immutability examples, closure use cases, JS performance optimization.

H34: Mobile L6 offer: React Native and a social app

Interview date: Jun 2022 · Report date: Jun 28, 2022 · Role: Software Engineer L6 (mobile developer) · Location: India · Result: Offer

  1. Technical 1: React Native and JavaScript.
  2. Technical 2.
    • React Native, JavaScript and Android core-concept questions.
  3. System design.
    • Design a social app for phones, as a mobile engineer.
  4. Hiring manager: Questions on their project experience, and one problem to solve.

H35: Frontend SDE-1: flatten, bind and a mini store

Report date: May 17, 2022 · Role: SDE-1 Frontend · Location: India · Result: Rejected

  1. First round.

H36: Frontend SDE2: flatten by depth and polyfills

Interview date: Dec 2021 · Report date: Jan 4, 2022 · Role: SDE2 (frontend) · Location: Bangalore · Result: Rejected

  1. Screening: JavaScript questions.

H37: Senior frontend: currying, Tabs and a hierarchy

Interview date: May 2021 · Report date: Jul 31, 2021 · Role: Senior Software Engineer - Front End · Location: Bangalore · Result: Positive feedback, not hired over 60-day notice

  1. Technical 1 (1 h).
  2. Technical 2 (1 h): React context and hooks.
    • Plan and build a reusable React component such as Tabs or an Accordion: its props and structure.
    • Plan a reusable React form that shows validation errors and reshapes the data before it is sent to the server.
  3. Hiring manager (1 h): A coding problem on a hierarchy, plus behavioral questions.

Common questions

What does Rippling ask in the frontend interview?

A form from config data in entries 185 and 180, infinite scroll in entry 181, a job board in entry 177 and an approval table in entry 175.

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.