Role Overview
GoCharting is a web-native charting and trading workflow platform specializing in institutional-grade orderflow and DOM tools. Quality is existential for our platform, as data accuracy and feed reliability directly impact customer trust and trading success. This role serves as the first line of defense against critical issues.
You will own functional and manual testing across the live trading terminal, charting, DOM, orderflow tools, and market-data surfaces. You will report to the CEO inside Client Engineering and collaborate closely with the QA Automation Engineer, backend, frontend, and Support teams.
Success in year one includes fewer regressions in production, faster release cycles, and catching data-accuracy issues before customers see them.
What you'll do
- Own functional and manual testing — across the terminal, charting, DOM, and orderflow; write and execute test plans and cases from product specs and real trader workflows
- Test what matters most — data accuracy and feed reliability — validate prices, bars/OHLC, symbols, and session handling across markets, and catch bad prints, gaps, and lag before release
- Run cross-browser and regression testing — across the established terminal and the newer product monorepo, keeping a dependable release regression suite
- Own the bug lifecycle — reproduce, isolate, and write crisp reproducible reports; verify fixes; and partner with Support to triage customer-reported data issues
- Maintain test documentation — test plans, cases, checklists, and acceptance criteria that keep quality repeatable
- Feed the automation effort — identify the high-value, repetitive cases worth automating and work with the QA Automation Engineer to keep the suite meaningful
- Be the last line before release — run release and acceptance testing and give a clear go/no-go quality read
Requirements
Must-haves:
- 3–5 years in QA / software testing, with strong manual and functional testing on complex, data-heavy web applications
- Rigorous, methodical, and detail-obsessed — you find the bug others miss and write reports engineers can act on immediately
- Solid test design — test plans, cases, boundary and edge conditions, and regression coverage
- Comfortable reading API responses, using browser devtools, and running basic SQL to verify data
- Clear written communication and genuinely reproducible bug reporting
- High autonomy — comfortable owning quality in a lean team with little hand-holding
- In-person in our Chennai office
Nice-to-haves:
- Trading, investing, fintech, or market-data exposure — you understand ticks, OHLC, and order book data, and how a trader reads a chart
- Some test-automation exposure (Playwright, Cypress, or Selenium), or clear eagerness to grow into it
- Experience testing real-time / WebSocket-driven or visualization-heavy UIs
- Familiarity with bug-tracking and test-management tools (Jira, TestRail)
- Familiarity with Indian (NSE/MCX) or US (CME) market structure
- Top-tier Indian institution (IIT/NIT/IIM) — nice-to-have, not a gate