Contractor Position: Playwright Test Automation Engineer
6 Month Contract
Looking for 2 resources
Position Overview
We are seeking an experienced Test Automation Engineer with strong Playwright expertise
to jumpstart our automated testing initiative. This includes converting existing manual tests
to automated tests, implementing CI/CD integration with GitLab, setting up test result
reporting with screenshot evidence capture, and providing knowledge transfer to our QA
team.
Project Scope
Core Deliverables
1. Test Automation Framework Setup
Review and optimize our set up of our Playwright test automation framework
Establish project structure, naming conventions, and best practices
Review and Configure test environments (development, staging, production-like)
Implement page object model or other maintainable design patterns
Set up test data management strategy
Configure parallel test execution for faster feedback
2. Manual to Automated Test Conversion
Review existing manual test cases and test documentation
Prioritize tests for automation (focus on regression and release testing)
Convert manual test cases into automated Playwright tests
Implement test scenarios for critical user workflows
Create reusable test components and utilities
3. Evidence Capture s Reporting
Implement automatic screenshot capture at key test steps
Capture screenshots on test failures for debugging
Set up video recording for failed tests (optional but recommended)
Integrate test results with test automation dashboard
Configure test result artifacts for easy access
Ensure compliance with objective evidence requirements
4. GitLab CI/CD Integration
Create GitLab CI/CD pipeline configuration for test execution
Enable on-demand test execution via GitLab UI
Configure scheduled test runs (nightly regression, pre-release)
Set up pipeline to run on merge requests (optional)
Implement test result publishing to GitLab
Configure notifications for test failures
Optimize pipeline execution time
5. Dashboard Integration s Reporting
Integrate test results with existing test automation dashboard
Configure dashboard to display:
o Test pass/fail rates
o Execution trends over time
o Failed test screenshots
o Test execution duration
Set up test result history and analytics
Create clear test result summaries for stakeholders
6. Documentation s Knowledge Transfer
Document test automation framework architecture
Create guidelines for writing new automated tests
Document CI/CD pipeline configuration and usage
Provide runbook for common troubleshooting scenarios
Create video tutorials or live training sessions for QA team
Document how to add new tests and maintain existing ones
Required Qualifications
Must Have
5+ years of test automation experience with modern frameworks
Strong Playwright expertise (minimum 2+ year hands-on experience)
Proven experience converting manual test cases to automated tests
Strong understanding of testing best practices (page objects, test data management,
etc.)
Experience with CI/CD integration (GitLab preferred, Jenkins/GitHub Actions
acceptable)
Proficiency in JavaScript/TypeScript for test automation
Experience with test reporting tools and dashboards
Ability to capture and manage test evidence (screenshots, videos, logs)
Strong communication skills for knowledge transfer and QA team collaboration
Nice to Have
Experience with test management tools (TestRail, Zephyr, qTest, or similar)
Knowledge of GitLab CI/CD specifically
Experience with Allure, ReportPortal, or similar test reporting platforms
Familiarity with web application testing (HTML, CSS selectors, APIs)
Experience testing Ruby on Rails applications
Understanding of accessibility testing (WCAG compliance)
Experience with visual regression testing
Knowledge of performance testing concepts
Previous contractor/consulting experience building automation frameworks from
scratch
Technical Environment
Primary Framework: Playwright (JavaScript/TypeScript)
Application Stack: [Ruby on Rails, React, etc.]
CI/CD Platform: GitLab CI/CD
Test Dashboard: [Allure, ReportPortal, custom dashboard, etc.]
Browser Support: [Chrome, Edge]
Existing Test Documentation: Manual test cases in Jira
Project Timeline
Estimated Duration: 6 months
Commitment: Full-time preferred (30-40 hours/week), part-time considered (minimum
20 hours/week)
Start Date: As soon as possible.
Working Arrangement
Remote: Yes (must overlap with [your timezone] for collaboration)
Communication: Regular check-ins via [Slack/Teams/etc.], daily status updates
Collaboration: Will work closely with QA team and DevOps/Engineering team
Knowledge Transfer: Regular pairing sessions with QA team members
Evaluation Criteria
We will evaluate candidates based on:
Playwright expertise and test automation experience
CI/CD integration experience
Test framework design and best practices knowledge
Communication and knowledge transfer ability
Availability and project timeline fit
About This Role
This is a focused, high-impact project ideal for a contractor who:
Has built test automation frameworks multiple times
Enjoys mentoring and knowledge transfer
Values writing maintainable, scalable test code
Understands the balance between speed and coverage
Can work independently but collaborates well with QA teams
Prefers short-term projects with clear deliverables
Questions for Applicants to Answer
To help us evaluate fit, please answer these questions in your application:
1. How many years have you been using Playwright specifically? Describe a
complex testing scenario you automated with Playwright.
2. Have you integrated automated tests into CI/CD pipelines before? Which CI/CD
platforms have you used? (GitLab experience is a plus)
3. What is your approach to test evidence capture? How do you ensure tests
generate useful debugging information when they fail?
4. Describe your experience with test reporting dashboards. Which tools have you
used, and what's your preferred approach?
5. What's your strategy for converting manual tests to automation? How do you
prioritize which tests to automate first?
6. How do you structure automated tests for maintainability? (Page objects, helper
functions, test data management, etc.)
7. What's your typical approach to knowledge transfer at the end of a contract?
How do you ensure the team can maintain tests after you leave?
8. What is your availability over the next 6 weeks? (hours per week, any blackout
dates)
Additional Context
Our Current State
Current Testing Approach:
We have started our playwright implementation but need a seasoned experienced resource
to help us continue it. We currently rely on manual testing performed by our QA team. Our
manual testing is thorough and well-documented, covering:
Release testing before each deployment
Regression testing of critical features
End-to-end user workflow validation
What We Have:
Documented manual test cases that can serve as the foundation for automation
QA team with deep product knowledge to guide automation priorities
GitLab CI/CD infrastructure already in place
Playwright implemented in our CICD
Allure Dashboard
What We Need:An experienced automation engineer to:
Update, improve, Build the automation framework foundation
Convert our priority manual tests to automated tests
Set up the CI/CD integration properly
Implement proper evidence capture and reporting
Train our QA team to maintain and extend the automation
Our Product:
Web-based SaaS platform
Ruby on Rails backend, React frontend
Success Criteria
The project will be considered successful when:
Playwright framework is set up with clear structure and best practices
priority manual tests are converted to automated tests
All automated tests run successfully in local development environment
Tests are integrated into GitLab CI/CD and can be run on-demand
Screenshots are captured automatically during test execution
Test results are displayed in our dashboard with pass/fail status and evidence
Failed tests generate clear debugging information (screenshots, logs, videos)
QA team has been trained and can write new tests independently
Documentation is comprehensive and clear
CI/CD pipeline executes tests efficiently (reasonable execution time)
Team feels confident maintaining and extending the test suite
Example Test Scenarios to Discuss
During the technical interview, we may discuss how you would approach automating
scenarios like these:
1. User Login Flow:
Navigate to login page
Enter credentials
Handle 2FA (if applicable)
Verify successful login and redirect
Capture evidence at each step
2. Workflow Steps and Process steps
Step through workflow steps that contain conditional logic.
Form data capture with conditional logic
eSignature capture and validation with ADFS/SSO
Workflow completion
3. Form Submission with Validation:
Fill out complex multi-step form
Test client-side validation
Test server-side validation
Handle success and error states
Verify data persistence
4. File Upload Workflow:
Upload file
Validate file type/size
Verify processing
Download/preview uploaded file
Pay: ₹70,000.00 - ₹80,000.00 per month
Work Location: Remote
