Skip to main content

CareerSwift

Quality Assurance Engineer

United States (Remote)fulltimemidAdded today

About this role

CelebriOS is seeking a Quality Assurance Engineer to ensure software reliability across web, mobile, and API products through manual testing, test automation, and defect prevention. You'll collaborate with engineering teams to define test strategies, identify risks, and maintain quality standards throughout the release cycle.

What you'll do

  • Develop test plans and define acceptance criteria based on requirements
  • Execute functional, regression, integration, and exploratory tests
  • Build and maintain automated UI and API tests
  • Document defects with detailed reproduction steps and evidence
  • Validate bug fixes and track recurring quality issues
  • Communicate quality risks and readiness status to stakeholders

What they're looking for

  • Manual and automated testing
  • Test design and defect management
  • API and web application testing
  • Jira and Postman
  • Playwright, Cypress, Selenium, or Appium
  • JavaScript, Python, or Java
  • SQL and CI/CD systems
  • Analytical problem-solving

Benefits

  • Health, dental, and vision coverage
  • Flexible PTO
  • 401(k) retirement plan
  • Home-office equipment stipend
  • Annual learning and development budget
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

CareerSwift

CareerSwift builds an AI-powered job search platform with a focus on reliable infrastructure and polished user experiences. The company is hiring DevOps engineers to manage cloud infrastructure and CI/CD pipelines, frontend developers to build React-based interfaces, and QA engineers to ensure product quality through manual and automated testing.

View all jobs at CareerSwift

Likely interview questions

  • Walk us through your approach to creating a comprehensive test plan for a new feature spanning web and mobile platforms.
  • Tell us about a time you discovered a critical bug—how did you document it and work with developers to resolve it?