Key accountabilities

- Cloud standards and guardrails. Own the cloud standards set (landing zone, identity, networking, tagging, resilience, patching, backup) and keep each one current, versioned and mapped to a control framework.
- Policy as code. Turn standards into enforced Azure Policy and pipeline checks, so compliance is the default rather than a review outcome. Every standard has a named enforcement mechanism or a stated reason it has none.
- FinOps. Run cost allocation, showback, budgets and optimisation (rightsizing, reservations, savings plans). Own the monthly cost review with finance and service owners.
- Architecture review. Run the review route for recent patterns against a 10-working-day target. Publish decisions as reusable reference patterns so the same question is not reviewed twice.
- Exception management. Own the time-bound exception register: risk owner, expiry date and remediation plan on every entry, 5-working-day decision target.
- Risk and control evidence. Provide control evidence for internal audit, regulators and risk, including cloud KRIs, and own the cloud input to policy reviews.
- Enablement. Run office hours,



guidance and onboarding for app teams, and feed recurring friction to Cloud Engineering as golden-path backlog items.
- Technical leadership. Act as the senior technical voice on cloud governance. Mentor engineers across all three cloud teams and influence decisions without line authority.

Skills and experience Essential 12+ years in cloud infrastructure or architecture, with at least 3 as a senior or principal architect owning governance or platform standards, while still building hands-on Deep Azure knowledge: Azure Policy, management groups, Entra ID, landing zones and the Cloud Adoption Framework Hands-on policy as code: Azure Policy, Terraform, and pipeline-based compliance checks Practical FinOps: cost allocation models, reservations, and savings plans, and show back to non-technical owners Experience writing standards that engineers actually adopt, and retiring ones they don't Working knowledge of control frameworks (CIS, NIST or ISO 27001) and supplying audit evidence

📌 Cloud COE Lead (Bengaluru)
🏢 TRIGENT SOFTWARE PRIVATE
📍 Bengaluru