Software Engineer: Quality (Terminal)

Job Title: Software Engineer: Quality (Terminal)Salary: $100,000-$220,000 + equity options.Location: Remote with occasional in-person work in our co-working space in downtown Toronto.

​

 About Us

​

Fiscal.ai (formerly FinChat) is a leading research and data platform for capital markets. Combining a powerful research Terminal with modern APIs, Fiscal.ai is building the modern financial data company. The firm has raised $13M in venture backing and is headquartered in Toronto, Canada. With thousands of customers and millions of end-users through their API offerings, Fiscal.ai is building the premiere financial data company in the AI era.

​

Brief Description of 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.

​

What you will do 

​

• Own the inbound bug pipeline for the Terminal: 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. Never patch the symptom.
• Design and build the end-to-end test framework for the Terminal (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: debugging guides, test conventions, and tooling the rest of the team uses 

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