> Markdown version of [/jobs/ext/1343363-qa-engineer-manual-automation](https://www.wearedevelopers.com/jobs/ext/1343363-qa-engineer-manual-automation). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # QA Engineer (Manual / Automation) - **Company:** GLUZDOV.COM, INC. - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** .NET Framework, Test Suite, Application Programming Interfaces (APIs), Artificial Intelligence, Business Logic, Automation of Tests, Microsoft Azure, C Sharp (Programming Language), Software as a Service, Continuous Integration, Github, Strategies of Testing, TypeScript, Integration Tests, Bug Reporting, Playwright, Webhooks, Api Management - **Published:** July 19, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=bad89c053a407ce3 ## About the Role * Balanced QA mindset - confident in both manual and automation testing, with automation viewed as a natural extension of strong testing fundamentals * Comfortable working independently and taking increasing ownership of quality * Business-value focused - tests against user value and real requirements, not just acceptance criteria as written * Self-managed under uneven load - handles a fractional, back-loaded schedule without needing constant oversight, * Strong manual and exploratory testing skills, complemented by hands-on automation experience * Playwright + TypeScript, or a modern equivalent with willingness to standardize on Playwright * API testing experience (REST, webhooks) * Uses AI tools as part of daily QA work and is interested in adopting new approaches * Understands business requirements and tests for user value, not just acceptance criteria * Experience working both independently and as part of an established QA team, with an understanding of what good QA processes look like * English B2 or higher - client-facing UAT, written bug reports and documentation Nice-to-Have * C# test code experience (the first project is .NET) * CI/CD test integration (GitHub Actions / Azure DevOps) * Payment or fintech domain testing experience * Performance or accessibility testing * Interest in helping establish QA practices and standards ## Description This role exists because the consultancy has no dedicated QA function yet. Its first job is to make a specific, high-stakes rebuild safe: a VC-backed, pre-launch HR/benefits SaaS product is going from prototype to commercial launch in about six months, and every change to the business logic the client trusts needs evidence that nothing broke. The QA Engineer is responsible for building confidence in every release through effective testing, automation, and a growing regression strategy. This role offers the opportunity to gradually take ownership of QA processes and help shape the department's QA practice over time., Regression strategy established and continuously improved - a defined, evidence-based regression approach is running for the first project, covering the trusted business logic being restructured Automation integrated into CI - Playwright + TypeScript test automation is built and running as part of the CI pipeline Payment surface covered - API and webhook testing covers Stripe ACH and credit-card flows - payment states, failures, and reconciliation Release readiness trusted - the team and client rely on this person's quality gates and reporting to know when something is ready to ship QA practice extended - groundwork is laid to bring QA practice to other projects across the department's portfolio, beyond the first assignment, Regression & Test Strategy * Help define and continuously improve the regression strategy. * Test planning from business requirements, not just tickets * Flag untestable requirements to the PM and Tech Lead before they become untestable code Automation & API Testing * Build test automation in Playwright + TypeScript, integrated into CI * Drive API and webhook testing on the highest-risk surface: payment integrations Manual & Exploratory Testing * Run persona-based manual and exploratory testing across three user portals * Cover payment flows and edge cases automation won't catch * Support client UAT sessions directly Quality Ownership & Practice-Building * Help establish quality gates and provide clear release readiness reporting * Use AI throughout testing work, and help decide which AI QA tooling the department adopts * Contribute to growing QA practices across the department as new projects are onboarded, This role is ideal for someone who enjoys taking ownership and wants to grow beyond hands-on testing. You'll have the opportunity to shape QA practices, gradually expand your responsibilities, and grow together with the department as more projects come under QA. You'll join as the first QA on a funded product preparing for commercial launch, where you'll help establish automation, improve the regression strategy, and build confidence in every release. As the department grows, you'll have the opportunity to broaden your impact across multiple projects and play an active role in shaping how QA is done within the consultancy. The workload is intentionally flexible, making this role a good fit for someone balancing other engagements or looking for a gradual path toward a larger role. We're also upfront that there is no existing test suite or documentation to rely on - if building structure from an imperfect starting point sounds motivating rather than intimidating, you'll likely enjoy the challenge. ## Related Videos - [Beyond Webhooks: The Future of Scalable API Event Delivery](https://www.wearedevelopers.com/videos/100312-beyond-webhooks-the-future-of-scalable-api-event-delivery) - [How To Test A Ball of Mud](https://www.wearedevelopers.com/videos/173-how-to-test-a-ball-of-mud) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [How I Built QA from Scratch in a Scaling Startup - no fluff real life story](https://www.wearedevelopers.com/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story) - [You don't need to write the code. You need to become a verification architect and prove it's correct](https://www.wearedevelopers.com/videos/100023-you-don-t-need-to-write-the-code-you-need-to-become-a-verification-architect-and-prove-it-s-correct) - [Dirty Tests And How To Clean Them](https://www.wearedevelopers.com/videos/515-dirty-tests-and-how-to-clean-them) ## Related Articles - [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 119 - ❤️ === ❤️](https://www.wearedevelopers.com/magazine/454-dev-digest-119) - [Integration And E2E Testing: Are They Complementary or Interchangeable?](https://www.wearedevelopers.com/magazine/86-integration-and-e2e-testing-are-they-complementary-or-interchangeable) - [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)