Metajive · 1 week ago
QA Specialist- Freelance/Contract
Metajive is seeking a QA Specialist to contribute to their product quality strategy. The role involves designing test cases, maintaining automated testing suites, and ensuring the quality of specific features or modules through comprehensive testing strategies.
AdvertisingGraphic DesignMarketingUX Design
Responsibilities
Take full ownership of testing for specific features or modules, from initial requirement analysis to final release
Create sophisticated test strategies that go beyond "happy paths," incorporating negative testing, boundary analysis, and error handling
Write and maintain reliable automated scripts within our framework (e.g., Selenium, Playwright, or Cypress). You will help reduce manual regression efforts by identifying high-value automation targets
Perform deep-dive testing of RESTful APIs using tools like Postman or Charles Proxy to validate data integrity and system integration
Act as a "Quality Advocate" by not just reporting bugs, but investigating root causes and providing developers with detailed logs and reproduction steps
Work closely with Product Managers to refine User Stories and acceptance criteria, ensuring requirements are clear and testable
Provide guidance and peer reviews for junior QA members' test cases and automation code
Qualification
Required
3–5 years of professional experience in software quality assurance
Willingness to be on-site for project kick-offs and check-ins at our office in Encinitas, CA
Proven experience writing automated tests (not just executing them). Proficiency in at least one scripting language (e.g., JavaScript, Python, or Java)
Strong mastery of the Software Testing Life Cycle (STLC) and how it integrates into Agile/Scrum environments
Expert-level knowledge of Jira, TestRail (or similar), and Git for version control
Ability to write complex SQL queries to verify data persistence and perform backend validation
Basic understanding of how testing fits into CI/CD pipelines (e.g., Jenkins, GitHub Actions, or GitLab)
The ability to look at a feature and ask, 'What happens if the user does this?'
Comfortable switching between manual exploratory testing and technical automation tasks as the sprint requires
Ability to explain technical defects to non-technical stakeholders and advocate for quality when deadlines are tight