Interview scorecard template

IT Energy Efficiency Specialist interview scorecard

Pre-screening scorecard for IT Energy Efficiency Specialist candidates.

See AI scoring
engineering applied sciencedata centre puedcimenergy auditgreen it
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical depth

35% weight

Check command of PUE, DCiE and CUE calculation, ASHRAE thermal envelopes, server utilisation baselining, DCIM tooling, and power metering at PDU or branch circuit level.

Evidence to listen for

  • Explains the physics or mechanism behind their work, not just the tooling
  • Names the standards, tolerances, and constraints they designed against
  • Can defend a design decision under follow-up questions
  • Distinguishes what they personally engineered from what the team delivered

Five-point scoring guide

1
Poor

Cannot explain the fundamentals of their own stated specialism.

2
Needs Improvement

Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.

3
Satisfactory

Solid working knowledge for the role; depth thins out on edge cases.

4
Very Good

Strong command of the domain; explains trade-offs and defends decisions well.

5
Excellent

Quotes measured PUE before and after work, explains ASHRAE class limits, and distinguishes IT load savings from cooling savings.

02
Evaluation factor

Work that shipped

30% weight

Probe specific efficiency projects delivered: hot aisle containment, VM consolidation ratios, free cooling hours gained, UPS right-sizing, or kWh and carbon reductions signed off by finance.

Evidence to listen for

  • Names specific programmes, parts, or systems that reached production or field use
  • States their own scope inside the project
  • Can give measured outcomes: yield, cycle time, cost, failure rate
  • Explains what went wrong and what they changed

Five-point scoring guide

1
Poor

No delivered work; experience is coursework, lab-only, or purely observational.

2
Needs Improvement

Contributed to projects but cannot say what shipped or what their part was.

3
Satisfactory

Has delivered real work; outcomes described without numbers.

4
Very Good

Names shipped work and their scope, with some measured results.

5
Excellent

Names delivered projects with kWh, cost and tCO2e savings verified post-implementation, plus payback periods that survived scrutiny.

03
Evaluation factor

Diagnosis under uncertainty

20% weight

Test how they investigate unexplained energy drift: stranded capacity, ghost servers, oversized CRAC units, bad power factor, or metering that disagrees with utility bills.

Evidence to listen for

  • Describes a real failure they chased to root cause
  • Shows a method: isolate variables, reproduce, measure, eliminate
  • Distinguishes correlation from cause
  • Says what they ruled out and why, not only what the answer turned out to be

Five-point scoring guide

1
Poor

No diagnostic method; guesses or escalates immediately.

2
Needs Improvement

Trial and error with no structure; cannot explain how they narrowed the cause.

3
Satisfactory

Reasonable method on familiar problems; less structured on novel ones.

4
Very Good

Clear systematic approach with a real root-cause story.

5
Excellent

Describes isolating a phantom load through metering, workload traces and asset reconciliation rather than assuming the DCIM dashboard was correct.

04
Evaluation factor

Working across the org

15% weight

Assess how they win over infrastructure, facilities and procurement teams when efficiency changes touch uptime SLAs, refresh budgets, or ISO 50001 and CSRD reporting duties.

Evidence to listen for

  • Explains technical constraints to non-technical stakeholders without condescension
  • Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
  • Documents decisions so others can act on them
  • Takes review feedback without defensiveness

Five-point scoring guide

1
Poor

Cannot communicate outside their specialism; dismissive of other functions.

2
Needs Improvement

Communication gaps cause rework; avoids stakeholder contact.

3
Satisfactory

Works adequately with other teams; documentation is thin.

4
Very Good

Communicates clearly across functions; reliable collaborator.

5
Excellent

Shows evidence of aligning facilities and IT owners, negotiating change windows, and feeding verified data into sustainability disclosures.

Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards