Sustainable technology and Green ops role profiles
Examples of roles, responsibilities, their contributions and SFIA skills
Each profile gives the level of responsibility, typical job titles, the role’s purpose, its main responsibilities and its core skills. It closes with three parts:
- Accountable for: what the role answers for
- Typical failure: what commonly goes wrong, because that is where GreenOps work most often stalls
- How SFIA helps address this: how the combination of skills, levels of responsibility and allocation of accountability can reduce the risk
SFIA cannot guarantee an organisational outcome. It can help an organisation define the capability, authority, interfaces and accountability needed, but not ensure those responsibilities are exercised well.
The failures are not all of the same kind, and each is labelled with one of three types.
| Type | What has gone wrong | What helps |
|---|---|---|
| Capability | The professional practice is missing or weak, for example efficiency is never tested | The appropriate skill at the appropriate level |
| Integration | The capabilities exist but do not join up, for example facilities and IT each hold half of the evidence | A combination of skills, responsibilities and working relationships across functions |
| Accountability | People can see the issue but someone else controls the decision | Correct allocation of decisions across SFIA levels, particularly levels 5, 6 and 7, rather than more GreenOps skill |
This gives organisations a way to diagnose whether a sustainability problem is a capability gap, an integration gap or an accountability gap, which is a stronger proposition than simply saying SFIA contains relevant skills.
These examples describe different contributions to sustainable technology and GreenOps: analysing evidence, designing and operating services, managing demand and investment, and providing leadership and coordination.
The contributions may sit in existing roles, specialist roles or combined responsibilities. Their location depends on the organisation. The groups help readers navigate the examples; they do not define departments, reporting lines or exclusive boundaries between roles.
SFIA provides professional skills and levels of responsibility relevant to these contributions. The examples focus on sustainable technology work and may describe only part of a wider job.
-
The examples are grouped by their contribution rather than by whether they where they sit organisationally. Typcial organisational association is also supplied – but these should always be considered specific to the organisations own structue and context.
| Contribution group | Role or contribution | Main contribution to sustainable outcomes | Typical organisational association |
|---|---|---|---|
| Analysing performance and evaluating evidence | 1. GreenOps analyst | Analyses consumption and utilisation; identifies and implements agreed improvements | Technology operations, FinOps or sustainability |
| 2. Senior GreenOps analyst or specialist | Develops methods and baselines; evaluates evidence quality | Technology, FinOps or sustainability | |
| Designing and operating services and infrastructure | 4. Infrastructure and cloud operations manager | Manages infrastructure efficiency, capacity and operational changes | Usually a technology function |
| 5. Solution architect | Evaluates environmental consequences of design choices and trade-offs | Usually technology or architecture | |
| 6. Software engineering lead | Builds resource efficiency into software design, development and testing | Usually technology or engineering | |
| 12. Estates or data centre facilities manager | Manages power, cooling, water and facilities evidence | Estates, facilities, data centre operations or technology | |
| Managing demand, investment and asset lifecycles | 10. Business service owner | Challenges demand and agrees service requirements and benefits | The function accountable for the service, which may include technology |
| 9. Finance business partner or FinOps lead | Evaluates cost and environmental implications; makes consumption visible | Finance, technology or a cross-functional FinOps practice | |
| 8. Technology procurement lead | Connects environmental requirements to purchasing, contracts and asset lifecycle decisions | Procurement, sometimes embedded within technology | |
| Leading and coordinating sustainable practice | 3. GreenOps lead | Coordinates practice, prioritises improvements and connects findings to decision owners | Technology, sustainability or a cross-functional remit |
| 11. Sustainability lead | Connects technology’s contribution to sustainability policy, reporting and commitments | Sustainability, corporate responsibility or a cross-functional remit | |
| 7. Accountable technology owner | Sets direction, allocates resources and takes accountability for technology outcomes | Technology leadership or wider executive leadership |
Sustainable technology and GreenOps role profiles
Level 3, apply. Typical titles: cloud optimisation analyst, FinOps analyst, infrastructure analyst, sustainable IT analyst.
Turns operational data into findings teams can act on, and gets idle, oversized and inefficient resources fixed.
- Collects and validates energy, utilisation and consumption data, labelling what is measured and what is modelled
- Identifies idle, oversized and out-of-hours resources and raises changes to remove them
- Applies agreed optimisations within set limits, such as scheduled shutdown of non-production environments
- Reports each finding with a named owner
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Infrastructure operations | ITOP | 3 | Identifies idle and oversized resources, applies agreed rightsizing and scheduling |
| Measurement | MEAS | 3 | Collects and validates consumption data and records its source and quality |
| Data analytics | DAAN | 3 | Analyses consumption trends and anomalies by service |
| Capacity management | CPMG | 3 | Tracks provisioned capacity against actual use |
SUST starts at level 4, so this role has no sustainability-labelled skill. Its work is still described by SFIA 9: ITOP guidance covers monitoring infrastructure for its impact on sustainability, and CPMG guidance covers the sustainability of service components and the continuous optimisation of resource utilisation.
Accountable for: the accuracy of the analysis, and acting on findings within agreed limits.
Typical failure (accountability): the analyst produces dashboards that nobody owns.
How SFIA helps address this: ITOP, MEAS, DAAN and CPMG at level 3 define responsibility for accurate analysis and agreed optimisation. Each finding is then connected to a named owner at level 5 or 6 with authority over the capacity, budget, service or standard involved.
Level 4, enable. Typical titles: senior FinOps analyst, GreenOps specialist, technology sustainability data analyst.
Owns the methods and baselines the analysts work to, and tests the evidence others supply before anyone relies on it.
- Builds and maintains baselines for energy, utilisation and carbon, with the method recorded
- Validates calculation methods and data sources, and states where figures are modelled
- Tests supplier and cloud provider evidence before it is used in reporting or decisions
- Guides analysts and agrees improvement priorities with service and infrastructure teams
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Sustainability | SUST | 4 | Applies sustainability methods and standards to technology data and practices |
| Measurement | MEAS | 4 | Defines measures, baselines and calculation methods, and controls their quality |
| Data analytics | DAAN | 4 | Finds the drivers behind consumption trends and tests whether improvements held |
| Capacity management | CPMG | 4 | Sets utilisation baselines and flags where capacity runs ahead of demand |
| Supplier management | SUPP | 4 | Tests the granularity and method of supplier and provider data |
SUPP4 fits where the specialist engages suppliers directly on data quality. Where the role mainly tests supplier evidence without managing the relationship, data management (DATM) or quality management (QUMG) at level 4 may describe the work better.
Accountable for: method and data quality in their area, including saying where figures are modelled.
Typical failure (capability): the specialist ends up assembling the annual report instead of fixing the method. Baselines drift and nobody can explain why the numbers moved year on year.
How SFIA helps address this: SUST4, MEAS4, DAAN4 and CPMG4 make ownership of methods, baselines and data quality explicit. Level 4 is about enabling consistent practice for others, not just collecting figures, so the role description itself protects time for method work.
Level 5, ensure and advise. Typical titles: head of sustainable IT, GreenOps lead, IT sustainability manager, FinOps and sustainability lead.
Owns the GreenOps practice for an estate or organisation, including the measurement approach, baselines, priorities, business cases and the evidence behind them.
- Sets measurement standards and keeps an evidence register that separates measured from modelled data
- Prioritises improvements on cost, carbon and risk, and builds the business cases
- Takes findings to the people who own the decisions in finance, procurement, estates and the business
- Advises the accountable owner and the sustainability lead on what the data can and cannot support
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Sustainability | SUST | 5 | Advises on technology sustainability priorities and compliance |
| Measurement | MEAS | 5 | Designs measurement across the estate and sets data quality standards |
| Capacity management | CPMG | 5 | Makes sure capacity plans carry utilisation targets and challenge headroom |
| Benefits management | BENM | 5 | Defines and tracks benefits in energy, cost and carbon avoided |
| Stakeholder relationship management | RLMT | 5 | Works across finance, procurement, estates and service owners to get decisions made |
| Data management | DATM | 5 | Governs sustainability data as an organisational asset, with ownership, lineage and retention defined |
Accountable for: the credibility of technology sustainability data, and getting findings to the people who decide.
Typical failure (accountability): the lead has responsibility without authority, so findings cannot influence investment, architecture or procurement decisions.
How SFIA helps address this: level 5 provides accountability for significant outcomes and authoritative advice, and RLMT5 connects the role to decision owners. A named sponsor at level 6 or 7 and a formal route into investment, architecture and procurement governance provide the authority the lead does not hold.
Level 5, ensure and advise. Typical titles: head of infrastructure, cloud platform manager, data centre operations manager, site reliability engineering manager.
Runs the IT estate efficiently across on-premises, colocation and cloud, including the capacity and density demands of AI infrastructure.
- Sets utilisation and efficiency standards, including accelerator utilisation for AI workloads
- Plans capacity against real demand rather than provisioned headroom
- Makes environmental impact part of change assessment
- Provides IT load data that the estates or facilities manager combines with facility data
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Infrastructure operations | ITOP | 5 | Sets efficiency standards and removes idle capacity across environments |
| Infrastructure design | IFDN | 5 | Plans workload placement, rack density and cooling constraints, and the different demands of training and inference |
| Capacity management | CPMG | 5 | Plans capacity against real demand |
| Change control | CHMG | 5 | Makes environmental impact part of change assessment |
Accountable for: the operational efficiency of the IT estate and the accuracy of IT load data.
Typical failure (integration): estates hold the facility data, IT holds the IT data, and nobody joins them. PUE then gets reported as an annual portfolio average that hides the worst sites.
How SFIA helps address this: ITOP5, CPMG5, IFDN5 and CHMG5 establish operational accountability for infrastructure efficiency. Defining the interface with the estates or facilities manager (DCMA and MEAS) as a shared responsibility makes joining IT load and facility evidence part of both roles rather than neither.
Level 5, ensure and advise. Typical titles: solution architect, cloud architect, and enterprise architect at levels 5 to 7.
Makes design decisions that fix a service’s resource profile for its lifetime, so shapes the footprint before anything is built.
- Includes energy, utilisation and lifecycle impact in design trade-offs alongside cost, performance and resilience
- Chooses placement and platforms using evidence on provider data, power density and cooling constraints
- Sets efficiency requirements that engineering and testing can check
- Records impact estimates in architecture decisions, stating what is measured and what is modelled
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Solution architecture | ARCH | 5 | Makes environmental impact one of the trade-offs in every solution design |
| Enterprise and business architecture | STPL | 5 | Builds efficiency and lifecycle principles into architecture standards |
| Infrastructure design | IFDN | 5 | Selects hosting, placement and platform with density and cooling in view |
| Capacity management | CPMG | 4 | Sizes designs against expected demand rather than worst-case assumptions |
Accountable for: the environmental consequences of design choices within the agreed scope.
Typical failure (integration): the team treats sustainability as a review checkbox after the design is fixed, or settles it by picking a fashionable design pattern without evidence about the workload.
How SFIA helps address this: ARCH5, STPL5, IFDN5 and CPMG4 make resource use and environmental consequences part of architecture decisions and trade-offs at the point where choices can still be changed.
Level 5, ensure and advise. Typical titles: engineering manager, head of software engineering, platform engineering lead, principal engineer.
Makes sure software uses no more compute, storage and network than the service needs.
- Sets coding and design standards for resource efficiency
- Builds efficiency tests into delivery pipelines and tracks results between releases
- Removes waste in non-production environments, such as idle test environments and oversized builds
- Challenges features and data retention that add load without adding value
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Software design | SWDN | 5 | Sets design standards that limit compute, storage and data movement |
| Programming/software development | PROG | 5 | Makes efficiency part of code review and engineering practice |
| Non-functional testing | NFTS | 5 | Tests resource use against efficiency requirements, release by release |
| Systems and software lifecycle engineering | SLEN | 5 | Designs pipelines and environments that start on demand and shut down when idle |
Accountable for: the efficiency of the software the team ships.
Typical failure (capability): nobody tests efficiency, so regressions only show up months later as a larger cloud bill.
How SFIA helps address this: SWDN5 and PROG5 establish design and engineering responsibility for efficiency. NFTS5 makes resource efficiency testable, since SFIA 9 already lists it among the qualities non-functional testing addresses, and SLEN5 builds the practice into environments and delivery pipelines.
Level 7, set strategy, inspire and mobilise. Typical titles: CIO, CTO, chief digital officer.
Owns technology’s environmental performance as part of technology strategy, investment and risk.
- Sets targets and constraints for technology, including power availability and AI growth
- Makes sure every decision in the decision table has a named owner
- Requires assurance behind any external claim about technology’s footprint
- Links efficiency to the objectives of the people who control demand and budgets
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Strategic planning | ITSP | 7 | Sets technology strategy with sustainability targets and constraints |
| Governance | GOVN | 7 | Sets decision rights and accountability, and requires assurance behind external claims |
| Portfolio management | POMG | 7 | Prioritises the portfolio on cost, carbon, risk and value together |
| Financial management | FMIT | 6 | Owns the financial treatment of technology, including carbon-related cost |
FMIT guidance says the skill typically applies to dedicated financial management roles rather than to managers of operational budgets. Organisations should include it only where the technology owner genuinely carries that capability. In many organisations it will sit with the finance business partner or finance leader instead.
Accountable for: outcomes against commitments.
Typical failure (accountability): the owner delegates sustainability to a specialist team, which treats it as reporting. Targets then have no link to investment decisions or to the objectives of the people who control demand.
How SFIA helps address this: ITSP7, GOVN7 and POMG7 place sustainability within strategy, decision rights and portfolio prioritisation. This is where SFIA makes the distinction between specialist advice and enterprise accountability clearest.
Roles outside technology
Level 5, ensure and advise. Typical titles: category manager for technology, IT procurement manager, head of technology sourcing.
Uses buying power to reduce impact, starting with whether to buy at all.
- Challenges the need before sourcing, including extended refresh, refurbished equipment and not buying
- Evaluates options on whole-life cost and impact rather than purchase price
- Secures contractual rights to granular emissions data, audit rights and end-of-life terms
- Tests supplier evidence and holds suppliers to improvement plans after award
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Sourcing | SORC | 5 | Sets criteria on whole-life cost and impact, and considers extended refresh, refurbished equipment and not buying |
| Supplier management | SUPP | 5 | Tests supplier evidence, including whether figures are activity-based or spend-based |
| Contract management | ITCM | 5 | Secures data rights, audit rights and end-of-life terms such as chain of custody and evidence of reuse |
| Asset management | ASMG | 5 | Manages lifecycle extension, reassignment and disposal, with embodied carbon in the decision |
Accountable for: sustainability requirements in contracts that are specific, measurable and enforced after award.
Typical failure (integration): sustainability criteria become a weighted questionnaire that the supplier’s marketing team answers. Nobody checks anything after award, data rights are never secured, and reporting relies on whatever the supplier chooses to publish.
How SFIA helps address this: SORC5 sets sustainability expectations during sourcing, ITCM5 makes them contractual (SFIA 9 guidance already covers integrating sustainability into contract management), SUPP5 monitors supplier performance against them and ASMG5 carries lifecycle considerations into use, reuse and disposal. Treating these as one chain rather than four separate activities is what keeps the requirements alive after award.
Level 5, ensure and advise. Typical titles: IT finance business partner, FinOps lead, technology business management lead.
Brings cost and carbon together so investment and consumption decisions see both.
- Allocates cost and carbon to the services and business units that consume them
- Builds whole-life cost and carbon, including embodied carbon, into business cases
- Reflects energy prices, capacity growth and refresh policy in forecasts
- Challenges carbon figures that have been derived from spend
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Financial analysis | FIAN | 5 | Analyses cost and carbon together, knowing which inputs are measured and which are modelled |
| Cost management | COMG | 5 | Allocates cost and carbon to the services and business units that consume them |
| Budgeting and forecasting | BUDF | 5 | Reflects energy, capacity growth and refresh policy in forecasts |
| Investment appraisal | INVA | 5 | Puts whole-life cost and carbon, including avoided spend, into business cases |
Accountable for: business cases that are honest about impact, and consumers seeing what they use.
Typical failure (capability): the finance team derives carbon from spend. A price cut then looks like an emissions reduction, and business cases ignore embodied carbon because it never appears in operating cost.
How SFIA helps address this: FIAN5, COMG5, BUDF5 and INVA5 make assumptions, models, whole-life implications and consumption visible in financial analysis and decision support, rather than reducing sustainability to a single proxy measure.
Level 6, initiate and influence. Typical titles: product owner, head of digital service, business application owner, service owner. In smaller organisations using the embedded pattern, the service owner may work at level 5, with level 6 accountability held by the director above them.
Owns a business service and the demand it places on technology.
- Decides whether services, features and data are still needed, and retires those that are not
- Sets availability and retention requirements knowing their cost and impact
- Accepts showback of the service’s cost and carbon, and acts on it
- Owns benefits that include reduced consumption
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Demand management | DEMM | 6 | Challenges whether demand is needed, and retires low-value services, features and data |
| Portfolio management | POMG | 6 | Balances value, cost and impact across the services they own |
| Benefits management | BENM | 6 | Owns benefits that include reduced consumption |
| Stakeholder relationship management | RLMT | 6 | Agrees service levels and trade-offs with technology, such as the cost of higher availability |
POMG6 fits where the service owner manages a set of services as a portfolio. Two alternatives are worth considering: product management (PROD), which covers the full lifecycle through decline and retirement, and service level management (SLMO), which covers agreeing service level targets and already recognises sustainability targets as a factor in service delivery.
Accountable for: the demand their service creates.
Typical failure (accountability): the service owner treats demand as fixed. Availability defaults to the highest tier, the service keeps data indefinitely, and IT ends up optimising services that should have been reduced or retired.
How SFIA helps address this: DEMM6 makes demand itself a management concern, POMG6 and BENM6 support decisions on value and benefits, and RLMT6 provides the influence to agree trade-offs between the business and technology.
Level 6, initiate and influence. Typical titles: head of sustainability, ESG reporting lead, sustainability director.
Owns the organisation’s sustainability commitments and what it reports externally, including technology’s share.
- Sets the reporting approach and the methods technology data has to meet
- Agrees with the accountable technology owner what technology contributes to organisational targets
- Makes sure external claims about technology are backed by evidence and assurance
- Brings technology into climate risk assessment and transition planning
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Sustainability | SUST | 6 | Sets sustainability policy and commitments that technology works within |
| Governance | GOVN | 6 | Operates oversight of reporting, claims and the evidence behind them |
| Measurement | MEAS | 5 | Sets calculation methods and data quality expectations for reported figures |
| Stakeholder relationship management | RLMT | 6 | Works with technology, finance and the board on targets and disclosure |
| Data management | DATM | 5 | Sets ownership and lineage for reported data, so every external claim can be traced to its source |
Accountable for: the integrity of what the organisation says publicly about its footprint.
Typical failure (integration): technology figures arrive once a year as a spreadsheet with no view of the method behind them. Estimates become reported facts, and nobody in technology knows which figures matter.
How SFIA helps address this: SUST6 and GOVN6 establish policy and oversight, while MEAS5 and DATM5 define measurement quality, ownership, lineage and traceability, so technology data reaches reporting with its method attached.
Level 5, ensure and advise. Typical titles: estates manager, data centre facilities manager, critical environment manager.
Runs the buildings, power, cooling and water that technology depends on, directly or through a colocation provider.
- Reports site-level PUE, WUE and CUE, with IT load and facility overhead measured separately
- Plans power and cooling capacity with the infrastructure and cloud operations manager, including higher rack densities for AI
- Manages colocation and utility contracts, including the energy and water data they provide
- Finds facility overhead that can be cut, such as cooling set points and unused space
| Skill | Code | Level | Applied in this role |
|---|---|---|---|
| Facilities management | DCMA | 5 | Manages site power, cooling and water, and the metrics that describe them |
| Supplier management | SUPP | 4 | Manages colocation and utility providers and the data they supply |
| Budgeting and forecasting | BUDF | 4 | Forecasts energy and water cost against capacity plans |
| Measurement | MEAS | 4 | Measures IT load and facility load separately, at site level |
Accountable for: the efficiency of the facility and the accuracy of site data.
Typical failure (capability): facility metrics come from annual meter readings or a provider’s headline figure. The site looks efficient on paper while cooling runs for IT load that no longer exists.
How SFIA helps address this: DCMA5 already includes monitoring usage against sustainability targets as part of facilities management. MEAS4 establishes credible site-level measurement, and SUPP4 and BUDF4 connect provider evidence and capacity forecasts to management decisions.
Skills used as core skills in these profiles
Across the twelve profiles, 30 skills from the view are used as core skills. They are core for these prototype profiles only. Other organisations, with different roles and structures, may rely on other skills in the view, so this is a starting point rather than a normative core and supporting classification.
| View category | Skills used as core in these profiles | Profiles using them |
|---|---|---|
| Strategy, governance and accountability | SUST, ITSP, GOVN, POMG, RLMT | 2, 3, 7, 10, 11 |
| Value, financial and investment management | FMIT, FIAN, COMG, BUDF, INVA, BENM, DEMM | 3, 7, 9, 10, 12 |
| Sustainable architecture, planning and design | STPL, ARCH, IFDN, SWDN, PROG, NFTS, SLEN | 4, 5, 6 |
| Green operations and optimisation | ITOP, CPMG, DCMA, CHMG | 1, 2, 3, 4, 5, 12 |
| Sustainability data, reporting and assurance | MEAS, DAAN, DATM | 1, 2, 3, 11, 12 |
| Sustainable sourcing, supplier and asset lifecycle | SORC, SUPP, ITCM, ASMG | 2, 8, 12 |
Measurement and capacity management recur most, each in five profiles, because GreenOps depends on measuring consumption properly and sizing capacity to real demand. Stakeholder relationship management appears in three, since findings change nothing until the people who own the decision act on them. The capability and change skills matter for building the practice, but no profile here depends on them as a core skill.