Search jobs

Position: Software Engineer: Product Quality

Salary: $120,000 to $140,000 CAD

Location: Canada based.

About Fiscal.ai

Fiscal.ai is a leading research and data platform built for capital markets professionals. Combining a high-performance research Terminal with a modern, near-real-time fundamentals API and MCP server, Fiscal.ai is redefining financial data infrastructure for the AI era. The company serves thousands of institutional and professional Clients while reaching millions of end-users through API Clients.

The Role

The Fiscal.ai Terminal is used every day by thousands of investors to research companies: financial statements, segments and KPIs, estimates, ownership and insider activity, filings, valuation models, screening, and charting. When a chart won't load, a screen returns the wrong companies, or a paywalled cell unlocks for the wrong tier, our users notice immediately, because they know exactly how the product should behave.

You will own the quality of the Terminal. This is an engineering role, not a QA analyst role. You will find bugs, reproduce them, trace them to root cause across the frontend and backend, and ship the fix yourself. You will build the end-to-end test framework that stops those bugs from coming back. You will work alongside the engineers building the Terminal and the Fiscal.ai data infrastructure.

If you think this is the perfect fit for you, we'd love to hear specifically why, and which bug in a financial product you are proudest of having found and fixed.

Key Responsibilities

• Own the inbound bug pipeline for the Terminal, including Sentry issues, customer-reported problems, and what you find yourself. Reproduce, prioritize, and fix or route every one of them.
• Fix bugs across the stack: the React/Next.js frontend, the Cloudflare Workers backend, and the data layer between them. Investigate to the root cause and never patch the symptom.
• Design and build the end-to-end test framework for the Terminal using Playwright, get it running in CI against preview deploys, and grow regression coverage of the flows that matter most: financials, charting, screener, portfolio, auth, subscriptions, and paywall.
• Write unit and integration tests alongside your fixes so the same class of bug cannot ship twice.
• Turn what you learn into playbooks, including debugging guides, test conventions, and tooling the rest of the team uses.

Requirements

• You write good code, fast, and you fix what you find. If you want to file tickets for someone else to fix, this is not the role.