To make sure new features are thoroughly tested, I like to go beyond trying them just once. I test multiple times and from different angles, thinking about how different types of users might interact with the feature. For example, an employer might use a tool one way, while a student might take a completely different approach. I make a list of all the possible ways someone could use the feature, test each scenario, and document how it performs, including what works well and where issues come up. This helps ensure the feature works smoothly for everyone, not just in one specific use case.

When identifying and reporting bugs, I take a systematic approach similar to how I debug code in my data science projects. Once I identify a bug, I start by testing it again to understand what causes the problem. I try to analyze the issue using a bottom-up approach while referencing guidelines and resources throughout the process. Once I can correctly diagnose the issue, I document each finding clearly with screenshots, steps, and notes so my team members can easily follow my work. This methodical process helps me maintain accuracy, consistency, and clear communication throughout testing.

I love to travel and have visited 18 countries!