Quality Assurance Tester (Ai First)
Contractor+ · India
This listing has closed — view similar roles below.
- Hybrid
- Full-time
- $85,000 / year
- India
Job highlights
- Test web, iOS, Android, APIs, and AI workflows.
- Automate tests with frameworks like Playwright.
- Utilize AI tools for test generation and bug reproduction.
- Write clear, reproducible bug reports.
- Requires AI-native mindset and strong testing fundamentals.
About the role
About Us
Contractor+ is building the all-in-one operating system for contractors. CRM, estimating, payments, scheduling, communications, accounting, and AI-powered tools on a single platform.
We ship fast. We use modern tools. And we treat quality as a competitive advantage, not a phase gate.
The Role
We're looking for a QA Tester who uses AI as a daily multiplier, not someone who heard about it in a webinar. You'll test across web, iOS, Android, APIs, and AI-driven workflows. You'll use AI tools to write tests faster, catch regressions earlier, and reproduce bugs that would take others hours. You'll combine sharp manual testing instincts with automation skills and an AI-native workflow.
This is a hands-on, high-output role. You test. You automate. You ship quality.
What You'll Do
- Test: deeply and across platforms
- Execute manual, exploratory, and regression testing across web, iOS, and Android (real devices + emulators)
- Validate edge cases, failure states, permission boundaries, and race conditions
- Test API endpoints for correctness, error handling, and contract compliance
- Verify AI-driven features where outputs are non-deterministic and require judgment-based validation
- Automate: with purpose, not vanity metrics
- Write and maintain automated tests using frameworks like Playwright, Cypress, Appium, or Detox
- Build tests that run reliably in CI/CD pipelines, not just locally
- Prioritize automation where it reduces regression risk, not where it looks impressive
- Use AI: as a core workflow, not an add-on
- Use AI-powered tools (Copilot, Testim, Mabl, Katalon AI, Applitools Visual AI, or similar) for test generation, self-healing locators, visual regression, and bug reproduction
- Leverage LLMs (ChatGPT, Claude, etc.) for writing test cases from specs, generating test data, analyzing logs, and drafting bug reports
- Prompt-engineer testing workflows. Turn a user story into a structured test plan in minutes, not hours
- Stay current with emerging AI testing tools and bring new ones to the team when they solve real problems
- Report: with clarity engineers respect
- Write bug reports that are specific, reproducible, and include environment, steps, expected vs. actual, and severity
- No vague tickets. No "it doesn't work." Every report moves the fix forward.
Tools & Environment
You should be comfortable working with most of these:
- Automation: Playwright, Cypress, Appium, Detox, Selenium
- API Testing: Postman, REST clients, contract testing
- AI-Assisted QA: GitHub Copilot, Testim, Mabl, Applitools, Katalon AI, or equivalent tools for test generation, self-healing, and visual diffs
- LLMs for QA workflows: Using ChatGPT / Claude for test case creation, log analysis, data generation, and documentation
- CI/CD: GitHub Actions, Jenkins, or similar. You understand how tests fit into pipelines
- Bug Tracking: Jira, Linear, or equivalent. Used properly, not as a dumping ground
- Devices: Comfortable testing on real iOS/Android devices and emulators alongside browser-based testing
Non-Negotiables
- AI-native mindset. You already use AI tools daily in your testing work. This isn't aspirational, it's how you operate.
- Strong manual testing fundamentals. AI amplifies good testers. It doesn't replace bad ones.
- Automation skills. You can write, debug, and maintain test scripts, not just record and playback.
- Clear written communication. Your bug reports, test plans, and status updates are precise and useful.
- Ownership. You don't wait to be told what to test. You see a risk, you cover it.
- Willingness to block a release. If it's not ready, you say so. Clearly and with evidence.
What Doesn't Work Here
- Testers who only run someone else's test cases without thinking
- "Automated 500 tests" with no connection to actual risk coverage
- Using AI tools superficially. Generating tests you don't review or understand
- Vague bug reports that waste engineering time
- Waiting for perfect specs before testing anything
What "Great" Looks Like
- You catch bugs in staging that would have cost users real time and money
- Engineers trust your reports because they're always reproducible
- Your automated suite runs in CI and actually catches regressions
- You use AI to do in 2 hours what used to take a full day
- You bring a new AI tool or technique to the team every quarter that sticks
Who This Is For
- QA testers with 2-3 years of experience who've outgrown checkbox testing
- People who already use AI in their daily QA workflow and want a team that values that
- Testers who are equally comfortable writing a Playwright script and doing hands-on exploratory testing
- Builders who care about the product, not just the test pass rate
We're not hiring a test executor. We're hiring a quality-obsessed tester who uses AI to punch above their weight.
Key skills/competency
- Quality Assurance
- AI Testing
- Test Automation
- Manual Testing
- API Testing
- Playwright
- Cypress
- CI/CD
- Bug Tracking
- LLMs
Skills & topics
- Quality Assurance
- QA Tester
- AI Testing
- Automation Tester
- Software Tester
- Test Automation
- Manual Testing
- API Testing
- Playwright
- Cypress
- Appium
- Detox
- Selenium
- Postman
- GitHub Copilot
- Testim
- Mabl
- Applitools
- Katalon AI
- ChatGPT
- Claude
- CI/CD
- Jira
- Linear
- iOS Testing
- Android Testing
- Web Testing
- Remote
How to get hired
- Customize your resume: Highlight your AI-native approach and automation skills. Quantify achievements in testing and AI tool usage.
- Tailor your application: Emphasize your experience with specific tools like Playwright, Cypress, and LLMs. Showcase how you've used AI to improve quality.
- Prepare for technical questions: Be ready to discuss your experience with manual, automated, and AI-assisted testing strategies.
- Demonstrate your AI mindset: Articulate how you integrate AI tools daily for efficiency and effectiveness in QA.
- Show ownership and communication: Provide examples of how you've proactively identified risks and reported bugs clearly.
Technical preparation
Master Playwright or Cypress for web automation.,Practice API testing with Postman or similar tools.,Learn prompt engineering for AI test generation.,Understand CI/CD pipeline integration for tests.
Behavioral questions
Describe a complex bug you found and fixed.,How do you handle testing non-deterministic AI features?,Share an instance where you blocked a release.,How do you prioritize automation efforts?
Frequently asked questions
- What specific AI tools are essential for the QA Tester role at Contractor+?
- While familiarity with tools like GitHub Copilot, Testim, Mabl, Applitools, Katalon AI, and LLMs (ChatGPT, Claude) is highly beneficial, the core requirement is an AI-native mindset. This means you should already be integrating AI into your daily testing workflows, regardless of the specific tool. We value adaptability and a proactive approach to learning and applying new AI testing technologies.
- How important is manual testing experience for this AI-First QA role at Contractor+?
- Strong manual testing fundamentals are non-negotiable. AI tools are seen as multipliers for skilled testers, not replacements for them. You'll need to execute manual, exploratory, and regression testing across various platforms, validating complex scenarios and edge cases. Your ability to combine sharp manual instincts with automation and AI will be key.
- What kind of automation experience is expected for this QA Tester position?
- We expect candidates to have solid automation skills, including the ability to write, debug, and maintain test scripts. Experience with frameworks like Playwright, Cypress, Appium, or Detox is highly valued. The focus is on writing reliable tests that run in CI/CD pipelines and effectively reduce regression risk, rather than vanity metrics.
- How does Contractor+ utilize AI in its QA processes?
- Contractor+ integrates AI as a core workflow, not an add-on. This includes using AI for test generation, self-healing locators, visual regression testing, bug reproduction, writing test cases from specifications, generating test data, analyzing logs, and drafting bug reports. We encourage prompt-engineering of testing workflows and staying current with emerging AI testing tools.
- What distinguishes a 'great' QA Tester at Contractor+?
- A great QA Tester at Contractor+ catches critical bugs before they impact users, earns engineer trust through reproducible reports, maintains a robust automated suite in CI, significantly reduces testing time using AI, and proactively brings new, impactful AI tools or techniques to the team regularly.
- What is the expected experience level for the QA Tester role at Contractor+?
- We are looking for QA testers with 2-3 years of experience. Specifically, we seek individuals who have moved beyond basic 'checkbox' testing and are looking for a role where they can leverage AI to enhance their testing capabilities and contribute to a high-quality product.
- Can you describe the work environment and culture at Contractor+?
- Contractor+ fosters a fast-paced environment where quality is a competitive advantage. We use modern tools and encourage a culture of ownership and clear communication. Testers are expected to be proactive, willing to block releases if quality is compromised, and contribute to continuous improvement, especially with AI integration.