Reverse-Engineer the Search Service
Work from the brief alone. Write what you would produce — actors, requirements, data, a first slice, your unknowns — before opening anything below it; the exercise stops working if you read the reality first.
You inherit the store's product search service from a team that no longer exists: about a thousand files (illustrative), no useful README, a green test suite, and a bug report about stale results. In one day, find the mechanism, and write the page the next engineer will need. Say which files you read closely and why.
Your attempt
Nothing here is checked. It exists so that the reveal below is a comparison rather than a reading.
Proposing a rewrite because "nobody understands it". A rewrite of a system whose behaviour is unknown reproduces its unknown behaviours in new code, minus the ones that were accidentally load-bearing; the mechanism was four files away and the rewrite would have taken a quarter.
Read this even if you are confident. It is here rather than behind a button because it is the move most people actually make, it produces things that look like a project, and its cost arrives when the first hard requirement has nowhere to go.