01Overview
Detailed requirement as below :
1. Non-Negotiable: AKS (Azure Kubernetes Service)
- Depth Required: Must have managed production clusters (not just learning environments).
- Specific Skills: Experience with Azure CNI, HPA/VPA, Ingress Controllers (Nginx/AGIC), and Node Pool lifecycle management.
- The Test: They must be able to explain how they handle a \"Pod Pending\" state or an \"ImagePullBackOff\" in a locked-down enterprise network.
2. Tooling Priority: Flux CD & Helm
- GitOps: We need Flux CD experience. If they only know \"Push\" pipelines (Jenkins/ADO), they are a secondary fit. We want someone who understands automated reconciliation loops.
- Helm: Must be able to author and troubleshoot Helm charts, not just run helm install.
3. Observability: Dynatrace
- Requirement: Hands-on with Dynatrace.
- Competency: Setting up Service Level Objectives (SLOs), Management Zones, and using Davis AI for root cause analysis. (Generic Prometheus/Grafana knowledge is positive but Dynatrace is the target).
4. Infrastructure as Code: Terraform
- Level: Advanced. Must be comfortable with Terraform State management, importing manual resources into code, and building reusable modules.
5. The \"Anti-Profile\" (What we DO NOT want):
- AWS Specialists: Do not send candidates whose primary experience is EKS/AWS with only \"basic\" Azure exposure.
- Theoretical/Reading Candidates: We will immediately reject anyone who appears to be reading from a screen or providing textbook definitions during the L1. .
