AI Orchestration / Platform Engineer

NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now. We are currently seeking a AI Orchestration / Platform Engineer to join our team in Hyderabad, Telangana (IN-TG), India (IN). 4. AI Orchestration / Platform Engineer Agent runtime | Model routing | LLMOps | CI/CD | Observability and reliability Number of positions 1 Level Senior / Lead Platform Individual Contributor Primary locations Hyderabad or Noida preferred; exceptional onshore candidates may be considered Target / alternate titles AI Platform Engineer; Agent Platform Engineer; LLMOps Engineer; GenAI Platform Engineer; AI DevOps Engineer; AI Site Reliability Engineer; ML Platform Engineer Core keywords agent orchestration, workflow engine, multi-agent systems, model gateway, model routing, LLMOps, platform engineering, Kubernetes, containers, CI/CD, infrastructure as code, policy as code, observability, OpenTelemetry, queues, state, retries, resilience, cost telemetry, SRE Recruiter red flags Traditional DevOps profile with no AI runtime understanding; framework-only orchestration without production platform depth; manual deployments; no observability or incident ownership; cannot explain model routing, state, retries, evaluation, or AI-specific controls. Role purpose Build and operate the orchestration and runtime capabilities that allow agentic applications to move reliably from development into production. The role will integrate agent workflows with existing cloud, security, policy, CI/CD, and observability capabilities, supporting multi-step execution, model routing, state, resiliency, evaluation, and production operations without rebuilding the client's established platform foundations. Client and delivery context • The client already has delivery pipelines, policy-based architecture, security controls, and production review processes. The engineer must integrate with and enhance those capabilities. • The platform should support multiple models, clouds, frameworks, and developer-productivity ecosystems without forcing avoidable lock-in. • The engineer will support shared patterns used across different business-process agents and may work across two parallel delivery tracks. • Platform work must be pragmatic and outcome-driven, with emphasis on enabling engineers to release and operate reliable agents quickly. Primary ownership • Agent workflow and runtime orchestration, including state, routing, queues, retries, timeouts, scheduling, persistence, and exception management. • Model gateway and routing patterns, provider abstraction, policy-based selection, fallback, rate limits, quotas, and cost controls. • CI/CD, environment promotion, configuration, secrets, infrastructure integration, release validation, rollback, and operational readiness. • Application and platform observability, reliability engineering, incident response, capacity, performance, and production support. Key responsibilities • Design and implement orchestration patterns for multi-step agents, multi-agent collaboration, deterministic workflows, long-running tasks, approvals, and event-driven execution. • Implement durable state, checkpoints, queues, retries, backoff, idempotency, timeouts, compensation, dead-letter handling, and recovery for agent workflows. • Integrate model gateways and routing logic that select models based on capability, sensitivity, latency, cost, availability, or policy requirements. • Build deployment and release patterns for agent services, orchestration components, prompts, tool definitions, configurations, and evaluation assets. • Integrate with existing CI/CD, infrastructure-as-code, policy-as-code, secrets, identity, container, and cloud-runtime capabilities. • Create observability for agent traces, model calls, tool calls, workflow state, token usage, cost, latency, errors, quality signals,