HireHire › TCS jobs › Network Automation Engineer

Network Automation Engineer

Apply for this role or explore on the map →

Job Requirements*

1. Automation & Orchestration Engineering

·         Develop and maintain network automation platforms using industry‑standard orchestrators (e.g., Ansible, Terraform, Python,NSO, SaltStack, StackStorm).

·         Build scalable workflow engines to automate provisioning, configuration, compliance, and operational tasks.

·         Implement reusable automation modules, libraries, and pipelines with strong testing and validation.

 

2. Data Modelling

·         Create and maintain data models (YANG, JSON, YAML, XML) for configurations, inventory, and service definitions.

·         Map network business requirements to logical service models and templates.

  • Establish relationships between topology, inventory, and configuration datasets

 

3. Workflow Execution & Orchestration

·         Design and implement multi-stage workflows for provisioning, change management, upgrades, and rollback routines.

·         Integrate orchestrators with external systems (ITSM, CI/CD, CMDB, monitoring, IPAM).

·         Implement task scheduling, dependency handling, and distributed execution capabilities.

 

4. Standards, Governance, and Guardrails

  • Define automation development standards, coding guidelines, and peer‑review processes.
  • Implement guardrails for safe automation execution (pre‑checks, simulation modes, drift detection).
  • Ensure secure handling of credentials, API keys, secrets, and sensitive network data.

5. Compliance & Validation

  • Automate policy enforcement and configuration compliance using templates and rules (e.g., security baselines, golden configs).
  • Develop continuous-validation pipelines for posture checks, drift remediation, and audit reporting.

6. Inventory, Topology, and Versioning

  • Build and maintain dynamic inventory systems for devices, services, and configurations.
  • Implement configuration version control, differential analysis, and automated rollback mechanisms.

·         Maintain topology databases to support dependency mapping and impact assessments

7. Zero-Touch Provisioning (ZTP)