IAM - Automation Test Engineer

Role:
Automation Test Engineer - IAM

Employment:
Contract - Inside IR35

Location:

Sheffield, UK - Hybrid 3 days onsite a week

NOTE:

Looking for candidates from UK only with valid work permit.

• Area: Coding & automation
  • Must: Strong Python coding &
    Py Test automation experience to build reusable test utilities
  • Should:
    Playwright exposure
  • Nice: Typescript
• Area: API testing
  • Must:
    REST API automation; API tooling (
    Insomnia
    /
    Apidog
    /
    Postman
    );
    API Gateway testing
  • Should:
    Batch ETL testing
  • Nice: Advanced schema/property-based testing
• Area: 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
• Area: Graph validation
  • Must: Any GraphDB testing or extensive testing of No
    
    SQL DB
  • Should:
    Neo4j basics;
    Cypher queries for assertions;
    graph data validation.
  • Nice: GDBMS performance analysis
    • Reporting query validation
• Area: IAM domain
  • Must:
    IAM concepts (auth/access);
    RBAC
    /
    ABAC
    /
    ReBAC
    /
    PBAC
  • Should: Identity lifecycle (Joiner/Mover/Leaver); human vs non-human identities
  • Nice: Federation concepts
• Area: Policy-as-code
  • Must: Testing decision points as code
  • Should:
    OPA
    /Rego policy testing; policy explainability validation
  • Nice: Policy drift detection automation
• Area: CI/CD & Dev Ops
  • Must:
    Jenkins pipeline creation/management; shift-left mindset
  • Should:
    Git Ops repo experience;
    Git Lab CI/CD integration
  • Nice: Containerised test execution patterns
• Area: Observability & reporting
  • Must: Log/metric/trace validation in tests
  • Should: Signal-based failure detection automation
    • Allure reporting;
      Grafana dashboard awareness
• Area: 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
• Area: Tools & ways of working
  • Must:
    JIRA
  • Should: Test tool selection/recommendations
  • Nice: Advanced test data factories
    • zephyr defect reporting and triage
    • Test tool selection/recommendations
• Area: Performance testing
  • Must: Awareness/exposure
  • Should: Licensing/config/dashboard ownership
    • JMeter
      /
      Gatling
      /
      Neo Load experience
• Area: Data ingestion protocols
  • Must: Awareness of formats/protocols
  • Should: Identity warehousing exposure
    • SCIM
      /
      LDAP
      /
      OIDC
      /
      CSV exposure