1

Sr Software Development Engineer In Test Jobs in Alberta

Partner with senior product engineers to route AI-generated defect fixes through the verification ... in software engineering, SDET, SRE, or DevOps roles. Why This Role, Why Now Most testing ...

Possess a Bachelor's degree in a relevant field and over 7 years of software development experience ... tests across multiple layers (e.g., unit, integration), and familiarity with modern frontend ...

... development required to visualize complex geoscience data. You will be instrumental in defining the ... Design, implement, test, document, and maintain complex frontend features using modern JavaScript ...

You are a senior software engineer who happens to specialize in automation, not a developer who ... Software Development Life Cycle and mentoring team members. * Experience working in the banking ...

About the Role The Senior Software Engineer is a hands-on technical contributor embedded in our agile development organization, helping build and deliver our next-gen compliance platform. You bring ...

next page

Showing results 1-20

Sr Software Development Engineer In Test information

What is a Sr Software Development Engineer in Test?

A Sr Software Development Engineer In Test (Sr SDET) is a senior-level professional responsible for designing, developing, and maintaining automated test frameworks and tools to ensure the quality of software products. They work closely with developers and other QA team members to create robust testing strategies, identify defects, and improve the overall software development process. Sr SDETs have advanced programming skills, deep knowledge of test automation, and often mentor junior team members. Their goal is to enable efficient, reliable, and scalable automated testing throughout the software development lifecycle.

What are the key skills and qualifications needed to thrive as a Sr Software Development Engineer in Test?

To thrive as a Sr Software Development Engineer In Test, you need advanced programming skills (such as Java, Python, or C#), deep understanding of software testing methodologies, and a bachelor’s or master’s degree in computer science or a related field. Expertise with automation frameworks (like Selenium or Cypress), CI/CD tools (Jenkins, Git), and test management systems is typically required, along with certifications such as ISTQB being beneficial. Exceptional problem-solving abilities, attention to detail, and strong collaboration and communication skills distinguish standout professionals in this role. These competencies ensure the delivery of high-quality, reliable software products through efficient test automation and seamless teamwork.

What are some common challenges faced by a Sr Software Development Engineer in Test when working on large-scale projects?

Sr Software Development Engineers in Test (SDETs) often encounter challenges such as managing complex test automation frameworks, ensuring comprehensive test coverage for rapidly evolving codebases, and coordinating with multiple development and QA teams. Balancing the need for speed in continuous integration pipelines with maintaining high-quality standards can also be demanding. Additionally, SDETs are frequently responsible for mentoring junior testers and advocating for best testing practices across cross-functional teams, which requires strong communication and leadership skills.

What is the difference between Sr Software Development Engineer In Test vs Software Development Engineer In Test?

AspectSr Software Development Engineer In TestSoftware Development Engineer In Test
Required CredentialsBachelor's/Master's in CS or related, experience in automation testingBachelor's in CS or related, focus on automation skills
Work EnvironmentDesigns and develops complex test frameworks, leads testing initiativesDevelops and maintains test scripts, executes testing
Employer & Industry UsageUsed in tech companies, especially in QA and testing teamsCommon in software development companies, focusing on testing automation

The main difference is that a Sr Software Development Engineer In Test typically has more experience, leads testing efforts, and designs complex testing frameworks, while a Software Development Engineer In Test primarily focuses on developing and executing test scripts. Both roles require strong automation skills and are vital in ensuring software quality, but the senior role involves more leadership and strategic testing responsibilities.

What are popular job titles related to Sr Software Development Engineer In Test jobs in Alberta?

For Sr Software Development Engineer In Test jobs in Alberta, the most frequently searched job titles are:

What job categories do people searching Sr Software Development Engineer In Test jobs in Alberta look for?

The top searched job categories for Sr Software Development Engineer In Test jobs in Alberta are:

Infographic showing various Sr Software Development Engineer In Test job openings in Alberta as of August 2026, with employment types broken down into 1% As Needed, 82% Full Time, 14% Part Time, and 3% Contract. Highlights an 89% Physical, 3% Hybrid, and 8% Remote job distribution.

Senior SDET

Algo

Calgary, AB • On-site

Full-time

Posted 22 days ago


Job description

About the Role

Software is entering a period where code generation isaccelerating,and verification is the new constraint. We are rebuilding our quality function from the ground up as an AI-first verification engineering team, and we are hiring founding SDETs to design and build it.This is not a test-case-writing role. You will build the verification infrastructure behavioral fences, property-based test suites, static analysis pipelines, and agentic QA workflows thatallowsAI-generated code to ship safely at high velocity. You will work directly with engineering leadership on one of the most consequential transformations in the company's history, with genuine authority to define how quality is engineered here.


What You'll Do

  • Design and build behavioral fences(characterization harnesses that lock in existing behavior, and acceptance harnesses derived from specifications) that AI-generated code must pass beforemerge.
  • Establish system-level behavioral baselines of our core product so agentic refactoring and extension can be verified against observable behavior.
  • Build and own property-based testing suites (invariant-driven, generative input) targeting the failure modes characteristic of AI-authored code.
  • Stand up andoperatethe non-behavioral verification stack: SAST/security scanning,secretsdetection, dependency/supply-chain analysis, and performance baselines in CI/CD.
  • Develop agentic QAworkflowsAI agents that generate, execute, and triage tests with humans reviewing at the level of strategy and coverage, not individual cases.
  • Define and report honest coverage boundaries: what is verified, what is sampled, and what is notcoveredso green dashboards mean what they claim.
  • Implement observability for quality: logging, tracing, and metrics that surface verification signals,escapeddefects, and behavioral drift across the pipeline and in production.
  • Participate in incident response and post-mortems for quality escapes, feeding every production defect back into the fences, suites, and pipeline as a permanent regression guard.
  • Automate deployment of the verification infrastructure itselftestenvironments, harnesses, and pipeline tooling.
  • Develop test strategies for AI-powered product features: prompt regression testing, behavioral boundary testing, output quality evaluation, and regression detection for non-deterministic outputs with observable quality signals defined alongside product and engineering.
  • Partner with senior product engineers to route AI-generated defect fixes through the verification pipeline with human review at the right altitude.


What We're Looking For

  • Strong software engineering fundamentals.You write production-quality code (Python, TypeScript/JavaScript, C#, Java, or Go) and think in systems, not scripts.
  • Active use of AI coding assistants.Tools like Claude Code, Copilot, or Cursor are part of your daily workflow, andyou'regenuinely curious about how far they can be pushed you have opinions about where they fail and how to catch it.
  • An instinct for testing invariants rather thanexamplesexperience with property-based tools (Hypothesis, fast-check,QuickCheck-family) is great evidence, but the mindset iswhat'srequired.
  • CI/CD ownership.You have built or owned pipelines, not justconsumed themgates, quality signals, and tooling that other engineers rely on.
  • Static analysis and security tooling familiarity(e.g.,Semgrep, SonarQube,CodeQL,Gitleaks) and an understanding of why input/output testing alone cannot catch security or performance rot.
  • Performance and reliability awareness.Knowledge of performance tuning, capacity planning, and reliabilitypatternscorrect output at unacceptable latency or fragility is still a defect.
  • Strong diagnostic and problem-solving skills for complex systems,and the ability to work collaboratively across development, QA, and operations teams.
  • A builder's bias.You would rather build a harness that finds a whole class of bugs than manually find one bug.


What Sets You Apart

We know deep experience in these areas israrethe discipline is only a few years old.We'rebuilding it here, andwe'llinvest in developing it. Bring the fundamentals and the appetite; any of the following moves you to the top of the list:

  • Agentic AI experience.Hands-on with Claude Code or comparable agents generating test scaffolding, accelerating authoring, analyzing coverage gaps, or building agentic workflows of your own.
  • Experience testing or evaluating LLM-based systems.Evaluation frameworks (evals), model-graded testing, handling non-determinism, and qualitative evaluation (rubrics, rating systems, calibrated human review) where qualitycan'tbe reduced to assertions.
  • Hands-on property-based or generative testingwith Hypothesis, fast-check, orQuickCheck-family tools in real projects.
  • Supply-chainplanning, manufacturing, or ERP domain exposure.
  • Experience characterizing legacy systems (snapshot/approval testing) ahead of large refactors.
  • Performance and load-testing baseliningexperience.
  • SRE or DevOps background on-call experience, chaos/resilience testing, or advocacy for test-driven development and resilience patterns.


Education & Experience

  • Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
  • 5+ years in software engineering, SDET, SRE, or DevOps roles.


Why This Role, Why Now

Most testing organizations are being disrupted by AI. This one is being built for it with executive mandate, from a clean sheet. You will be a founding member of the team that defines how an entire product organization ships AI-authored software safely. If you have been waiting for a role where verification engineering is treated as the product rather than the afterthought, this is it.


When applying, please include a short noteon the most interesting failure you have seen an AI coding agent produce.