Manual QA Engineer, Web Applications (US-Remote)

About the role

Give Lively is looking for a highly autonomous QA Engineer to support manual QA, regression testing, and release validation across our fundraising platform.

This is an immediate 40-hour/week contract need through the end of year, with U.S.-based candidates preferred. The role will be heavily focused on classical manual QA: clearing a persistent QA backlog, validating Jira tickets against existing acceptance criteria, running regression on deployments, and helping keep our deployment process moving safely.

You’ll report to our Senior QA Engineer and work closely with product managers and engineers to identify, document, and resolve issues before code reaches production.

This role is ideal for someone who enjoys hands-on QA work, understands when manual testing is more valuable than automation, and is comfortable testing web applications where not everything is a modern single-page app.

What success looks like

You will help Give Lively maintain a reliable, secure, and always-available donation platform for nonprofits and their donors.

Success means:

• Nonprofits can set up donation pages without errors or unexpected behavior.
• Donors can complete donations smoothly across modern browsers and devices.
• Engineers receive clear, actionable bug reports.
• The QA backlog is reduced.
• Regression testing supports consistent, safe deployments.
• The team has a clear view of known bugs, their severity, and frequency.
• When needed, payment, refund, donation, and disbursement flows are tested thoroughly.

What you’ll do

• Manually test new features, bug fixes, and release candidates.
• Review Jira tickets, acceptance criteria, and review apps.
• Validate expected user behavior before changes go to production.
• Run regression testing on deployments.
• Log clear, reproducible bugs and communicate findings to engineers.
• Work closely with the Senior QA Engineer, product managers, and engineers.
• Use Gherkin-style specs and acceptance criteria to guide testing.
• Identify edge cases that automated tests may miss.
• When needed, test payment, refund, donation, and disbursement workflows.
• Help improve QA process, bug tracking, and release quality.

Must haves

• 2+ years of experience as a QA Engineer in a product engineering team.
• Strong manual QA experience.
• Experience testing consumer-facing web products, APIs, or apps.
• Comfort testing against acceptance criteria and product requirements.
• Ability to work independently and communicate clearly with engineers.
• Strong judgment around when to use manual testing vs. automation.
• Experience working with end-to-end test cases, acceptance criteria, or regression test plans.
• Familiarity with HTML, CSS, JavaScript, and responsive web behavior.
• Experience using Jira or a similar ticketing system.
• Comfort working in a small, collaborative team.

Nice to haves

• Experience testing Ruby on Rails or server-rendered applications.
• Experience with Gherkin, BDD, or human-readable acceptance specs.
• Experience with Capybara, Cypress, or RSpec.
• Experience testing Salesforce integrations.
• Experience testing Stripe, PayPal, payment flows, refunds, or disbursements.
• Experience with donation, fintech, billing, marketplace, ecommerce, or transactional platforms.

Current stack

Our application is built primarily with Ruby on Rails. The core platform uses Heroku, Postgres, CloudFront, and CircleCI. We use RSpec, Cypress, Capybara, and Gherkin-style specs to support end-to-end coverage.