Rippling Software Engineer interview experience: financial precision coding

The coding challenge was the familiar driver-delivery system problem, and I had heard that Rippling used a relatively small pool of widely discussed questions. Financial representation mattered a great deal during the implementation. I had to justify using a particular numeric type instead of floating point.

A copilot-style assistant inserted changes that did not meet the precision requirements. Tests produced an incorrect small fraction where the value should have been zero, so I had to correct the precision myself. The interviewer wanted us in the code quickly. After the initial functions, I added follow-up functions for payout timing and unpaid costs, then tested those as well.

The interview was intense because financial precision was the real bottleneck. I did not receive an offer, but I came away understanding how seriously they treated edge cases and representation.

Location: London, England. Overall feedback: Positive. Offer status: No offer.