About Our Client
Our client specializing in cloud communication, is looking to add dual QA Engineer / DevOps Engineer for a full-time and permanent position. This role is fully remote anywhere in Canada and comes with an amazing benefit package. To provide some clarity, 80% of this role is QA and 20% is going to be DevOps. The nature of the product would require manual testing with the view to looking at automation where possible.
Responsibilities:
QA
◦Thoroughly reviewing requirements and technical design documents to gain a deep understanding of the software's functionalities and specifications.
◦Identifying inconsistencies, ambiguities, or gaps in documentation, and feeding that back to the development team early.
◦Creating detailed test plans and test cases covering functional, regression, and performance testing.
◦Systematically identifying and documenting defects so the software functions as intended.
◦Assessing scope and complexity, allocating time effectively, and setting realistic testing timelines.
◦Collaborating with developers and product managers across the CI/CD pipeline so testing lands where it's needed, not just where it's convenient.
◦Executing manual test cases that simulate real user interactions and documenting results.
◦Writing and maintaining automated test scripts, ideally wired directly into the CI/CD pipeline you also maintain — this is where the two halves of the role reinforce each other.
◦Recording and tracking bugs in JIRA with severity and reproduction steps, in an Agile environment.
◦Performing regression testing to confirm fixes don't introduce new issues.
◦Identifying areas for improvement and contributing to the ongoing reliability of the software.
◦Keeping pace with the evolving QA and test-automation tooling landscape.
DevOps
◦Administering our Bitbucket repositories: access permissions, repo structure, and housekeeping (archiving stale repos, managing webhooks/integrations).
◦Defining and maintaining our branching strategy (e.g. trunk-based development or a Git-flow variant), and making sure the team actually follows it.
◦Configuring branch protections — required reviews, status checks, and restricting merge rights on main/release branches to the Senior Solutions Architect.
◦Facilitating the PR process: making sure PRs are reviewed, checks pass, and merges are clean (no unresolved conflicts, no broken build history).
◦Preparing PRs for merge and confirming they meet the merge checklist — final merges to main are performed by the Senior Solutions Architect
◦Building and maintaining Bitbucket Pipelines (or equivalent) for build, automated test, and staging-deploy stages.
◦Troubleshooting pipeline failures and keeping build times reasonable.
◦Coordinating releases: versioning, tagging, changelogs, and scheduling deployment windows.
◦Preparing release candidates and staging deployments for sign-off; production deployment is executed by the Senior Solutions Architect.
◦Maintaining dev/staging/production environment configuration and keeping them in sync.
◦Writing and maintaining rollback procedures, and executing rollbacks on staging (production rollback is triggered by the Senior Solutions Architect).
◦Setting up basic uptime, error-rate, and performance monitoring/alerting for production services.
◦Triaging alerts and escalating to the right developer when an issue is beyond first-line response.
◦Maintaining runbooks for deployment, rollback, and common operational tasks, so this knowledge isn't stuck in one person's head.
Requirements:
◦This is not a junior or beginner position — proven experience in software QA is required.
◦Hands-on experience with Git and a Git hosting platform (Bitbucket preferred; GitHub/GitLab acceptable), including branching strategies (Git-flow, trunk-based, or similar).
◦Experience configuring or maintaining a CI/CD pipeline (Bitbucket Pipelines, Jenkins, GitHub Actions, CircleCI, or similar).
◦Comfortable with basic Linux administration and shell scripting.
•Strong knowledge of software QA methodologies, tools, and processes.
•Proficiency in SQL and scripting.
◦Experience with performance and/or security testing.
◦Familiarity with a public cloud platform (AWS, Azure, or GCP) at a basic operational level.
◦Exposure to containerization (Docker) and/or Infrastructure as Code (Terraform, CloudFormation) — not mandatory, but a plus given our environment footprint is small.
