You can use the link below to view a report I created for a major bug detected in the Security app I mentioned earlier. However I had to remove the screenshots and screen recordings of the actual app to avoid breaching my previous contract. But please feel free to follow up with any questions or doubts you may have.

https://docs.google.com/document/d/1VkiW-5t4YzdPJ3wW-04N25G0rSMoFlR1ImseNQxalgI/edit?usp=sharing

During my internship with SoftNet technologies, one of my first tasks was to thoroughly test and document the launch of a new in-house security app. My approach was more of a break-it mindset. where i basically just used the product by moving beyond the obvious features to hunt for special cases—like weird inputs or interrupted flows—and especially on different devices to see where the product might get stuck.

Once I found any issues, I verified that it was constant and not a one time glitch, and then I documented it with a clear step guide, including screenshots or screen recordings. Additionally, I would list down the steps to recreate the bug exactly as well, in case screenshots was not an option, or just as a safety measure in case the attachments would not load for whatever reason.

My goal was to give the developers everything they needed to see the problem exactly as I did, in the most straightforward and simple way, while prioritizing bugs based on how much they disrupted the user experience.

I am proficient in canva, adobe photoshop and adobe illustrator for graphic designing.