
Manual QA Tester
Welo Data · Posted 1 month ago
- Delhi, India (Remote)
- Remote
- Contract
- USD 8,320 - USD 8,320
About the role
Job Overview
We are looking for a detail-oriented Manual QA Tester to execute frontend test operations with precision and consistency. This role sits at the client-facing UI layer of a complex web onboarding workflow and is responsible for validating form behavior, field-level validation logic, and error handling across browsers — all while following defined test runbooks and maintaining accurate, well-documented evidence of every defect or error state encountered. The primary assignment is to execute structured walkthroughs across representative onboarding personas and document the observed frontend constraints that will become inputs to downstream FSM/state-model analysis and evidence set.
The ideal candidate thrives on process discipline and has a sharp eye for visual and functional inconsistencies in data-entry-heavy web applications.
Project Details
- Title: Manual QA Tester - (India)
- Rate: $3.5/hr
- Start Date: 19th October
- Duration: 3 Weeks
- Commitment: 40 Hours per Week
- Location: India (Remote)
- Job Type: Freelance (with the possibility of full time employment based on performance and project needs in all opportunity)
Responsibilities
- Execute test cases strictly in accordance with documented test runbooks, ensuring no steps are skipped or altered without approval
- Perform cross-browser UI testing to validate layout, functionality, and boundary conditions across supported browsers and devices
- Validate client-side form field rules such as character-length limits, format/pattern (regex-style) validation, and required-field enforcement across form inputs (e.g., text fields, dropdowns, radio buttons)
- Verify UI state behavior driven by validation outcomes — for example, error banners appearing on malformed input, or action buttons remaining disabled until all fields pass validation
- Identify, capture, and log DOM-level screenshots and error states with clear, reproducible documentation
- Track and report test execution status, flagging deviations from expected runbook outcomes
- Maintain organized records of test evidence (screenshots, logs, error traces) for defect tracking and audit purposes
- Escalate boundary and edge-case UI failures to senior QA or development teams with sufficient supporting detail
- Collaborate with QA leads to refine and update test runbooks based on recurring issues or coverage gaps
- Execute structured walkthroughs across the defined onboarding personas.
- Document observed UI constraints, field limits, regex/pattern behaviour, conditional states, error states, and decision points.
- Consolidate findings into a structured frontend constraint dictionary and evidence set for downstream FSM validation.
- Maintain traceability between each observed behaviour, persona, test step, and captured evidence.
Required Qualifications
- Proven experience in manual QA testing, preferably in a frontend/UI-focused environment involving multi-field forms
- Demonstrated ability to strictly follow and execute structured test runbooks
- Hands-on experience with cross-browser testing tools and techniques (e.g., BrowserStack, native browser dev tools)
- Working knowledge of DOM structure and browser developer tools for inspecting and capturing error states
- Familiarity with client-side validation concepts (field length limits, format/regex validation, conditional UI states)
- Strong attention to detail and disciplined documentation habits
- Basic understanding of UI/UX boundary conditions and how they manifest as defects
- Good written communication skills for clear, reproducible bug reporting
- Ability to produce structured evidence that can be reviewed and reused by senior QA/SDET resources.
- Experience testing complex onboarding, registration, account-creation, or other multi-step workflows is preferred.
Skills
Quark9 guide
How to land this Manual QA Tester role
Our notes for applicants, based on how QA and testing hiring usually works and on 3 similar open jobs on Quark9.
Resume checklist for this job
Most companies screen resumes with an ATS before a person reads them. Make sure each skill you genuinely have appears in your resume in the same words the job uses.
Must have
- manual QA testing
- cross‑browser testing
- BrowserStack
- browser dev tools
- client‑side validation
- documentation
- bug reporting
- Name the frameworks and languages you automated with, not just "automation testing"
- Give numbers: test coverage added, regression time cut, defects caught before release
- Mention CI tools (Jenkins, GitHub Actions) if your tests ran in a pipeline
How QA and testing interviews usually run
- A screening call on your testing background and the tools you have used
- A practical round: write test cases for a feature, or find bugs in a sample app
- An automation round on your framework of choice (Selenium, Cypress, Playwright, Appium)
- A final discussion with the engineering manager on process and release quality
Questions worth preparing
- How would you test a login page? Walk through functional, negative and security cases.
- What is the difference between regression, smoke and sanity testing, and when do you run each?
- How do you decide what to automate and what to keep manual?
- Tell us about a bug that reached production. What did you change afterwards?
Every company runs its own process, so treat this as a likely shape, not a promise. Practise a mock interview on Quark9 and get scored feedback before the real one.