Did one for

Here’s my approach to finding and documenting bugs—I keep it methodical but practical! First, I try to recreate the issue to make sure it’s not just a random glitch, paying close attention to the exact steps, device, browser, or any quirks (like slow loading times). If it’s legit, I prioritize it—like, "this crashes the app" is way more urgent than "this button’s slightly off-center." For documentation, I keep it clean: a quick title (e.g., "Login fails on Safari after update"), step-by-step instructions to reproduce, what should happen vs. what actually happens, and a screenshot or screen recording if it helps. I’ll drop it into whatever system the team uses (Jira, Notion, even a shared Google Sheet) with relevant tags—like "mobile" or "UI bug"—so it’s easy to track. If I stumble on a possible fix (like a typo in the code), I’ll note that too, but otherwise, I stick to the facts so devs can jump in fast. It’s all about making their job easier while keeping things organized!(And yeah, I’ve done this for college projects—happy to adapt to real-world tools!)

I used to run a print on demand store. I did some campaigns like giveaways, influencer marketing. The influencer campaign failed as I didnt select the right influencer that time.