Senior Software Developer at Caseware
Toronto
—
Jul 21, 2026
Toronto
Jul 23, 2026
What this job asks for AI summary
A senior backend-leaning engineering role focused on designing and building distributed microservices for audit and accounting software. Day-to-day work spans prototyping, shaping architecture proposals, maintaining CI/CD pipelines, and guiding less experienced developers through code and design reviews. The role suits an experienced Java/Spring Boot engineer comfortable working across cloud infrastructure, SQL/NoSQL data stores, and AI-assisted development tooling.
Senior level · Toronto, ON · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
This role is based in Toronto, Canada (hybrid, 3 days/week in office) — US compensation benchmarks do not apply; salary is quoted in CAD.
A Computer Science/Software Engineering degree is listed in the responsibilities section rather than a formal requirements block, and the posting explicitly accepts 'equivalent work experience' — treated as no hard degree requirement.
AWS is listed as the required cloud platform with 'ideally' as a qualifier, suggesting it is the preferred cloud but the requirement is for public cloud experience broadly; alternatives (Azure, GCP) are noted accordingly.
GitHub Actions is listed with the parenthetical '(or other tool)', confirming the specific tool is interchangeable; common CI/CD alternatives are captured.
REST and GraphQL are presented as interchangeable options ('such as REST or GraphQL') under the requirements block — emitted as one skill with GraphQL as an alternative.
The 'Tech stack you'll be working with' section names the team's actual tools (EKS, Lambda, Step Functions, SNS/SQS, Aurora, DynamoDB, MongoDB, S3, Jira, IntelliJ, Claude) — these appear as stack context rather than gated requirements and are marked preferred.
AI/agentic engineering expectations (Claude Code, conversational AI assistants, inline code completion) are described as behavioral expectations rather than named technology gates; Claude is captured as a preferred tool from the stack section.
No overall years-of-experience figure is stated in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.