Work mode: Hybrid 3 days weekly from office
We a Coforge are looking for Automation Test Engineer in Sheffield, UK.
Role Summary
We are looking for a highly skilled Automation Test engineer with expertise in Identity and Access management (IAM) back-end validation. Skilled in identity orchestration, API testing, data ingestion and transformation, and event-driven (Pub/Sub) architectures. This role focuses on testing secure, scalable identity and access workflows across Google Cloud Platform, integrating identity services with custom APIs, Pub/Sub pipelines, and cloud-native applications.
Using an automation first approach, you will collaborate closely with tech leads, Cloud Security, DevOps, and Application Engineering teams to thoroughly test robust IAM, identity lifecycle workflows, and secure service integrations that support enterprise-level cloud and Identity operations.
Key Responsibilities
* Build and maintain an automated test framework and suites for API, event, and graph-based services (Python/PyTest).
* Define and execute test plans/cases/data aligned to requirements and technical specs; maintain FR/NFR traceability.
* Validate IAM concepts and access models (RBAC/ABAC/ReBAC/PBAC) and test decision points “as code” (policy-as-code).
* Perform API automation, contract testing, and replay/reprocessing scenarios.
* Validate graph data (nodes/relationships/hop logic) and event lineage/change behaviour. Experience in Neo4J is preferred.
* Produce regulatory evidence as required; support entry/exit criteria and test governance activities.
* Create/manage Jenkins pipelines to manage tests executions and reporting as part of CI/CD.
* Log, track, and drive defects through triage to closure (JIRA/ Zephyr); communicate progress to stakeholders.
* Collaborate with Cloud Security, DevOps, and Engineering teams; contribute to improving testability and quality.
Skills required
Coding & Automation
* Must: Strong Python coding & PyTest automation experience to build reusable test utilities
* Should: Playwright exposure
* Nice: Typescript
API Testing
* Must: REST API automation, API tooling (Insomnia / Apidog / Postman), API Gateway testing
* Should: Batch ETL testing
* Nice: Advanced schema/property-based testing
Event-Driven Testing
* Must: Pub/Sub and MQ concepts, Replay/reprocessing, Idempotency-style validation
* Should: Async failure handling patterns
* Nice: Ordering / duplication / retry deep-dive suites
Graph Validation
* Must: Any GraphDB testing or extensive testing of NoSQL DB, Reporting query validation
* Should: Neo4j basics, Cypher queries for assertions, Graph data validation
* Nice: GDBMS performance analysis
IAM Domain
* Must: IAM concepts (authentication & access), RBAC / ABAC / ReBAC / PBAC
* Should: Identity lifecycle (Joiner / Mover / Leaver), Human vs non-human identities
Policy-as-Code
* Should: OPA / Rego policy testing, Policy explainability validation
CI/CD & DevOps
* Must: Jenkins pipeline creation and management, Shift-left mindset
* Should: GitOps repository experience, GitLab CI/CD integration
* Nice: Containerised test execution patterns
Observability & Reporting
* Should: Log, metric, and trace validation in tests
* Nice: Signal-based failure detection automation, Allure reporting, Grafana dashboard awareness
Test Governance
* Must: FR/NFR traceability, Entry & exit criteria, Test case review for coverage
* Should: Risk-based prioritisation, Layered test architecture
* Nice: Cross-team RACI enforcement
Tools & Ways of Working
* Must: JIRA, Zephyr defect reporting and triage
* Should: Test tool selection and recommendations
* Nice: Advanced test data factories
Performance Testing
* Should: Awareness / exposure
* Nice: Licensing / configuration / dashboard ownership, JMeter / Gatling / NeoLoad experience
Data Ingestion Protocols
* Should: Awareness of formats and protocols
* Nice: Identity warehousing exposure, SCIM / LDAP / OIDC / CSV exposure
#J-18808-Ljbffr