All About Rewards
Reported by candidates from Amazon's online assessment. Pattern, common pitfall, and the honest play if you blank under the timer.
Amazon's 'All About Rewards' OA landed in March 2025 and it's a simulation problem that looks deceptively simple. You're tracking reward accumulation and redemption across transactions, which means state management and edge cases matter more than algorithmic brilliance. The trap is assuming the problem wants a greedy solution when it actually needs careful sequencing. StealthCoder sits in your corner if you blank on the logic mid-OA, but the real win here is understanding the reward lifecycle before you hit record.
Pattern and pitfall
This is fundamentally a simulation where you track reward balances, apply rules in the right order, and handle special conditions. The common pitfall is misunderstanding when rewards apply (first transaction, minimum spend threshold, category restrictions) or the order of operations (do discounts reduce the reward base, or not). You'll likely need to iterate through events, maintain state, and return a final count or value. The pattern is simulation plus careful state tracking. If you get stuck on the exact rule interpretation during the live OA, StealthCoder can read the problem statement in real time and guide you through the correct sequence. Most candidates overthink it or apply rules in the wrong order.
If this hits your live OA and you blank, StealthCoder solves it in seconds, invisible to the proctor.
You can drill All About Rewards cold, or you can hedge it. StealthCoder runs invisibly during screen share and surfaces a working solution in under 2 seconds. The proctor sees the IDE. They don't see what's behind it. Built by an Amazon engineer who would have shipped this the night before his JPMorgan OA if he'd had it.
Get StealthCoderRelated leaked OAs
You've seen the question.
Make sure you actually pass Amazon's OA.
Amazon reuses patterns across OAs. Built by an Amazon engineer who would have shipped this the night before his JPMorgan OA if he'd had it. Works on HackerRank, CodeSignal, CoderPad, and Karat.
All About Rewards FAQ
Is this a straightforward simulation or is there a trick?+
It's a simulation, but the trick is rule ordering and edge cases. Read the exact wording on when rewards apply, which transactions qualify, and whether overlapping rules stack or conflict. Test your logic against boundary cases before submitting.
Do I need dynamic programming or greedy for this?+
No. This is pure simulation and state tracking. No optimization algorithm needed. Build a clean state machine, apply rules in the order specified, and iterate through transactions. Correctness beats fancy.
How do I prepare in 48 hours with no problem text?+
Expect to track account balances and apply conditional logic. Practice reading ambiguous rule sets and coding defensively. Run through scenarios like zero transactions, maximum limits, and category mismatches. You'll be fastest if you can parse English clearly.
Will they ask me to optimize or return intermediate states?+
Likely just the final result. But be ready to explain your state transitions out loud. Amazon often wants to see how you think through multi-step processes, not just the answer.
Is this Amazon-specific or a pattern I'll see elsewhere?+
Simulation and state tracking show up everywhere (payment systems, game loops, financial transactions). The 'rewards' theme is Amazon-flavored, but the underlying skill is recognizing when to simulate instead of optimize.