Get Experience
Reported by candidates from Amazon's online assessment. Pattern, common pitfall, and the honest play if you blank under the timer.
Amazon's 'Get Experience' problem hit the OA circuit in May 2024, and candidates are blanking on it because the problem text is vague and the pattern isn't obvious from the title alone. You're looking at a string or array manipulation problem that requires careful parsing of what 'experience' actually means in context. The trick is almost always in how you interpret the input, not in the algorithm itself. StealthCoder reads the exact problem statement on your screen and will surface the pattern in real time if you freeze.
Pattern and pitfall
Without the full problem text, the pattern could be string matching, counting operations, or simulation. The likely move is breaking down an experience string or list into components, then applying a rule to filter, sort, or aggregate them. Common pitfalls: misreading what constitutes a valid experience entry, off-by-one errors in indexing, and forgetting to handle edge cases like empty inputs or duplicate values. During the live OA, if the problem statement feels ambiguous, reread the examples carefully. StealthCoder will flag the actual pattern once it parses the full problem, so you're not guessing blind.
Memorize the pattern. If you can't, run StealthCoder. The proctor sees the IDE. They don't see what's behind it.
You can drill Get Experience 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. Made by an engineer who treats the OA as theater. If yours is tonight, you don't have time to grind. You have time to hedge.
Get StealthCoderRelated leaked OAs
You've seen the question.
Make sure you actually pass Amazon's OA.
Amazon reuses patterns across OAs. Made by an engineer who treats the OA as theater. If yours is tonight, you don't have time to grind. You have time to hedge. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Get Experience FAQ
Is this a string manipulation or data structure problem?+
Most likely string manipulation with some form of parsing or filtering. It could involve splitting, matching patterns, or counting occurrences. The examples in the OA will clarify whether you're building a result or just returning a count.
What's the most common mistake on this one?+
Misinterpreting what counts as valid experience. Read the examples twice. Candidates often miss edge cases like whitespace, case sensitivity, or what happens when experience is empty or malformed.
Do I need to optimize for time complexity?+
Probably not heavily. Amazon OAs often accept O(n) or O(n log n) solutions for non-hard problems. Focus on correctness first. Optimization is secondary unless the problem explicitly warns about large input sizes.
How much time should I spend on this in the OA?+
If it's the only problem, 20-30 minutes max. If there are multiple problems, treat it as a warm-up. It's likely medium difficulty. Don't overthink the pattern. Code, test against examples, move on.
Will this problem show up again or is it one-off?+
Amazon rotates OA problems regularly, but similar experience-parsing patterns appear often. If you understand the parsing and filtering logic here, you'll recognize the pattern in future Amazon OAs.