Daria Gekht
LinkedIn
QA & Automation for international product teams
I help fast-moving product teams reduce release risk through manual QA,
exploratory testing, regression planning, clear bug reporting, and
practical automation strategy. I focus on critical flows, reproducible issues,
release visibility, and automation
decisions that are worth the maintenance cost.
Available for freelance projects, contract work, and selected full-time
QA / Automation roles with international product teams.
Positioning
I combine manual QA, practical automation experience, product thinking, and software
development experience across game studios, SaaS, AdTech, web products, and complex
product workflows.
That mix is valuable for teams because I can test the product,
understand engineering constraints, and help turn release risk into clearer priorities
for product and engineering.
Services
Focused 3-5 business day pre-release testing for critical flows, reproducible issues, screenshots/video notes, and a clear release risk summary.
Includes tested areas, open risks, blocker/critical issues, known limitations, and QA release recommendation.
Ongoing weekly or monthly QA support for product teams that need release testing, regression planning, bug investigation, product feedback, and QA documentation without hiring a full-time QA engineer.
A lean review of your QA workflow, release risks, and next-step priorities. Best for small teams that want a quick outside view.
A deeper review of your QA process, test coverage, bug workflow, release readiness, and tooling, with a clear 30-day improvement plan.
Inputs can include Jira or Linear tickets, test cases, release process, CI/CD results, bug reports, product flows, and the automation suite if one exists.
I review product flows, current test coverage, CI/CD setup, release frequency, and bug history to identify which checks are worth automating, which should stay manual, and which belong at API, integration, or unit level instead of fragile UI automation.
I recommend automation when a flow is stable, repeated often, business-critical, technically automatable, expensive to test manually, and suitable for reliable test data/setup.
Looking for full-time QA / Automation support? These services also reflect the kind of
support I can bring inside product teams:
release risk visibility, clear bug reporting, practical automation strategy, and
collaboration with product and engineering.
Pricing
Final scope depends on product complexity, platforms, release urgency, and access needed, but these anchors help teams quickly understand the usual engagement size.
A lean review of your QA workflow, release risks, and next-step priorities. Best for small teams that want a quick outside view.
A deeper review of your QA process, test coverage, bug workflow, release readiness, and tooling, with a clear 30-day improvement plan.
Coverage map, automation candidates, and practical automation priorities.
Focused 3-5 business day pre-release testing for critical flows, reproducible issues, screenshots/video notes, and a clear release risk summary.
Ongoing weekly QA support inside product teams.
Need a custom scope? I can quote a narrower review, a release-specific review, or a longer team engagement after a short discovery call.
Bring me in when
My QA approach
I start with product risk, not random test cases. I identify critical flows, map
coverage, test the product manually and technically,
report reproducible issues, and
recommend automation only where it creates reliable value.
Identify critical user journeys, business risks, integrations, permissions, payments, onboarding, content, analytics, and platform-specific risks.
Define what needs smoke, regression, exploratory, compatibility, API, data, or automation coverage.
Run focused manual, exploratory, regression, API, and release testing. Report reproducible issues with severity, priority, environment, evidence, expected/actual results, and business impact.
Deliver a release summary with known risks, blockers, and QA recommendation. Identify stable, repeated, high-value flows worth automating.
My bug reports include environment, steps to reproduce, expected result, actual result, severity, priority, evidence, and business impact.
I recommend automation when a flow is stable, repeated often, business-critical, expensive to test manually, and suitable for reliable test data/setup. I avoid automating unstable UI flows too early and may recommend API or integration checks instead of fragile end-to-end UI tests.
Selected impact
At Minute Media, I created a clearer QA process, improved test coverage visibility, exposed UX and functional mismatches, and helped product and engineering teams make better release decisions. As part of this process, approximately 95% of new and reported issues were identified before production release.
At MY.GAMES, I participated in the creation of QA automation infrastructure, Unity tools, CI-integrated checks, build-machine workflows, and documentation that improved release validation across multiple projects. This contributed to a 30% improvement in QA process quality and automation coverage.
Tested frontend/backend flows, wrote Xray test plans and test cases, automated with Testim, used SOQL/APEX, and connected CI/CD reports to Slack and Gmail.
Worked as a .NET developer with frontend/backend releases, Jenkins, MS SQL Server, API testing with Postman, and client support.
AI-assisted workflow
I use AI tools to speed up research, documentation drafts, QA checklist creation,
UX copy iteration, and implementation support.
Final decisions, client deliverables,
prioritization, and QA judgment remain human-reviewed.
Best fit
I work well with teams that already move fast, but need someone to slow down in the right places: check the risky flows, ask product questions, and make release quality easier to see.
I am strongest when the work includes manual QA, release testing, regression planning, bug investigation, product feedback, and identifying what is actually worth automating before the team invests time in tests that are unstable, low-value, or expensive to maintain.
The best match is a game studio, SaaS, AdTech, or web product team that wants QA judgment, product feedback, and clear release risk visibility, not only checklist execution.
Open to full-time and contract roles
Alongside freelance QA projects, I'm open to selected full-time or long-term contract opportunities with international product teams.
Best-fit roles include QA Engineer, QA Automation Engineer, Software QA Engineer,
Product-minded QA Engineer, Release QA Engineer, and
selected QA Lead or SDET-adjacent roles where quality work is connected to release confidence, practical automation
strategy, and product risk.
Available for freelance projects, contract work, and selected roles
I'm open to selected full-time QA Engineer,
QA Automation Engineer, Software QA Engineer,
Release QA Engineer, and product-minded QA roles
in international product teams.
I'm available for release readiness reviews, QA process audits, automation readiness reviews, and fractional QA support.
Contact me about a projectExperience
I am available for international release QA, product quality audits, QA team support, automation readiness reviews, and test process setup for game studios, SaaS, AdTech, and web products.
I built a standardized QA process for a global sports and culture technology company, improved delivery quality, exposed design mismatches, reported UX and functional issues, and made QA reporting clearer for product and engineering teams.
I tested a Salesforce-based insurance platform, wrote test plans and cases in Xray, managed Jira issues, automated frontend and backend testing with Testim, SOQL, and APEX, and integrated CI/CD reports with Slack and Gmail notifications.
I supported an early HR tech product with competitive market analysis, monetization model development, and structured competitor research in Miro for data-driven product decisions.
I worked on Guild of Heroes, Storyngton Hall, and Gym Mania. I contributed to automation infrastructure, Unity tools, CI-integrated autotests, build machines, TeamCity and BuildBot workers, Firebase and Google Analytics result analysis, Android Test Farm module integration, release risk assessment, and manual QA for large game features.
I fixed bugs, developed product features, analyzed code, delivered frontend and backend releases through Jenkins, supported clients, corrected data in MS SQL Server, and tested APIs with Postman.
Education
Penza State University
LinkedIn Learning
View certificateIBM / Coursera
View certificateIBM / Coursera
View certificateIBM / Coursera
View certificateIBM / Coursera
View certificateUnity Technologies / Credly
View badgeUnity Technologies / Credly
View badge