Handmade Items
Reported by candidates from Microsoft's online assessment. Pattern, common pitfall, and the honest play if you blank under the timer.
Microsoft asked this in March 2024 and it's a deceptively simple problem that catches candidates off guard. You get a list of handmade items and need to figure out what the interviewer actually wants you to do with them. The problem text isn't always clear upfront, which is the real test. If you blank on the approach during the OA, StealthCoder can read the problem on screen and surface the pattern in seconds, so you're not stuck guessing.
Pattern and pitfall
Without the full problem statement, the trick is likely around grouping, counting, or filtering items by some property (material, category, price, availability). This smells like a hash-table or array problem where you're either aggregating data, deduplicating, or sorting by a custom comparator. The gotcha is usually that the problem description is loose and you have to infer the data structure from examples. During the live OA, if the problem feels ambiguous, slow down and map the input to the expected output carefully. That's where most candidates lose time. StealthCoder lets you lock in the pattern without second-guessing.
StealthCoder is the hedge for the one pattern you didn't drill. It runs invisibly during the screen share.
You can drill Handmade Items 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. If you're reading this with an OA window open, you're who this was built for.
Get StealthCoderRelated leaked OAs
This OA pattern shows up on LeetCode as group anagrams. If you have time before the OA, drill that.
You've seen the question.
Make sure you actually pass Microsoft's OA.
Microsoft reuses patterns across OAs. If you're reading this with an OA window open, you're who this was built for. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Handmade Items FAQ
Is this a sorting or grouping problem?+
Most likely grouping or counting. Handmade items problems typically ask you to bucket items by a property (like material or maker) and return aggregated results. If the output is a list of items in a specific order, sorting is involved. Read the examples first, not the description.
How do I prepare for this if I've never seen the exact problem?+
Brush up on hash-table aggregation and stable sorting. Know how to group objects by a key, count occurrences, and sort by multiple fields. Practice building a frequency map and reconstructing output. These are the building blocks.
What's the most common mistake on handmade items problems?+
Assuming the problem wants you to sort or filter when it actually wants grouping, or vice versa. Second mistake: not handling edge cases like duplicate items or missing fields. Read the constraints and examples carefully.
Can I solve this with a simple loop or do I need DP?+
No DP. This is a single-pass or two-pass problem. Hash-table for aggregation, then sort or reconstruct. If you're thinking dynamic programming, you've misread the problem.
How much time should I spend on this in the OA?+
If the problem is under 20 lines of actual logic, aim for 15-20 minutes total. If you're stuck after 10 minutes on understanding, use the examples to reverse-engineer what the output should be.