Seven areas separate candidates who understand DC fast charging uptime SLAs from those who only have general EV experience: estate scope, technical diagnosis across hardware, software, communications and power, incident response from alert to restoration, SLA literacy on definitions and exclusions, supplier coordination, improvement work, and role fit. Test each through a real outage the candidate owned, not the terms on their CV.
That distinction is the whole hiring problem. DC fast charging (DCFC) has drawn in installers, field technicians and network operations staff who all describe their background as "EV charging experience." Some of them commissioned equipment and moved on. Others carried live availability targets and answered for every minute a charger sat down. Your job description and your interview need to separate the two before you make an offer.
What does "DC fast charging" and "uptime" actually mean for this hire?
DC fast charging equipment, sometimes called EVSE (Electric Vehicle Supply Equipment) in job postings and CVs, delivers DC power directly at the charging station rather than relying on the vehicle's onboard converter. It is used wherever fast turnaround matters: public highway networks, commercial sites, fleet depots.
Uptime is not one number. Before you write the role, decide how your organization measures it: at the charger, the connector, the site or the network level. A charger connected to the backend can still fail to start a session, so connectivity and usable availability are not the same thing. You also need your reporting period and your downtime exclusions settled, because a candidate's SLA experience only means something against a definition you can name back to them.
The consequence of downtime changes by setting too. A failed charger at a fleet depot can stop vehicles from running their shift. A failed charger on a high-turnover commercial site loses walk-up revenue and reputation. A failed charger at a lower-traffic site may tolerate a longer restoration window. Write the brief for the environment you actually operate, not for DC fast charging in general. If you are staffing the wider team around this kind of hire, our EV Charging Operations Teams work covers that broader build.
How do I tell installation experience from live-operations experience?
Start with the operating context, not the CV keywords. Before you screen anyone, be able to state:
• The charging hardware and power range in use
• Whether power is shared across multiple charge points or dedicated per unit
• The connector standards (such as CCS or NACS) and vehicle population served
• The operating model: public network, fleet, depot or commercial site
• The parties involved: charger manufacturer, charge point management platform, field-service provider, utility, telecoms provider, payment provider and site owner
• The uptime definition, reporting period, exclusions and service commitments that apply to the role
With that context fixed, read CVs and job history for four separate things rather than one blended impression:
DC fast charging infrastructure. Look for named hardware, connectors, high-voltage systems, switchgear, transformers and utility interconnection work. Ask candidates to name the equipment and systems they personally worked on, not the program they worked near.
Charging software and communications. Candidates on live networks may reference OCPP (Open Charge Point Protocol), charge point management systems, remote monitoring, fault alerts, firmware updates and ticketing workflows. These terms show exposure. They do not show depth. The evidence is in whether the candidate can explain how information coming off a charger informed a diagnosis and the action that followed.
Reliability and incident management. Look for remote diagnosis, field dispatch, parts logistics, escalation management, preventive maintenance, root-cause analysis and repeat-fault reduction. Ask for an example where they separated a symptom from the underlying cause.
Service-level accountability. This is where installation-only candidates fall away. Ask what uptime measure their team used, how incidents were classified by severity, what response and restoration commitments applied, and what reports tracked performance. Related measures worth asking about include successful session starts, time to acknowledge critical incidents and time to restore service.
Someone can be strong in the first category and thin in the last. That is fine for a commissioning or installation role. It is a gap for a network operations or reliability hire.
What does a real interview on this look like?
Take the candidate through one incident they owned, start to finish. Ask:
• What was the first information you needed to assess the issue?
• How did you determine whether the fault was hardware, backend software, communications, payment or upstream utility power?
• What remote actions did you try before dispatching anyone on site?
• Who did you escalate to, what did you ask for, and how did you keep ownership clear when several suppliers were involved?
• What counted as restoration of service?
• What did you change afterward to reduce repeat faults?
The strongest signal is whether a candidate can walk you through one real outage, start to finish, from alert to restoration to what they changed afterward to prevent it recurring. A candidate who has only installed or commissioned equipment tends to stop at the repair step and has little to say about restoration confirmation or prevention.
You can test the same judgment with a scenario. Describe a site with reduced availability, open supplier tickets and an operational escalation already under way. Ask the candidate to set priorities for the first 48 hours: what evidence they would gather, which stakeholders they would bring in, and what they would report to the customer or internal team. This exercise separates candidates who can think through a live, multi-party problem from those who can only describe past ones.
How do I test whether a candidate really understands SLA terms?
A headline uptime percentage tells you almost nothing on its own. The definition, the exclusions and the ownership model behind it are what determine what that number represents. Ask candidates:
• How was uptime defined in your previous role: connectivity, charger availability, connector availability or successful charging?
• How did you treat partial failures on multi-port equipment?
• Which outage types were excluded, and how was an exclusion evidenced?
• What were the severity levels, response targets and restoration targets?
• Who owned hardware, platform, firmware, payment, telecoms and utility-related issues respectively?
• What did the monthly uptime report show, and how did you reconcile it with service tickets?
• How were firmware or software releases approved, staged and rolled back?
A candidate who has lived inside an SLA answers these with specifics: named severity tiers, actual response windows, the report they used. A candidate who has only heard about SLAs answers in generalities.
How do I verify the scale and scope a candidate claims?
Ask directly for the scope of their responsibility: the sites or assets they supported, geographic coverage, operating hours, the suppliers they managed, and the type of role they personally played when an incident was resolved. Follow up on commissioning versus maintenance experience, travel readiness where relevant, and safety or electrical credentials required for hands-on work. For field roles, confirm high-voltage safety requirements and whether their experience is electrical installation or live-network support. For operational leadership roles, weight service management, vendor governance and reporting discipline more heavily than hands-on technical depth.
A scorecard you can reuse
| Area | What to validate | |---|---| | DC fast charging estate | Equipment, site type, role and personal responsibility | | Technical diagnosis | Ability to investigate hardware, software, communications and power-related faults | | Incident response | Monitoring, triage, escalation, dispatch and confirmation of restoration | | SLA literacy | Uptime definition, exclusions, reporting, severity and service commitments | | Supplier coordination | Clear ownership across OEM, platform, field service and other dependencies | | Improvement work | Root-cause analysis, preventive maintenance and reduction of repeat faults | | Role fit | Safety, travel, location, working pattern and required level of hands-on work |
Putting it together
Define your operating context and uptime measure before you write the brief. Source for DC fast charging experience that matches your hardware and site type. Interview against a real incident, not a list of terms. Test judgment with a 48-hour scenario. Verify scope with detailed follow-up questions. That process gives you a shortlist built on demonstrated reliability ownership, not broad EV charging terminology.
If you're building or scaling a wider charging operations team around this kind of hire, our EV charging operations teams work covers the broader team-building question. For DC fast charging and uptime SLA roles specifically, we can help you define the brief and assess the evidence above once you've confirmed the operational experience and process you need against it.
FAQ
### How is uptime different from connectivity for a DC fast charger? A charger can stay connected to the backend network while still failing to deliver a charging session, so connectivity alone does not prove uptime. Uptime should reflect whether a driver could actually start and complete a session, measured at whichever level your SLA specifies: charger, connector, site or network. Ask any candidate which of these levels their previous employer used, since the answer changes what their uptime percentage actually represents.
### What counts as a partial failure on multi-port DC fast charging equipment? A partial failure is when one connector or dispenser on a shared power cabinet goes down while the others keep working, so the site is still operational but at reduced capacity. How this is scored depends on the SLA: some agreements count it as full downtime for that port, others prorate it against total site capacity. A candidate with real SLA experience can explain how their previous employer treated this case and how it affected reported availability.
### What should a candidate be able to say about a real outage they handled? They should be able to walk through one incident from the first alert to confirmed restoration: what information they checked first, how they ruled in or out hardware, backend software, communications, payment and upstream power as the cause, who they escalated to, and what changed afterward to reduce repeat faults. This sequence is the clearest way to separate someone who has owned live availability from someone who has only installed or commissioned equipment. If a candidate stops at the repair step and has little to say about restoration confirmation or prevention, that is a gap worth probing further.
### Which downtime causes need to be separated during vetting? DC fast charging outages typically trace back to one of five sources: the charger hardware itself, the backend software or charge point management platform, communications between charger and network, the payment system, or upstream utility power. A candidate who has owned SLA performance can name which of these caused their most recent incidents and how they confirmed the cause before dispatching anyone. This separation also determines which supplier gets the escalation, so it matters for coordination as much as diagnosis.
### Why does commissioning experience differ from live-operations experience? Commissioning and installation experience covers getting DC fast charging equipment safely energised and working for the first time, which is a different skill set from carrying an ongoing uptime target against a live SLA. Someone can be strong in commissioning and have never answered for a monthly availability report, service ticket reconciliation or supplier escalation. Both are valid backgrounds, but they suit different roles, so job specs and interviews should ask about them separately rather than treating "DC fast charging experience" as one skill.
Who does AYM Recruitment place?
+
Commercial, product, infrastructure and leadership people across EV charging and grid infrastructure, in every state.