Operational Readiness Testing Engineer
Client: Enterprise Technology
Contract: 8-month rolling contract
Location: Toronto, Downtown, 2-3 days/week preferred
Summary:
- Develop clear and traceable manual test cases, including breakage and chaos scenarios, to meet the non-functional requirements (NFRs) for Operational Readiness Testing (ORT) of the Payment Platform.
- Ensure these test cases serve as the authoritative source for future test scripts, aligning with ORT test areas such as TRP, HA, ITSM/ITOM, Business Support, BAM, and Observability.
Responsibilities:
- Create test cases using the program's testing template, based on identified flow and technical layer.
- Extract acceptance criteria from NFRs (e.g., latency, MTTA, DR, security) and map each to the corresponding Observability & ITOM alert.
- Conduct peer reviews of ServiceNow Flows and CI scan outputs to ensure the Configuration Items (CIs) referenced in CSDM and CMDB data align with the environment.
- Maintain a traceability matrix linking Application Test Scenarios, ORT Test phases, and NFRs.
- Collaborate with Observability & ITOM engineers to confirm required metrics and events exist before declaring a test ready.
Key Qualifications:
- Proven experience in writing system-integration or SRE readiness test cases for distributed, containerized platforms.
- Strong understanding of fail-over concepts such as node reboot, pod recycle, cluster namespaces, and HA sites.
- Proficient in OpenShift/Kubernetes, including micro-services, containerized deployments, and REST messaging.
- Ability to interpret Dynatrace dashboards, Splunk searches, and ServiceNow Event timelines to confirm observable outcomes.
- Skilled in using Jira and Confluence for test-case management and defect logging.
- Familiarity with ServiceNow Flow to validate ITSM/ITOM alignment.
- Excellent documentation skills, capable of expressing complex scenarios in concise, unambiguous steps for both manual execution and future automation.
- Proficiency in English with strong communication skills to effectively respond to comments and feedback from technical, application, and business stakeholders without ambiguity.
Nice-to-Have:
- Experience in the payments or banking domain.
- Familiarity with chaos-engineering tools.