Manual QA Engineer
Manual QA Engineer — BroTrades
Type: full-time, remote
Team: you would be the second QA on the product
What BroTrades is
A trading journal with a trading school built in. Traders connect a read-only exchange key or upload a broker statement; their trades import themselves, and they journal the reasoning behind each one. Schools run structured courses on the same platform, where homework is graded against a student’s real trades rather than a quiz.
The product runs in three languages and touches real money records, so a mistake is not a cosmetic bug — it is a trader looking at a number that is wrong about their own account.
What you would test
— Broker statement imports.
— MT4 and MT5 Detailed Statements (.htm) and Libertex closed-deals reports (.csv).
Statements differ by broker, by platform version, by account currency and by locale, and a parser that reads one correctly can silently mis-read another. You would build and maintain a corpus of real statements to test against.
Exchange sync. Bybit, Binance and OKX, over read-only API keys. Closed positions, open positions, and the states in between.
Backtest import. TradingView Strategy Tester exports (.xlsx), read separately from live trades.
The school side. Courses, lessons, homework submission, mentor review, enrolment and invitations.
Everything in three languages. English, Ukrainian and Russian, across the whole product — not a spot check of the home page.
Requirements
— Hands-on experience testing web applications, with a habit of writing down what you did rather than reporting that something “doesn’t work”
— MT4 and MT5: you can open a terminal, place and close trades on a demo account, and export a Detailed Statement without being walked through it
— Comfortable reading a broker statement and saying what the platform should have produced from it
— GitHub Issues for tracking: you would file, reproduce, label and verify fixes there
Use-case testing: you work from a described user journey and its edge cases, not only from a click-through script
English for all written work — tickets, notes, test cases. The team is multilingual; the written record is not
Ukrainian or Russian as a second language, since two of the three interfaces are in them and someone has to read them as a native speaker would
Nice to have
You trade, or have traded. You do not need to be profitable — you need to know what a stop-loss is without looking it up, because half the bugs are only visible to someone who understands what the number is supposed to mean
Experience with financial or fintech products, and the care that comes with them
Basic SQL, enough to check whether the screen and the database agree
Familiarity with browser devtools: network tab, console errors, responsive mode
How the work runs
Tickets live in GitHub. You file with steps to reproduce, expected versus actual, environment, and evidence. Fixes come back as pull requests with preview deployments — you re-test on the preview before it reaches production.
You would work directly with the founder. There is no QA manager to translate what you find, which cuts both ways: nothing is filtered, and nobody else will notice what you miss.
What we are honest about
This is an early-stage product. The test surface changes weekly, some areas have no automated coverage at all, and you will find bugs older than your employment. If you want a mature suite to execute, this is the wrong role. If you want to decide what testing this product needs, it is a good one.