I focus my expertise on three thing generally. First, does our solution really fix the issue that it is addressing. Second does our solution not only work, but does it make our system better as a whole. I am interesting in solutions that also take performance into account. Third I focus on helping other QAs level up. I try to make sure that when I learn or try something I share it so others may use it. I also believe that it is better to not only know how something works but also why. If we can get our QAs to have an engineering mindset and not just a testing mindset, we will start seeing massive improvements on our quality because they start owning some of the problem (and solution) instead of just executing someone else's orders (learned from Extreme Ownership - topic of decentralized leadership)
Minor in General Business
Brand 360 Project
This was my first experience in Automated Testing. Before this I was doing more functional/physical testing. I was on many projects and became a major leader both in the QA community but also in the technical community as well.
Scrum Master Responsibilities:
Dev Team Responsibilities:
Software Development Engineer in Test Responsibilities:
Build Engineering Responsibilities:
Resumes, and other information uploaded or provided by the user, are considered User Content governed by our Terms & Conditions. As such, it is not owned by us, and it is the user who retains ownership over such content.
Many factors go into creating a strong resume. Here are a few tweaks that could improve the score of this resume:
Job Titles Held: