The author describes a Rippling recruiter screen followed by an hour-long HackerRank technical interview where AI assistance was encouraged. The recruiter discussed project impact, responsibilities, motivation, AI-tool use, and practical job requirements.
The coding exercise tracked delivery costs using driver rates that could change over time. Important requirements included ignoring duplicate delivery IDs, selecting the rate effective when a delivery began, and preserving previously recorded charges. The report emphasizes that retaining precise amounts, choosing when to round, and selecting a rounding convention are separate decisions. Tests supported accumulating fractional cents before formatting the total, but the exact half-cent rule was not confirmed. An AI debugging suggestion conflicted with that behavior. The author also distinguishes duplicate billing from precision errors and describes follow-up discussion about investigating failing tests. No hiring outcome is stated.
Discussion
Loading comments…