IAM - Automation Test Engineer

Area

Must

Should

Nice

Coding & automation

Strong Python coding & PyTest automation experience to build reusable test utilities

Playwright exposure

Typescript

API testing

REST API automation; API tooling (Insomnia/Apidog/Postman); API Gateway testing

Batch ETL testing

Advanced schema/property-based testing

Event-driven testing

Pub/Sub and MQ concepts; replay/reprocessing; idempotency-style validation

Async failure handling patterns

Ordering/duplication/retry deep-dive suites

Graph validation

Any GraphDB testing or extensive testing of NoSQL DB

Neo4j basics; Cypher queries for assertions; graph data validation.

GDBMS performance analysis
Reporting query validation

IAM domain

IAM concepts (auth/access); RBAC/ABAC/ReBAC/PBAC

Identity lifecycle (Joiner/Mover/Leaver); human vs non-human identities

Federation concepts

Policy-as-code

Testing decision points “as code”

OPA/Rego policy testing; policy explainability validation

Policy drift detection automation

CI/CD & DevOps

Jenkins pipeline creation/management; shift-left mindset

GitOps repo experience; GitLab CI/CD integration

Containerised test execution patterns

Observability & reporting

Log/metric/trace validation in tests

Signal-based failure detection automation
Allure reporting; Grafana dashboard awareness

Test governance

FR/NFR traceability; entry/exit criteria; test case review for coverage

Risk-based prioritisation; layered test architecture

Cross-team RACI enforcement

Tools & ways of working

JIRA

Test tool selection/recommendations

Advanced test data factories
zephyr defect reporting and triage
Test tool selection/recommendations

Performance testing

Awareness/exposure

Licensing/config/dashboard ownership
JMeter/Gatling/NeoLoad experience

Data ingestion protocols

Awareness of formats/protocols

Identity warehousing exposure
SCIM/LDAP/OIDC/CSV exposure