Who I am

I’m Dmitry Yarygin, a senior software QA engineer, technical educator, and digital nomad. My work sits at the intersection of hands-on testing, mobile debugging, automation, and clear technical communication.

This site is where I turn field experience into practical tutorials for QA engineers, mobile testers, and technical people who want to understand how applications behave beyond the happy path.

What I focus on now

  • Mobile QA strategy for Android and iOS applications, including regression, release, exploratory, and new-feature testing.
  • Modern automation and tooling with Playwright, Selenium WebDriver, Appium, Espresso, JUnit, Pytest, Allure, Postman, Newman, Python, Java, Swift, shell scripting, and API tools.
  • Android debugging, network traffic analysis, API testing, device setup, logs, proxy workflows, and reproducible test environments.
  • Localization and accessibility testing, especially where language, device behavior, and user experience meet.
  • Hardware-adjacent testing such as firmware updates, device connectivity, configuration changes, and reliability checks.
  • Practical security-minded QA topics, including vulnerability-management basics, computer-forensics fundamentals, and mobile security lab work.

Experience highlights

  • 15+ years in software quality across web, mobile, desktop, virtualization, e-commerce, education, and technical content.
  • Senior QA consulting work through Upwork since 2018 for clients and end customers including SurveyMonkey, Britelite Immersive, Sutter Health, Visa, Tempur-Pedic, and PackageCenter.
  • Former Software Test Engineer at Google, where I tested Gmail and Inbox for iOS and Android, contributed mobile automation, investigated user-reported issues, and worked closely with development, product, localization, and accessibility teams.
  • Earlier QA roles included MokaFive desktop virtualization testing and PhoneFunShop mobile-content/e-commerce testing.
  • Instructor experience with OTUS, where I created and taught a Mobile QA Engineer course covering mobile test environments, debugging, Appium setup, automation-framework fundamentals, and connectivity testing.

How I approach testing

Good QA is not only a checklist. I care about building a reliable picture of product risk: what changed, what can break, what users actually do, and what evidence helps developers fix problems quickly.

That usually means combining structured test documentation with hands-on investigation: test plans, matrices, checklists, clean bug reports, logs, screenshots, videos, proxy captures, device states, and reproduction steps that another person can follow.

Technical background

I have a university degree in Information Technology and an Android Developer Nanodegree. My day-to-day technical background includes Windows, macOS, Linux, Android, iOS, Docker, virtual machines, Postman, Charles Proxy, Wireshark, Procmon, ADB, Xcode, Jira, Asana, Bugzilla.

I speak English, Russian, and Spanish, which is one reason localization testing has always been more than a checkbox for me.

Beyond QA

I also write technical articles, create tutorials and videos, experiment with Linux and Android labs, and enjoy music. I play guitar and like projects that combine practical engineering with curiosity, creativity, and real devices.

Connect