DTICI_API_Testing_PrincipalConsultant_T7

Role Summary We are looking for a Senior Backend Engineer to build and scale our API management platform . You will be hands-on in a modern, cloud-native Azure environment, primarily developing microservices in Kotlin and managing their deployment lifecycles via Helm on Kubernetes. You will also directly interact with our infrastructure, writing Terraform and configuring API gateway policies to ensure secure, high-performance service delivery.

• Frontend UI testing

Test web applications, developer portals, administration portals, and documentation interfaces.

Responsibilities

• Create automated end-to-end UI tests for critical user journeys.
• Validate frontend behaviour across supported browsers.
• Test responsive behaviour for desktop, tablet, and mobile breakpoints where required.
• Validate form behaviour, validation messages, error states, loading states, and empty states.
• Test navigation, menus, authentication flows, logout, session expiry, and access-denied screens.
• Validate that frontend screens display the correct API data.
• Test filtering, pagination, search, sorting, table behaviour, dashboards, and export actions.
• Validate file downloads, API documentation views, Swagger/OpenAPI user flows, and portal workflows.
• Test UI behaviour when backend APIs are slow, unavailable, return empty data, or return errors.
• Validate accessibility basics:
• Keyboard navigation
• Focus behaviour
• Button and form labels
• Screen-reader-friendly controls
• Colour contrast
• Error-message visibility
• Identify UI regressions after frontend changes.

Required frontend testing skills

• Playwright or Cypress — essential.
• JavaScript or TypeScript — essential.
• HTML, CSS, browser DOM, browser developer tools.
• React frontend testing knowledge.
• Experience with:
• End-to-end tests
• UI regression tests
• Visual/state validation
• Cross-browser testing
• Responsive UI testing
• Accessibility testing basics
• Familiarity with React component testing using:
• React Testing Library
• Jest or Vitest

is preferred.

---

• Backend API testing

Test backend services, API gateway behaviour, API Management policies, and integration workflows.

Responsibilities

• Design and maintain automated API tests for REST services.
• Validate backend business logic through API-level tests.
• Test request validation, response structures, status codes, and error messages.
• Validate OpenAPI/Swagger contracts.
• Test API versioning and backward compatibility.
• Validate pagination, filtering, sorting, rate limits, caching, retries, and timeouts.
• Test API gateway routing and policy behaviour.
• Validate service-to-service integration workflows.
• Test failure conditions:
• Invalid input
• Missing required fields
• Invalid authentication
• Expired tokens
• Unauthorized user roles
• Backend dependency failures
• Timeout and retry behaviour
• Validate data consistency between UI, API, and persistence layer.
• Create API regression suites and smoke tests for release validation.

Required backend/API testing skills

• Strong REST API testing experience.
• OpenAPI / Swagger knowledge.
• JSON and HTTP protocol knowledge:
• HTTP methods
• Headers
• Status codes
• Cookies
• CORS
• Caching
• Authentication headers
• API automation tools such as:
• REST Assured with Java/Kotlin
• Karate
• Postman / Newman
• pytest + requests/httpx
• Supertest is useful for JavaScript services
• Ability to understand Kotlin/Java backend code sufficiently to:
• Review API changes
• Identify missing test cases
• Debug failed integration tests
• Work with developers on defect root cause
• SQL fundamentals for validating backend data.

---

• Authentication and authorization testing

DTAGAPI contains API-management, authorization, LDAP, API key, gateway, and security-related services. The tester must validate application security behaviour.

Responsibilities

• Test login and logout workflows.
• Validate session expiration and token refresh.
• Test OAuth2/OIDC and JWT-based authentication flows.
• Validate role-based access control.
• Validate API key creation, rotation, expiry, and invalidation workflows.
• Test LDAP-authentication flows where applicable.
• Ensure users cannot access data or administrative functions without permission.
• Validate secure error handling: errors must not reveal internal data, tokens, secrets, or stack traces.

Required skills

• OAuth2 / OpenID Connect basics.
• JWT structure and validation basics.
• API key and token handling.
• Role-based access control testing.
• OWASP Web and API Security fundamentals.

This is application-security validation, not an offensive penetration-testing role.

---

• Integration and end-to-end testing

Responsibilities

• Test complete workflows across frontend, backend APIs, gateway, identity, and data layers.
• Validate that portal actions correctly call backend APIs.
• Validate that changes made in the UI are correctly persisted and displayed after refresh.
• Test gateway-control-plane workflows.
• Validate API publishing, consuming, access management, and documentation workflows.
• Test mock server, API test-control-plane, and backend test repositories where applicable.
• Build stable test data and cleanup strategies for automated tests.

Example end-to-end scenarios

• A user signs in, receives correct role-based access, creates or updates an API configuration, and sees the result in the portal.
• An API consumer receives a valid API key and can access only permitted APIs.
• An expired or revoked API key is rejected by the gateway.
• An API definition published through the UI is available through API Management.
• A backend service failure is displayed correctly in the portal without leaking sensitive technical details.
• Search, filtering, pagination, and exports show data consistent with backend API responses.

---

• Database and data validation

Responsibilities

• Validate that frontend data matches backend API responses.
• Validate that backend APIs correctly persist and retrieve data.
• Write SQL queries for test verification and defect analysis.
• Validate data migration and backward-compatibility scenarios where relevant.
• Validate cache behaviour for application features using Redis or cache-sync services.
• Verify no duplicate, missing, or inconsistent records are created after workflows.

Required skills

• SQL query writing.
• PostgreSQL or relational database fundamentals.
• Understanding of transactions, indexing, data integrity, and migration testing.
• Basic understanding of caching concepts is preferred.

---

• Test automation framework ownership

Responsibilities

• Build maintainable frontend and backend test frameworks.
• Create reusable helpers for:
• Login/authentication
• API request construction
• Test-data setup
• Test-data cleanup
• UI navigation
• Common assertions
• Error validation
• Keep tests deterministic and reduce flaky tests.
• Categorize tests clearly:
• Unit tests
• Component tests
• API tests
• Integration tests
• End-to-end tests
• Smoke tests
• Regression tests
• Maintain test reports and failure diagnostics.

---

Required Skills (Must-Have)

• ·Strong proficiency in Kotlin within the JVM ecosystem (experience with Spring Boot or Quarkus is essential).
• ·Hands-on experience deploying and managing services on Kubernetes using Helm.
• ·Proven ability to write and manage Infrastructure as Code using Terraform (specifically for Azure resources).
• ·Direct experience with Azure APIM, including writing gateway policies (C#/XML) and configuring routing.
• ·Deep understanding of API Gateway patterns (rate limiting, auth, routing) and OAuth2/JWT authorization models.
• ·Familiarity with the building commercial B2B APIs.

Preferred Skills (Should-Have)

• ·Proficiency in Python for scripting, tooling, and building runbooks.
• ·Experience configuring and maintaining pipelines in GitHub Actions and Azure Pipelines.
• ·Familiarity with Open Telemetry for tracing and observability.
• ·Strong operational knowledge of Redis.

Nice-to-Have

• ·Experience with Go (specially building Terraform providers) or Rust.
• ·Familiarity with TypeScript/React for occasional work on internal developer portals.
• ·Exposure to Scala for automation tooling.