Rippling·Software Engineer·Technical Phone Screen
- Given a list of expenses (each with fields like amount, category, employee, and date) and a list of rules (each with conditions and an action like approve or flag), write code to evaluate every expense against every rule and return which rules match each expense.
- Extend your rule engine with product-level considerations: richer field types, how results would be surfaced to users, and edge cases you'd need to handle in a real product.
- Extend the rule engine so that individual rules can have compound conditions joined by AND and OR, including nested combinations. Evaluate these boolean expressions against each expense.
“Straightforward on the surface but the matching logic trips you up if you don't think about how to represent conditions cleanly.”