FinOps -12 Months
Posted
Description
Job Title FinOps
Minimum experience 5+ years
Duration 12 Months
Location Qatar
Minimum experience 5+ years
Duration 12 Months
Location Qatar
- Role Expectation
- Main Capabilities Cloud financial governance across Azure and GCP Cost allocation, tagging, budgets and forecasting FinOps reporting, showback and unit economics Cost anomaly detection and optimization backlogs Commitment, reservation and consumption analysis Engineering, finance, procurement and vendor coordination
- Required Experience
- Core Responsibilities Own hands-on technical delivery for the assigned FinOps scope Translate approved requirements and architecture into implementable designs, configurations, code, controls or delivery artefacts Apply the defined capabilities using secure, maintainable, testable and supportable engineering practices Identify technical risks, dependencies, gaps and decisions early, and drive them to closure with accountable stakeholders Support end-to-end validation, production readiness, troubleshooting and controlled handover Maintain version-controlled documentation, decisions, runbooks and knowledge-transfer material
- Expected Outputs Role-specific technical designs, implementation artefacts or operational deliverables Documented decisions, assumptions, dependencies, risks and acceptance evidence Reusable standards, templates, code, configurations, runbooks or checklists Testing or validation evidence and production-readiness inputs Structured technical documentation and knowledge transfer
- Technical Assessment Candidate selection should include a structured technical discussion based on recent delivery examples. The assessment should validate genuine hands-on depth in cloud financial governance across Azure and GCP, cost allocation, tagging, budgets and forecasting, finOps reporting, showback and unit economics, cost anomaly detection and optimization backlogs, commitment, reservation and consumption analysis. The candidate should be able to explain personal contribution, design trade-offs, control and failure handling, testing or validation evidence, and how delivered solutions were supported in production.
- Role Boundaries The role is accountable for technical delivery within the assigned scope but does not replace business product ownership, formal architecture or security approval, security risk acceptance, platform ownership or vendor contractual accountability. Production changes must follow approved engineering, security, release and operational processes.
Skills
Sign in to read and join the discussion.