Sr. FinOps Engineer

Job Overview

Function Cloud & Data Engineering.

Company:
Hitachi Digital Services, a global digital solutions and transformation business with a bold vision of our world’s potential.

Certified from Fin Ops.org;
Fin Ops for DC knowledge; DCIM; CMDB / asset DB; hypervisor metrics; power monitoring; contracts & licenses management.

Deliver hands‑on Fin Ops engineering for the organisation’s on‑premises estate, working under the Fin Ops Architect to implement cost visibility, data integration, reporting, and optimisation initiatives following the Fin Ops.org framework. Serve as the primary onshore engineering resource who connects data sources, builds dashboards, analyses usage patterns, identifies savings, and supports governance processes. Collaborate with all Fin Ops personas to embed cost accountability into day‑to‑day operations.

As the onshore engineer, this role acts as the bridge between stakeholders (finance, engineering, operations) and the offshore engineering capacity, ensuring quality, context, and alignment with business priorities.

• Cost Visibility — Gain full visibility of on‑premises infrastructure, licensing, and operational costs by establishing comprehensive data collection and integration from identified sources.
• Data Source Identification & Setup — Identify, agree upon, and integrate all relevant cost data sources including CMDB, asset management, licensing portals, procurement systems, and infrastructure monitoring tools.
• Fin Ops Maturity Baselining — Assess current Fin Ops maturity against the Fin Ops.org maturity model (Crawl → Walk → Run), identifying gaps and opportunities across tagging, savings, and cost governance.
• Tagging & Allocation Gaps — Identify and remediate gaps in cost allocation, tagging, and labelling across on‑premises assets to enable accurate chargeback, showback, and cost attribution.
• Savings Identification — Discover potential savings opportunities through licence optimisation, hardware rightsizing, capacity rebalancing, decommissioning, and vendor renegotiation.
• Cost Governance Gaps — Assess and strengthen cost governance processes including approval workflows, budget controls, anomaly detection, and policy enforcement.
• Data Normalisation — Normalise cost data from disparate sources into a unified cost model, enabling consistent reporting across business units, environments, and service categories.
• Usage, Pattern & Licence Analysis — Analyse infrastructure utilisation patterns, workload distribution, peak/off‑peak trends, and software licence usage to identify waste and optimisation opportunities.
• Cost Modelling & Economics — Define unit economics, cost‑per‑service models, TCO calculations, and amortisation schedules for on‑premises infrastructure to enable informed decision‑making.
• Implementation Roadmap — Develop a prioritised roadmap of quick‑wins (0–3 months), mid‑term initiatives (3–6 months), and long‑term transformations (6–12 months) based on value and feasibility.
• Reporting & Dashboards — Design and recommend live/near‑real‑time cost dashboards with drill‑down capabilities, trend analysis, anomaly alerts, and executive reporting views.

• Implement cost data integration from identified sources: CMDB, asset management, procurement systems, licence portals, and monitoring tools — building automated data pipelines where possible.
• Build and maintain data normalisation processes to unify cost data from disparate systems into a consistent, queryable format for reporting and analysis.
• Develop and maintain Fin Ops dashboards and reports: executive cost views, business‑unit breakdowns, trend analysis, anomaly alerts, and licence utilisation reports using Power BI, Tableau, or Grafana.
• Conduct usage, pattern, and licence utilisation analysis: identify under‑used licences, oversized hardware, idle resources, peak/off‑peak patterns, and capacity rebalancing opportunities.
• Support the Fin Ops Architect in maturity assessments: gather evidence, document current‑state practices, score maturity against Fin Ops.org’s Crawl/Walk/Run model, and track improvement progress.
• Implement tagging and cost allocation…