You're standing in front of a unit that "just stops sometimes." The customer is watching you. The previous technician already came out, poked around, found nothing, and left. Now it's your turn — and the customer's patience is roughly where you'd expect it to be.
This is the field service technician interview question that separates diagnosticians from parts-swappers. The interviewer plays the customer and opens with something like: "Appreciate you coming out. Thing is, the unit just... stops sometimes. No warning, no pattern I can see. Last guy poked around and said he couldn't find anything. So — where do you even start?"
Most candidates start by reaching for a multimeter or suggesting a part replacement. Both are wrong. Not because the tools are wrong, but because the sequence is. You haven't asked a single question yet. You don't know what "stops" means. You don't know when it happens, how often, or what the previous technician already ruled out. And the interviewer just watched you repeat the exact approach that already failed.
Why the Intermittent Fault Scenario Trips Up Experienced Technicians
A field service diagnostic interview is a role-play scenario where the interviewer presents an intermittent or ambiguous equipment fault and evaluates how you gather information, reason through potential causes, and commit to a diagnostic path — all while interacting with the customer on-site.
What makes this particular scenario vicious is the word "sometimes." Intermittent faults are the hardest problems in field service because they resist the standard troubleshooting playbook. A unit that's dead on arrival is straightforward. A unit that fails unpredictably forces you to think in probabilities, not certainties. According to the US Bureau of Labor Statistics, field service technician roles are projected to grow 6% through 2032, and employers consistently rank diagnostic reasoning as the most sought-after skill — ahead of specific technical certifications.
Here's what interviewers are actually scoring in this scenario:
1. Targeted questioning — Did you ask specific questions to narrow the intermittent fault, or did you jump to physical inspection?
2. Systematic reasoning — Did you reason through likely causes methodically, or start swapping parts?
3. Using the owner's observations — Did you leverage what the customer has noticed (timing, conditions, frequency)?
4. Avoiding the dead-end — Did you find out what the last technician tried before repeating their work?
5. Commitment to a cause — Did you land on a likely diagnosis and a concrete next step before leaving the site?
The typical failure mode is a candidate who hears "it stops sometimes" and immediately says "I'd check the compressor" or "could be a capacitor." They're guessing. And the interviewer knows they're guessing because they haven't gathered enough information to narrow it down. A 2023 ServiceMax survey found that 29% of first-visit field service calls result in a return trip — and the primary driver is misdiagnosis due to insufficient information gathering. The interview scenario is designed to surface exactly that habit.
The hard curveball is particularly revealing. Mid-scenario, the interviewer will mention that the last technician already replaced the part you were about to suggest. Candidates who built their entire reasoning around a single component have nowhere to go. They stall. The ones who asked thorough questions before proposing anything can pivot without losing credibility.
How to Approach the Field Diagnosis Scenario
The framework that works maps directly to the five criteria above. It's a sequence, and the order matters.
1. Interview the customer before you touch the equipment.
This is the step that most candidates skip or rush. Ask: "When it stops, what exactly happens? Does it shut off completely or does it seem like it's trying to run? How long has this been going on? Does it happen more at certain times of day?" You're building a fault profile from the person who's observed it most. Candidates who go straight to the equipment are telling the interviewer they don't value the customer's observations — which is both bad diagnostics and bad customer service.
2. Ask about the previous technician's work.
This is non-negotiable. "You mentioned someone came out before — do you know what they checked or replaced?" If the last tech replaced the run capacitor and the unit's still failing intermittently, that's a critical data point. It eliminates a common suspect and redirects your reasoning. Candidates who skip this question risk proposing the exact same fix that already failed — and the interviewer will let them walk right into it before revealing the trap.
3. Look for environmental and conditional patterns.
This is where strong candidates separate themselves. "Does it seem worse on particularly hot days? Is there anything else running on the same circuit? Has anything changed recently — new equipment nearby, building work, anything unusual?" The scenario is designed so that the customer mentions it seems worse on hot days, but "not every hot day." That's a signal, not noise. Thermal intermittents — components that fail at operating temperature and recover when they cool — are a classic failure mode. The candidate who connects "hot days" to thermal behaviour is demonstrating genuine diagnostic reasoning.
4. Form a hypothesis and test it logically.
What good looks like: "Based on what you've described — intermittent shutdowns, worse in heat, and the previous tech already replaced the capacitor — I'm thinking thermal overload. That could be a contactor failing under heat, or a compressor drawing high amps as it heats up. I'd want to check the amp draw on the compressor at operating temperature and inspect the contactor contacts for pitting."
What bad looks like: "Let me just swap out a few parts and see if that fixes it." No reasoning. No connection to the customer's observations. No plan that the customer can follow. The interviewer has just learned that you troubleshoot by trial and error — which is expensive and unreliable.
5. Commit to a next step before leaving.
Even if you can't reproduce the fault on site (because it's intermittent, and it may be working fine when you arrive), tell the customer what you're going to do. "I've measured the amp draw and it's borderline high. I want to come back on a hot afternoon when the unit's been running for a few hours and measure again. If it's spiking under sustained heat, that confirms a thermal overload on the compressor, and we'll replace it." You've given the customer a plan, a timeline, and a reason. The interviewer just heard you commit to a diagnostic path without blindly swapping parts.
Practice Makes the Difference
You can memorise every diagnostic framework in the HVAC manual and still fumble when the interviewer tells you the part you're about to suggest has already been replaced. That's not a knowledge gap. It's a practice gap.
The dynamic that makes this scenario hard to prepare for on paper is the layered complication. First you're dealing with an intermittent fault. Then you discover the obvious fix was already tried. Then the customer mentions the heat pattern but says it's "not every time." Each revelation forces you to adjust your reasoning mid-conversation while maintaining the customer's confidence.
This is why I built the field service scenarios on MORT's interview practice platform with adaptive complications. One thing I've observed from building these diagnostic role-plays: candidates almost always overestimate their questioning skills. In their first practice run, the average candidate asks two questions before proposing a fix. By their third run, that number doubles — and their proposed diagnoses become dramatically more accurate. The questioning isn't wasted time. It's the diagnosis.
If you've been working through incident response scenarios or customer service role plays, the field service diagnosis draws on overlapping skills — structured thinking under pressure, reading the person in front of you, and resisting the urge to jump to a conclusion before you've gathered enough data.
The Bit That Actually Matters
The single best habit you can build for a field service interview is this: ask one more question than feels comfortable before you propose anything. Every experienced technician I've spoken to while building MORT says the same thing — the difference between a first-visit fix and a callback isn't tools or parts knowledge. It's patience at the information-gathering stage. The best diagnosticians are the ones who can tolerate not knowing the answer for a few minutes longer than everyone else.