Contract QA Tester Needed for Short-Term Project: Manual Test Audit of Financial Webapp

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.

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...