QA Tester

About Vantum

Vantum helps fractional operators win new clients while delivering for the clients they already have. When you are managing several engagements, client work can consume the week and leave little time to find the next one.

The product is a web app for planning, tasks, calendar, goals, and Ask Vantum, an AI chat that helps an operator decide what to do next.

We are a team of five, working toward product-market fit. We are looking for a QA tester to use the live product the way a customer would, and to write bugs we can reproduce.

You will work directly with the founders.

What you will own

Your job is to find what is broken, write it so someone else can reproduce it, and check that the fix actually holds.

• Walk the main flows. Sign-in, home, plan, tasks, calendar, goals, notes, and Ask Vantum.

• Write each bug so it can be reproduced. Steps, what you expected, and what actually happened. Include the page, the account state, and a screenshot when it helps.

• Recheck fixes. A bug is not done because someone said it was fixed. Confirm the original steps, and check that a nearby flow did not break.

• Notice gaps. If a button does nothing, a save does not stick, or the page says one thing and the data shows another, file it.

• Ask when a behavior might be intentional. Do not guess, and do not redesign the product.

You are not building features, and you are not writing production code. Clear written English is the job.

What we are looking for

You notice when software is wrong, and you can describe it without a developer sitting next to you.

You should be able to:

• Follow a flow from start to finish. Include empty states, errors, and the second time through.

• Write a bug report a stranger can follow. Steps, expected result, actual result.

• Tell a display problem from a data problem. The page looks saved, but a refresh brings the old value back.

• Show the evidence. Use a browser, screenshots, and a short screen recording when steps are hard to write.

• Communicate clearly in written English. We read your reports every day.

• Take ownership. Retest what you filed, and say when you cannot reproduce it.

Prior QA employment is useful. It is not required. Testing your own projects, a client product, or a careful write-up of bugs in software you use counts.

We do not need test automation, a computer science degree, or experience with our stack.

Why join

You will see real product decisions, talk to the founders, and watch your reports turn into fixes.

The work is part-time and remote. You set a steady weekly rhythm with us, and you tell us what you found in writing.

Compensation and working arrangements

• $500 to $1,000 USD per month, depending on hours and how clearly you report what you find.

• Part-time, remote.

• At least three hours of weekday overlap with Bangkok (GMT+7), so we can review bugs the same day.

• Hours are agreed on the call. This is not a full-time engineering role.

How we hire

1. Written application. We read how you describe a bug.

2. Screening call. We talk through a product you tested and a bug you filed.

3. A short look at the live app. You walk one flow and write up what you find.

Apply

Describe one bug you found that was easy to miss. Include the steps, what you expected, and what actually happened.

Tell us your timezone, your weekday overlap with Bangkok, when you can start, how many hours a week you can give, and your expected monthly pay.

Originally posted on Himalayas