Senior Cloud Infrastructure Engineer (DNS, NTP, LDAP, Linux)
Miratech (company site, opens in a new tab)5+ yrsDelhi NCRRemoteDirect career pageEst. 18–30 LPA
Posted 20h ago
Reach people at Miratech
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Miratech you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own implementation and support of multi-region DNS across private and public cloud, including enterprise DDI and cloud DNS services.
- Build automated infrastructure provisioning and CI/CD workflows; maintain monitoring, alerting, high availability, disaster recovery, and rollback capabilities.
- Support production DNS, NTP, and LDAP services, including on-call incident response, troubleshooting, and root-cause analysis.
Minimum Requirements
- Work Experience Required: 5+ years managing global DNS, NTP, and LDAP systems on Linux.
- Strong Linux systems engineering and hands-on experience implementing OpenLDAP and NTP services.
- Infrastructure-as-Code proficiency with Ansible, Terraform, or Pulumi; experience with Python, Bash, or Go scripting and CI/CD pipelines.
- Experience with Infoblox DDI or comparable enterprise DNS services, and supporting mission-critical 24x7 production environments.
Ideal Candidate Profile
- Has operated large-scale, multi-region DNS and infrastructure services across private/public cloud and enterprise environments.
- Can combine Linux, networking, virtualization, and storage knowledge to diagnose infrastructure performance and reliability issues.
- Has built or maintained high-availability or multi-region OpenStack clusters; exposure to observability, GitOps, and security compliance is also relevant.