QA Automation Engineer - Web + API + Mobile

Qapitol QAS Private Limited; Bengaluru; Presencial; INR 900.000 - 1.500.000; Jornada completa

Descripción de la vacante

Qapitol QAS Private Limited in Bengaluru onsite is seeking an AI - Full Stack Manual QA Engineer to design and maintain a single, reusable automation framework spanning web, API and mobile. The role focuses on reliable automation that supports rapid releases and strong test coverage.

The ideal candidate has 3–5 years of hands‑on automation experience, can implement framework patterns, and collaborate in a CI/CD environment to ensure quick and accurate feedback on builds.

Formación

• 3–5 years of QA automation experience.
• Experience building a single reusable framework for web, API and mobile.
• Proficiency with Selenium/Playwright/Cypress; REST Assured/Karate; Appium.

Responsabilidades

• Design and maintain a single, reusable automation framework spanning web, API and mobile.
• Write and maintain automated test scripts for web, API and mobile and integrate with CI/CD.
• Emphasise Page Object Model, data‑driven patterns, clean reporting and logging.

Descripción del empleo

AI - Full Stack Manual QA Engineer

• Website team: Professional Services BU
• Location on website: Bengaluru onsite
• Suggested Keka location: Bengaluru (Onsite)
• Job type: Full Time
• Experience: 3 to 5 years

You build the automation that lets a team ship with confidence instead of crossing their fingers - across web, API and mobile, in one coherent framework.

Manual regression doesn't scale, and stitching together three separate automation stacks for web, API and mobile doesn't either. This role is for an engineer who can design and maintain a single, reusable automation framework spanning all three, so a release can be regression-tested in hours, not days.

You'll write and maintain automated test scripts using Selenium/Playwright/Cypress for web, REST Assured/Karate for API, and Appium for mobile, wiring all of it into CI/CD so failures surface the moment they're introduced. Framework design matters as much as script-writing here - Page Object Model, data-driven patterns, clean reporting and logging - because the framework has to outlast any single release.

Who thrives here

Engineers who'd rather build the thing that catches ten future bugs than manually catch one today. You think in frameworks and reusable components, you're comfortable owning a codebase rather than just scripts, and you like the discipline of making automation reliable enough that people actually trust a red build.