Infrastructure Automation Engineer Role

The Infrastructure Automation Engineer will create tools that simplify deployment and management of Ooto Neural OS clusters. You will design infrastructure-as-code systems, cluster provisioning automation, and operational tooling for enterprise customers.

Responsibilities

• Implement automated cluster deployment pipelines.
• Build infrastructure monitoring and alerting systems.
• Develop tools for sovereign node lifecycle management.

Your automation work will enable customers to operate Neural OS at global scale.

Automation Focus - Infrastructure as code

Ooto clusters require sophisticated orchestration across cloud providers, on-premises hardware, and edge deployments. You'll build Terraform modules, Kubernetes operators, and custom tooling that make sovereign infrastructure accessible to operations teams.

Core Technologies - Kubernetes and infrastructure tooling

• Design Helm charts for Neural OS component deployment.
• Build admission controllers that enforce sovereignty policies.
• Develop custom resource definitions for mesh configuration.
• Implement GitOps workflows for declarative cluster management.
• Create observability dashboards for cluster health monitoring.

Deployment Patterns - Multi-cloud sovereign clusters

Support hybrid deployments spanning AWS, Azure, GCP, and on-premises.

1. Abstract cloud-specific APIs behind unified interfaces.
2. Implement network policies that enforce data residency.
3. Design backup and disaster recovery automation.

Operational Excellence - Reduce toil through automation

Identify repetitive operational tasks and build automation to eliminate manual processes. Develop runbooks and incident response playbooks. Create self-service tools that empower customers to manage infrastructure independently.

Customer Enablement - Support global deployments

Work with customer SRE teams to integrate Ooto into existing infrastructure. Provide technical guidance on best practices for cluster architecture. Build documentation and training materials for operational procedures.

"The best automation is invisible: reliable deployments, consistent state, and predictable operations."