Manual QA for web and mobile. Clear bug reports, real edge cases, and the weird bugs that only show up right before launch

Hey, I'm Saba. I test websites and apps for a living, and I take it pretty seriously.

I'm based in Tbilisi. Before QA I worked in live broadcast and hands-on IT, so I'm used to pressure, detail, and products that have to work when it counts. That stuck with me. When something feels off, I dig until I can reproduce it cleanly.

What I care about is the weird stuff. The freeze that only happens on submit. The OTP that spam-fires. The price that rounds wrong after a fee. The session that leaks between accounts. The chatbot that invents inventory. I've written 65+ public bug reports across travel, marketplace, AI chat, and security products, so you can see how I work before we start.

A few real examples from that work:
- Travel and booking app: 83 test cases. Caught mobile freezes, OTP and token failures, and broken web auth flows.
- Gardening marketplace: OAuth and session issues, plus pricing math that quietly dropped fees or rounded wrong.
- AI e-commerce chat: WebSocket failures, search filter overwrites, and RAG answers that drifted from the catalog.
- Security platform: AI analysis failures and a cross-account session leak. The kind of bug you really want found early.

Day to day I do manual testing on web and mobile, API checks in Postman, and bug reports developers can actually fix from: severity, steps, expected vs actual, screenshots, environment. Not vague "something broke" notes.

I'm not the person who clicks around for five minutes and says "looks fine." I slow down on the edges. Empty states. Bad input. Race conditions. Permissions. Payments-adjacent math. The paths users take when they are tired, impatient, or doing something unexpected.

If you're about to launch, demo, or hand a build to a client and you want another pair of sharp eyes on it, message me. Tell me what the app does, which flows matter most, and when you need it. We'll figure out the scope from there. Happy to start small with a smoke pass or go deeper when the release matters.

Tools I use: Postman, Jira, ClickUp, Chrome DevTools, GitHub, Maestro. Growing into Playwright as I go. English is fluent. Georgian is native.

Work Terms

I'm on GMT+4 and flexible. Happy to overlap with EU days and US mornings when a release needs it. If you have a hard launch window, say so up front and I'll plan around it.

Prefer chatting here on Guru. Keep it simple: send the link or build, the main flows, any test accounts or sandbox keys, and your deadline. Screenshots of Figma or expected behavior help when the UI is new.

Quick smoke checks usually take 1-2 days. A fuller pass with functional coverage and API checks is typically 3-5 days depending on size. Bigger launch reviews take longer, and I'll tell you that before we start.

SafePay works best for me. Milestone or hourly, whichever fits the job. I like clear scope more than vague open-ended hours.

If something in a bug report isn't clear, I'll clarify. Re-testing after fixes is easy to add once we know what changed.

NDA is fine. A lot of client work stays private. I can share redacted samples and my process when that helps you decide if we're a fit.