Companion post to the video. Every answer below is written out word for word, exactly as promised. Print it. Stick it next to your mirror. Say them out loud.
You’ve got a help desk interview coming up. Maybe your first one ever. No real experience behind you, and you’re lying awake working out what they’re going to ask — and what on earth you say back.
I’ve been there. I got my first IT job with no real experience. No degree. Just a couple of certs and a homelab. And these days I’m on the other side of the table — I’ve sat on the panel, deciding who gets the job.
So I know the exact questions you’re walking into. Here they are, with the answer that works for each one, and why it works.
But first, the thing nobody tells you before that first interview: they are not hiring a senior engineer. They know you’re entry level. What they’re actually scoring is simpler. Can you think clearly. Can you stay calm. Do they want to sit next to you for the next two years.
Keep that in your head for every answer below.
1. “Tell me about yourself”
The one you’ll always get first. It’s not small talk — it’s the first thing they score, and most people fumble it in the opening ten seconds.
The trap goes one of two ways. Your whole life story. Or worse — “I don’t really have experience, but I’m hoping to learn.” Don’t hand them that.
Here’s the answer that works:
“I’ve just finished my CompTIA A+. I’ve been running a homelab and fixing friends’ and family’s equipment for a couple of years — I’m the IT guy in the family. I want to move into IT because I like solving problems and working with people, and I’m ready to do it properly.”
That’s it. Technical background. Initiative. And you’ve put yourself across as ready to contribute — not ready to be taught.
When I did this with zero professional experience, the homelab was my answer. It was the proof I’d actually done the work, not just read about it. You’re not asking them for a chance. You’re telling them you’re ready.
2. “How do you handle a stressful situation or a difficult user?”
Look — half of help desk isn’t tech. It’s people. Angry people, sometimes. And they’d rather train someone calm than someone brilliant who falls apart the second Karen’s printer won’t print and she’s blaming you for it.
The wrong answer is “oh, I don’t really get stressed.” Nobody believes that.
Here’s what you say:
“I stay calm, I ask clear questions, and I don’t take it personally. I let the user know I’m there to help. If I’m stuck, I ask internally — and if I really can’t fix the issue, I know my escalation path.”
And there’s a structure under every answer like this: problem, action, result. What happened, what you did, how it ended. Use it every time.
They’re not after someone who never gets stressed. They’re after someone who doesn’t lose the plot when it happens.
3. “What’s the difference between TCP and UDP?”
Now we’re into the technical ones. This is where people freeze and start reciting a textbook. Don’t — they’re not hiring a network engineer, and word-for-word definitions actually sound worse.
Keep it real:
“TCP is like a phone call — you know they picked up, you know they heard you. It checks the data actually gets there. File transfers, loading a web page. UDP is like shouting across the room — faster, but no guarantee they catch all of it. Streaming, voice calls — if it goes choppy for half a second, it’s not the end of the world.”
Notice each one is tied to something real instead of a definition. That’s the whole trick. It makes you sound like someone who’s used it, not someone who crammed it the night before.
Be right, and be clear. Most people manage one or the other. And if you don’t know the answer — just be honest.
4. “A user can’t access the internet. What do you check?”
This is the one they actually care about. They’re not testing what you know — they’re testing how you think. And the fastest way to fail it is to blurt out “it’s probably DNS” and start there.
First problem: “the internet” means nothing. Is it one user, or is it everyone? That changes the whole job.
So you go layer by layer, and you start at the bottom:
“First I’d check whether it’s one machine or the whole office. Then the physical — cable, Wi-Fi. Then the IP address. I’d ping the default gateway. I’d test DNS. I’d try another browser. Start broad and narrow it down.”
Half the “internet’s down” calls I ever took came down to the dumbest thing possible — a kicked-out cable, caps lock on the password. That’s what real troubleshooting is. They want to see you don’t panic, and you don’t skip steps.
5. “What is Active Directory?”
Almost guaranteed if it’s a Windows shop. And the trap here is overselling — don’t claim mastery you can’t back up, because they’ll find the edge of it in one follow-up question.
Clean answer:
“Active Directory is Microsoft’s system for managing users and devices. It handles logins, permissions, and group policy across the network.”
Definition. Core functions. Done.
Funny thing — I run AD every day now. Back in that interview I just needed to show I knew the shape of it. That was plenty. They want to know you’ve heard of it and you know what it does. That’s the bar.
6. “Why do you want to work here?”
Sounds soft. It’s a trap. Because the real answer in your head — “I need the experience” — is the one that quietly sinks you. So is generic flattery.
Do your research on the company and make it about them:
“I’m after a team where I can grow and actually contribute from day one. I like that you invest in training and work with modern tools.”
That shows you’ve thought about them, not just what you get out of it. And it tells them you’ll stick around — which, if you’re being real with yourself, should be true.
7. “Do you have any questions for us?”
Most people say “no, I think I’m good” — and hand the room straight back. Don’t be most people. This is where you flip it. Now you’re interviewing them.
Have a few ready:
“What does a typical day look like for a tier-one tech here?” “What do your best techs do differently?” “What ticketing system do you use?”
And then the one that puts you ahead of nearly everyone:
“If my first 90 days here went perfectly — what would that look like to you? Performance, culture fit, all of it.”
That question does something. It shows you’re serious. You’re thinking long-term. And you’re already picturing yourself in the seat, doing the work.
That’s the answer that separates you from 90% of the room. And it costs you nothing but the nerve to ask it.
Before your interview, do one thing for me
Say these out loud. On camera, if you can stand it. You’re going to feel like an idiot. Do it anyway. Five minutes a day, and you’ll walk in calmer than you think.
And if you want to hear how each of these lands out loud — watch the video. Say hi in the comments while you’re there: tell me which question worries you most, and I’ll give you an answer that works.
