We’re a small, technical engineering team building a modern web application focused on financial workflows (income, expenses, assets, liabilities, etc.). We've inherited a codebase/website that was built from an outsourced software company. We've found several miscellaneous ways in which the site isn't working as expected - mostly reported from users. We want someone to do a deep Testing Audit of the website so that we don't hear about these issues from customers, we hear it from someone testing all the edge cases.
We’re looking for an experienced QA Analyst / Tester who has strong familiarity in financial software to perform a deep exploratory QA audit of the product, identify edge cases, and document current behavior clearly and thoroughly. This is a hands-on, manual QA role, not an automation-focused position.
This engagement will start as a focused, full-time audit and may evolve into a long-term, part-time relationship (5–20 hrs/week) for regression testing and new feature validation.
--------------------------
Phase 1: Initial QA Audit (Primary Scope)
For the first phase, you will:
- Perform deep exploratory testing across the application
- Thoroughly test several complex, spreadsheet-like pages as well as supporting features (charts, tasks, notes, etc.)
- Identify edge cases related to:
--- Financial data entry and calculations
--- State management and data persistence
--- Invalid or unexpected user inputs
--- Workflow interruptions and partial actions
- Document issues with clear, actionable bug reports
--- Repro steps
--- Expected vs actual behavior
--- Severity / impact assessment
- Help us understand how the product behaves today, not just what’s broken
This phase is expected to last ~3–6 weeks at ~40 hrs/week, depending on findings.
--------------------------
Phase 2: Ongoing QA Support (Optional, Not Guaranteed)
- After the initial audit, there may be an opportunity for ongoing, flexible QA support, specifically for regression testing before releases.
- Hours will vary week to week (typically 1–20 hrs/week). Some weeks may be very light.
--------------------------
Deliverables
We’re looking for clear, structured output, including:
- Well-written bug reports with reproducible steps
- A test coverage summary outlining what was tested
- A manual regression checklist we can reuse internally
--------------------------
Ideal Background
We’re looking for someone who:
- Has 3+ years of QA / software testing experience
- Has tested complex, data-heavy web applications
- Has a strong understanding of basic financial concepts, such as:
--- Income vs expenses
--- Assets vs liabilities
--- Balances, totals, and financial edge cases
- Excels at exploratory testing, not just scripted test cases
- Writes clear, precise documentation
- Is comfortable working independently and asynchronously
You do not need to be a software engineer, but you should be technically comfortable navigating modern web apps and reasoning about edge cases.
--------------------------
What This Role Is NOT
To avoid confusion, this role is not focused on:
- Building automated test frameworks
- Writing end-to-end test code
- Designing test infrastructure
We’re specifically looking for a strong manual QA / exploratory testing mindset.