QA Engineer

About This Role

Give Lively is looking for a highly autonomous QA Engineer to support manual QA, regression testing, and release validation for our fundraising platform. This is a 40-hour per week contract position needed immediately through the end of the year, prioritizing candidates in the US.

The role will focus primarily on classic manual QA: clearing ongoing QA backlogs, validating Jira tickets against existing acceptance criteria, performing deployment regression testing, and helping to ensure our deployment process is secure.

You will report to our Senior QA Engineer and work closely with product managers and engineers to identify, document, and resolve issues, ensuring code is addressed before it enters production.

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

Criteria for Success

You will help Give Lively maintain a reliable, secure, and always-available donation platform serving 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.
• QA backlogs are reduced.
• Regression testing supports consistent, secure deployments.
• The team has a clear understanding of known bugs, their severity, and frequency.
• Payment, refund, donation, and allocation processes are thoroughly tested when needed.

Your Work

• Manually test new features, bug fixes, and release candidates.
• Review Jira tickets, acceptance criteria, and review applications.
• Validate expected user behavior before changes enter production.
• Perform regression testing on deployments.
• Document clear, reproducible bugs and communicate findings to engineers.
• Collaborate closely with senior QA engineers, product managers, and engineers.
• Guide testing using Gherkin-style specifications and acceptance criteria.
• Identify edge cases that automated testing might miss.
• Test payment, refund, donation, and allocation workflows when needed.
• Help improve QA processes, bug tracking, and release quality.

Must-Haves

• 2+ years of QA engineer experience with product engineering teams.
• Extensive manual QA experience.
• Experience testing consumer-facing web products, APIs, or applications.
• Ability to test against acceptance criteria and product requirements.
• Ability to work independently and communicate clearly with engineers.
• Strong judgment on when to use manual testing versus automation.
• Experience using end-to-end test cases, acceptance criteria, or regression test plans.
• Familiarity with HTML, CSS, JavaScript, and responsive web behavior.
• Experience using Jira or similar ticketing systems.
• Ability to work 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 specifications.
• Experience using Capybara, Cypress, or RSpec.
• Experience testing Salesforce integrations.
• Experience testing Stripe, PayPal, payment flows, refunds, or allocations.
• Experience with donation, fintech, billing, marketplace, e-commerce, or transaction platforms.

Current Tech Stack

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