Quality Engineering Analyst · Toronto
I test complex digital products across mobile, web, and APIs—then build the automation and feedback loops that help teams ship with confidence.
Confidence, made visible.
01 / Selected work
Native mobile apps are my specialty: understanding how iOS and Android should feel, not only whether they technically work. I also bring deep familiarity with product analytics—from structuring clear event schemas to validating the signals teams use to understand real user behaviour.
Download résumé Coming soonProduct quality at national scale
Supporting quality across iOS and Android news experiences, internal mobile products, and multiplatform readiness for the 2026 Winter Olympics. My work combines exploratory testing, release validation, automation, and API-level investigation.
Previous experience
QA Lead · Toronto
Led testing for KOHO's cross-platform Ionic applications on iOS and Android. I investigated backend behaviour and tested APIs across sandbox and production environments, while helping shape features that improved customer satisfaction, product functionality, and company cost efficiency.
QA Analyst · Toronto
Oversaw software updates across iOS, Android, and web; contributed to roadmap strategy and every sprint plan; and wrote feature and sprint specifications. I tested front-end and back-end code manually while guiding the strategy for mobile test automation.
Reusable foundations
Appium · Java
A project-neutral foundation for native mobile automation: driver setup, reusable utilities, platform separation, and clear seams for your app-specific code.
Playwright · TypeScript
A clean starting point for browser and API testing with reusable fixtures, sensible configuration, and patterns that can grow with a real product.
Next case study
Add a concise problem, your testing strategy, and the release outcome.
Next tool
Reserve this space for a QA utility, experiment, or open-source contribution.
02 / My QA philosophy
The best QA engineers do more than find defects. They connect disciplines, represent the user, and help teams see the product as one coherent system. Building relationships with the developers, product owners, designers, and others I work with is something I value as much as my technical skills. I want to be someone people want to work with.
People skills are the most important skill in quality assurance.
QA is deeply collaborative. We work every day with developers, product managers, designers, analysts, and operations teams. We write technical specifications, organize analytics requirements, and build broad operational knowledge across systems. The job is not standing at the end of a process with a red pen; it is helping the whole team make better decisions throughout it.
To me, being QA means being the user—with enough empathy, curiosity, and platform knowledge to notice when an experience does not feel right, even if it technically “works.”
Collaborate first
Clear communication and strong relationships turn QA from a release gate into a source of shared product understanding.
Native means native
Apple's Human Interface Guidelines and Google's Material Design guidance are my practical bibles. A missing gesture or an icon that is hard to tap is as much a bug as a crash or a page that won't load because the API returned a JSON object instead of a JSON array. Pop quiz: is the standard iOS overflow icon three vertical dots or three horizontal dots? (•••) Quality also means knowing when an Android user won't recognize an iOS icon right away.
Automation + judgment
Reality check: not everything can be automated, and not everything that can should be automated. It may seem like manual testing is yesterday's game, but it isn't. Exploratory manual testing is the foundation of what makes a QA a QA. Test scripts don't think like users. Every tool has its place, and all types of testing are important.
Anyone can test one expected happy path. A QA has to imagine ten unhappy paths around it.
03 / Who am I?
I like working for people who are looking for a person—not just a set of skills.
Curiosity shapes how I test, but it also shapes the rest of my life. I am always learning a language, carrying a camera, reading one more chapter, or finding a reason to get beneath the surface. Those interests are not separate from how I work—they are where my attention to detail, empathy, and sense of exploration come from.
Where I come from
As an Indigenous person, I value opportunities to attend cultural events, powwows, language camps, and community gatherings. They keep me connected, learning, and grounded in something larger than work.
Reading
I am currently on book three of the Three-Body Problemseries. Haruki Murakami is my favourite author, and I will happily disappear into fantasy, science fiction, adventure—or a good vintage Archie comic.
Photography
Waiting for my film to get developed reminds me that not everything has to be instant. Film is my regular dose of nostalgia. Besides, who actually looks at all the photos on their phone's camera roll?
Scuba diving
I could wax lyrical about the ocean or about the transferable skills from diving to my professional life. But the truth is, every time I go down, it's terrifying but worth it. I probably read 20,000 Leagues Under the Sea too much as a kid.
I love languages. Right now I am improving my Italian for an upcoming trip to Sardinia.
Film
I love movies. If you let me talk about framing, directors, scores, or how Tarkovsky filmed that one 15-minute scene with no cuts, we will be here all day.
Check out my Letterboxd04 / Connect
Want to talk mobile testing, automation strategy, or a role where product thinking and quality engineering meet?