QA / DEV TESTING
I break flows. So your users don’t have to.
Manual QA, game testing, software testing, bug reproduction, UI/UX feedback, regression checks, and technical test support for websites, apps, indie games, MVPs, WordPress builds, and digital products that need sharper quality before users, clients, or investors see them.
I bring 3+ years of manual testing experience across game testing and software testing, with a strong focus on clean bug reports, practical reproduction steps, user flow analysis, UI/UX friction, security awareness, automation thinking, and fast feedback that developers can actually use.
Not “I clicked around and found some bugs.”
I test flows, document defects, reproduce edge cases, question assumptions, and look at the product like a user, tester, developer, and frustrated customer at the same time.
WHY THIS SERVICE EXISTS
Because “it works on my machine” is not a release strategy.
A product can compile, deploy, load, and still fail the user. Broken forms, unclear states, weak error messages, bad responsiveness, confusing onboarding, missing validation, edge-case crashes, inconsistent UI, and silent failures can destroy trust faster than a missing feature.
My job is to hunt the friction before it becomes public. I test with structure: expected result, actual result, reproduction steps, severity, environment, screenshots or recordings when needed, and a clear explanation of why the issue matters.
I value time and efficiency. That means I charge for speed, clarity, and useful output — not for wasting hours inside a messy checklist that nobody reads.
WHAT I ACTUALLY DO
Technical QA with developer-readable output.
I do not sell vague feedback. I look for defects, risk, friction, broken assumptions, and weak product behavior. The output should help you decide what to fix, what to delay, and what might hurt users first.
Bug reproduction
I isolate issues, retry flows, test different paths, document the environment, and write reproduction steps that developers can follow without guessing.
User flow testing
Onboarding, registration, login, checkout, booking, contact forms, account areas, dashboards, settings, empty states, and weird user behavior.
UI/UX friction checks
Confusing labels, weak CTA hierarchy, inconsistent spacing, unclear states, bad mobile behavior, missing feedback, and moments where users hesitate.
Regression testing
After a fix, I verify whether the original bug is gone and whether the fix broke nearby behavior. No “fixed” label until it actually behaves.
Automation mindset
I am pushing into automation testing and DevOps. Where it makes sense, I identify repeatable checks that could later become automated smoke or regression tests.
Security-aware testing
Not penetration testing, but I look for risky behavior: exposed data, weak validation, suspicious flows, unsafe assumptions, account confusion, and careless user handling.
MY QA PROFILE
Manual tester now. Automation-minded tester next.
I have 3+ years of manual testing experience and a background that connects game testing, software testing, hardware/software validation, bug reporting, Linux-based environments, databases, and product thinking.
I am preparing for ISTQB certification and actively moving toward automation testing, DevOps workflows, better test strategy, and more technical QA. I am not pretending to be a senior SDET today. I am telling you exactly where I am: strong manual QA foundation, technical curiosity, and a serious direction.
Game QA eye
I look for broken mechanics, player friction, UI confusion, progression blockers, edge cases, inconsistent feedback, and bugs that hurt immersion.
Software QA discipline
I care about reproducibility, severity, regression, environment notes, acceptance criteria, and reports that reduce developer back-and-forth.
Technical curiosity
I am interested in automation, CI/CD, DevOps, testing pipelines, security basics, and smarter ways to catch repeated failures faster.
Quality obsession
I do not only ask “does it work?” I ask “does it make sense, can it fail, can users recover, and would I trust this product?”
SERVICE OPTIONS
Priced for efficient QA, not cheap clicking.
I charge slightly more than basic casual testing because speed and quality matter. You are not paying me to randomly click buttons. You are paying for structured attention, clear reports, technical curiosity, and less wasted developer time.
Game testing, release QA, repeated regression passes, automation planning, code cleanup, and multi-flow testing should be scoped properly before booking. That keeps the work sharp and fair.
Best first step if you are not sure what kind of testing your product needs.
Start FreeFast external check for obvious bugs, broken flows, weak UX, bad mobile behavior, or launch blockers.
Book ScanOne focused flow, feature, page, form, checkout, booking path, onboarding path, or game mechanic.
Book SessionBetter for multiple flows, bug reproduction, UI/UX notes, responsive checks, and deeper triage.
Book SessionUseful for a compact but serious pass across core flows, regression checks, and report preparation.
Book SessionRecommended before release. Structured findings, severity, screenshots, reproduction steps, and priorities.
Request QuoteGameplay bugs, UI confusion, onboarding, progression, player friction, softlocks, crashes, and feedback.
Request QuoteSmall front-end bugs, WordPress issues, JavaScript problems, layout fixes, and clear technical cleanup.
Book HelpFor studios, dev teams, SaaS products, MVPs, agencies, repeated testing, or release support.
Request QuoteAAA-LEVEL MINDSET, FREELANCE ACCESSIBILITY
The same discipline smaller teams usually postpone.
AAA studios like Ubisoft, EA, Rockstar, and other large publishers can afford specialized QA pipelines, dedicated test teams, build verification, compliance checks, regression cycles, and release pressure management. Smaller teams often cannot.
That does not mean smaller teams should ship blind. I bring a practical version of that mindset: structured manual testing, clear documentation, bug severity, player/user experience, regression awareness, and honest prioritization.
- For indie games: I test like someone trying to break the player experience, not like someone trying to “be nice.”
- For web apps: I follow the user path, then intentionally step outside the happy path.
- For WordPress/WooCommerce: I check flows, responsiveness, forms, bookings, account states, and obvious friction.
- For MVPs: I separate launch blockers from nice-to-have polish so you do not drown in feedback.
- For dev teams: I write reports that should reduce time lost in back-and-forth clarification.
WHAT I CAN TEST
Manual QA across web, software, and games.
I focus on behavior, risk, flow, clarity, and reproducibility. The exact test scope depends on what you built and what you are afraid might fail.
Websites & landing pages
Navigation, responsive behavior, CTAs, forms, broken links, layout issues, content clarity, mobile friction, and conversion blockers.
Apps & MVPs
Onboarding, login, account states, empty states, validation, error handling, core flows, edge cases, and user confusion points.
Games & prototypes
Controls, softlocks, UI, progression, tutorials, collisions, save/load behavior, performance symptoms, player friction, and game-breaking bugs.
WooCommerce & bookings
Product pages, service selection, cart, checkout, account pages, emails, payment confusion, booking flow, and invoice/order friction.
Basic API / data sanity
Not full backend QA yet, but I can check obvious response issues, bad states, validation problems, broken assumptions, and data mismatch symptoms.
Automation candidates
I can identify repeatable checks that may later become smoke tests, regression tests, or automated checks in a CI/CD workflow.
OUTPUT YOU CAN USE
Reports that make developers breathe easier.
A useful bug report is not “this is broken.” It is a small technical investigation that helps someone reproduce, understand, prioritize, and fix the problem.
Reproduction steps
Clear steps, expected result, actual result, environment, screenshots, recordings, and notes when the bug is inconsistent.
Severity & priority
Crash, blocker, major, minor, polish, UX friction, security concern, regression risk, or “fix later but do not ignore.”
Technical notes
Browser/device context, account state, inputs used, suspicious patterns, and technical hints when I can identify likely cause areas.
UI/UX observations
Confusing wording, weak visual hierarchy, missing feedback, unclear buttons, user hesitation points, and trust-breaking micro-friction.
Regression checklist
When useful, I suggest what should be retested after a fix so the same area does not break again.
Fix suggestions
If the issue is clear enough, I can suggest practical fixes or next steps instead of only reporting the problem.
FOR TECH PEOPLE
You know that bug you hope nobody notices?
The form that fails silently. The checkout path nobody tested on mobile. The tutorial step that softlocks if the player does things out of order. The button that looks clickable but is not. The modal that traps focus. The user state you forgot after logout. The “temporary” validation hole that stayed in production.
That is the stuff I like finding. Not because I want to be annoying — because quality is cheaper before damage.
Happy path
First I verify the intended flow. Then I stop behaving like an ideal user.
Edge path
Back buttons, refreshes, bad inputs, repeated clicks, weird timing, missing data, and state confusion.
Break path
I look for the moment where the product stops guiding the user and starts blaming them silently.
Fix path
The best QA output makes the next developer action obvious.
LIMITS & BOUNDARIES
Serious testing needs permission and scope.
I can help with manual QA, bug reproduction, UI/UX feedback, small fixes, and technical testing support. But I do not test systems without permission, and I do not sell hacking, bypassing, or illegal access.
- I only test products, builds, websites, apps, or systems you own or have permission to test.
- This is not penetration testing, exploit development, account bypassing, or cybersecurity attack work.
- I cannot guarantee that every possible bug will be found.
- Bug fixing depends on access, code quality, stack, scope, and whether the issue is realistically fixable.
- Large codebases, complex apps, games, or company projects should be quoted before starting.
- For sensitive data, production systems, and user accounts, access rules must be agreed clearly first.
FOR STUDIOS, DEVELOPERS & COMPANIES
Need extra QA eyes before release?
I am open to working with indie developers, small studios, web developers, agencies, startups, SaaS teams, and larger companies that need fast manual QA support, release checks, regression passes, game testing, or structured bug reports.
- Indie game developers can request playtest QA, onboarding feedback, bug reports, and player-experience notes.
- Web developers can request pre-handover QA, responsive checks, form testing, and client-facing bug reports.
- Startups and MVP teams can request launch-readiness testing and prioritised risk reports.
- Studios and companies can request custom QA support, repeated test cycles, or scoped release support.
- AAA studios and larger teams can contact me for contract-style manual QA support, test execution, or junior-to-mid QA capacity.
READY TO FIND WHAT BREAKS?
Send me the flow you are afraid to test.
Tell me what you built, what stage it is in, what worries you, and what kind of user behavior you want tested. I will recommend the simplest useful QA step before you pay for the wrong kind of help.