Rippling Interview Question Bank
Rippling's engineering loop is unusually concentrated: a small set of OOD coding prompts, two data-heavy system-design prompts, and a practical web API round account for most SWE interviews. The bar is driven by speed through multi-part prompts, clean extensible design, and whether the candidate can collaborate with AI tools without losing ownership of the solution.
92
questions
Last updated
Before you start
Showing 18 of 18
Best and Worst Completion of a Partial Camel Card HandCamel Cards Hand ComparisonDesign an Extensible Expense Rules EngineDelivery Billing System with Historical RatesFind Common Ancestors in a Directed GraphHierarchical Task SchedulerCurrency Exchange Query ConversionExtensible Expense Rule EngineTask Manager: Filter, Sort, and Deduplicate TasksExtensible Simplified Poker Hand Evaluator and CompletionConfigurable Expense Reimbursement Rule EvaluatorObject-Oriented Rule EngineDelivery Billing SystemCompare Two Poker HandsDesign an In-Memory Logger with Search and DeduplicationRule Evaluation Engine for ExpensesTask Scheduler with Parent-Child DependenciesFilter and Sort Task SchedulerExpense Transaction Rule EvaluatorTask Management Filtering and SortingTask Manager Filtering, Deduplication, and Priority OrderingExpense Rule EngineDesign and Implement a Sliding Window Rate LimiterLogger System with Handler Pipeline and Keyword SearchCompare two poker hands with possibly incomplete information (output UNKNOWN if winner cannot be determined)Camel Cards Hand Ranking (with Jokers or Variants)Configurable Logger With Message Transformations and StorageLongest Consecutive Sequence (variation)Pandas GroupBy Aggregation for Precision/RecallSQL Aggregation and Percentage Calculation