Gleb S.

I'm a Software QA specialist with 7+ years of experience in Manual Testing, focused on catching the defects that scripts and automated checks miss before your users do. I also handle Performance Testing, so you get functional coverage and load behavior checked by the same person. 📊 AT A GLANCE • 7+ years in Software QA across web, mobile, API and AI-powered products • 134 projects tested • 88% of my clients are long-term clients • 3,500+ hours on a single long-term SaaS engagement as the embedded QA partner on the team • Consistent five-star reviews citing communication, reliability and quality • 5+ years of QA engagements on Upwork • Available for Manual Testing on one release or for ongoing QA coverage 🎯 WHY THE HUMAN CHECK STILL MATTERS A script only checks what someone thought to write down. As a Manual QA Tester, I work through a product the way a real user would, and then the way a careless one would: unexpected inputs, odd sequences, edge cases nobody scripted. This is where most first-release bugs are actually found, and it's the foundation every later automation effort builds on. ⚙️ CORE SERVICES ✅ Manual Testing - functional, regression, exploratory and smoke testing ✅ Manual QA Tester coverage - hands-on checks before every release ✅ Performance Testing - load, stress and response-time benchmarking ✅ Software QA process - test plans, test cases, checklists and structured bug reports ✅ API testing - REST and GraphQL, checked alongside the interface ✅ Cross-browser and cross-device testing ✅ AI & LLM product testing - output validation, regression and edge case coverage 🔍 HOW I APPROACH TESTING I check business logic against the requirements, try inputs nobody expected, and re-test every fix before it ships. Smoke tests on each new build show quickly whether it's worth testing further. Regression testing before release confirms yesterday's fixes didn't break today's features. Manual Testing done this way depends on judgment, not a script someone wrote last quarter. ⚡ WHEN LOAD BEHAVIOR MATTERS TOO Functional correctness isn't the whole story if the product falls over under real load. My Performance Testing covers response times under normal and peak traffic, how the system behaves as load increases, and where it breaks first. I report findings the same way I report functional bugs: reproducible, with numbers attached, so your team knows exactly what to fix. 🧪 QA AS A REPEATABLE PROCESS Good Software QA isn't just running tests, it's building a process your team can rely on. I write test plans that scope what gets covered and why, test cases your team can reuse, and checklists that catch what memory alone would miss. That structure is what makes manual coverage repeatable instead of ad hoc. 🐞 BUG REPORTS YOU CAN USE Every report has clear reproduction steps, severity and screenshots, so a developer can start fixing without a follow-up call. I work inside Jira, Linear or GitHub Issues, which means bringing in a Manual QA Tester doesn't mean introducing a new process. 🔧 WHEN CLIENTS BRING ME IN • Releases keep shipping with avoidable bugs: I add structured Manual Testing and smoke checks before every release. • Nobody has tested how the product holds up under load: I run Performance Testing and report where it breaks. • There's no Software QA process yet: I set up test plans, test cases and a bug-tracking workflow from scratch. • AI or LLM features behave unpredictably: I validate outputs and cover the edge cases. • Automated checks exist but miss real user behavior: I add manual coverage where it counts. 🏆 RESULTS • 3,500+ hours on one long-term SaaS engagement, trusted as an embedded QA partner • 88% of clients stay long-term, with five-star reviews on communication and reliability • Brought in as a Manual QA Tester across web, mobile and API products, with Manual Testing as the constant across every engagement 🧭 HOW A PROJECT STARTS First I review your product, requirements and any existing tests. Then I write a short test plan covering scope, environments and priority risk areas, including load conditions if Performance Testing is in scope. Testing follows in your sprint rhythm: I work as your Manual QA Tester on the riskiest flows first, then expand coverage as we go. Bugs are logged in your tracker as I find them, with a clear summary after each release. 👉 LET'S TALK Send me your staging URL, your release scope or a short description of your current QA setup, and I'll reply with a practical plan. Need a Manual QA Tester for the next release? Want help setting up a Software QA process from scratch? Or Performance Testing before a big launch? Write to me.