PHASE 6 · MODULE 2

Resume & Interview Preparation

Craft a compelling resume and ace your technical interviews to land your first IT support role.

9 Modules
~8.5 hours total
Career focus

🎯 Learning Objectives

Choose the best resume format for your current experience level.
Properly highlight technical certifications and lab projects.
Optimize your LinkedIn profile for IT recruiters.
Master 15+ common technical help desk interview questions.
Apply the STAR method to behavioral interview answers.
Navigate realistic help desk troubleshooting scenarios.
Negotiate entry-level IT salaries effectively.
Prepare for a successful first day in a support role.

1. Resume Formats for IT Support

30 min â–¼

Choosing Your Format

Your resume is your primary marketing document. For IT support, you need to choose a format that emphasizes your skills and certifications, especially if you're transitioning from another field.

Format Best For... Key Focus
Chronological Those with 1-2+ years of direct IT experience. Career progression and consistent employment.
Functional/Skills-Based Career changers or recent graduates. Technical skills and projects rather than work history.
Hybrid (Recommended) Most entry-level IT candidates. Combines a strong skills section with relevant experience/projects.

Standard IT Resume Structure

  • Header: Name, professional email (e.g., firstname.lastname@email.com), LinkedIn URL, GitHub/Portfolio link.
  • Professional Summary: 2-3 sentences highlighting your passion for IT, key certifications, and your goal (e.g., "CompTIA A+ certified professional seeking an entry-level Help Desk position...").
  • Technical Skills: Categorized list (OS, Networking, Software, Hardware, Tools).
  • Certifications: Clearly listed with dates (e.g., CompTIA A+, Network+).
  • Projects / Lab Work: Detailed descriptions of your home lab, AD setups, or cloud projects.
  • Experience: Professional history with a focus on transferable skills (customer service, troubleshooting, communication).
  • Education: Degrees or relevant coursework.
Pro Tip: ATS Optimization

Use standard section headings and clear fonts. Avoid complex graphics or columns that might confuse Automated Tracking Systems (ATS). Use keywords from the job description (e.g., "Active Directory", "Ticketing Systems").

2. Highlighting Certifications

20 min â–¼

The Power of Certs

In entry-level IT, certifications like CompTIA A+ are often "gatekeepers." They prove a baseline of knowledge that many HR departments require.

How to List Them

Don't just bury them at the bottom. If you have your A+, it should be near the top of your resume.

CERTIFICATIONS & LICENSES CompTIA A+ (Core 1 & 2 Certified) | License #12345678 | Issued: Jan 2024 CompTIA Network+ (In Progress - Expected March 2024) Google IT Support Professional Certificate | Issued: Dec 2023

Certification Strategy

  • Verify your status: Include your license number or a link to your digital badge (Credly).
  • Be honest: If you're "in progress," state it clearly with an expected date.
  • Show relevance: Highlight specific domains of the cert that match the job (e.g., Networking, Security).
Certification Ranking for Support

1. CompTIA A+ (The standard entry-level cert)
2. Microsoft 365 Certified: Endpoint Administrator Associate
3. CompTIA Network+ (Great for Level 2 support)
4. AWS Certified Cloud Practitioner (Good for modern help desks)

3. Project Showcase

30 min â–¼

Proof of Skill

If you don't have job experience, your projects ARE your experience. Use your portfolio to show, not just tell, what you can do.

What to Include

  • Active Directory Home Lab: Show that you can manage users, groups, and GPOs in a Windows Server environment.
  • Virtualization Projects: Documenting the setup of VMs (VirtualBox, VMware, Proxmox).
  • Automation Scripts: PowerShell or Bash scripts used to automate repetitive tasks (e.g., user onboarding).
  • Networking Labs: Packet Tracer or GNS3 labs showing VLAN configurations or subnetting.
  • Cloud Deployments: Setting up an Azure AD (Entra ID) tenant or a simple AWS S3 bucket/EC2 instance.

Documenting Troubleshooting Wins

Include a "Troubleshooting Journal" or specific project write-ups that follow this flow:

Project: Windows Server 2022 Active Directory Setup Problem: Users unable to authenticate across subnets. Diagnosis: Found DNS records were not properly replicating. Solution: Configured DNS Forward Lookup Zones and verified replication settings. Result: 100% authentication success rate across all test clients.
GitHub for IT Support

Yes, IT support people use GitHub! Store your scripts, documentation markdown files, and lab configurations there. It shows technical literacy and familiarity with version control.

4. LinkedIn Optimization

25 min â–¼

Your Professional Digital Brand

LinkedIn is where recruiters find you. If your profile is empty, you're missing out on 50% of the job market.

The Headline Formula

Don't just put "Student." Use a keyword-rich headline:

CompTIA A+ Certified | Aspiring IT Support Specialist | Active Directory | Office 365 | Troubleshooting

About Section Strategy

  • The Hook: Start with your passion for solving problems and helping people.
  • The Tech: List the technologies you've mastered (AD, PowerShell, MDM).
  • The Human Side: Mention your customer service background or communication skills.
  • The Call to Action: "Open to entry-level IT Support and Help Desk opportunities. Let's connect!"

Recommendations & Skills

  • Ask former colleagues or teachers for recommendations focusing on your reliability and problem-solving.
  • Add at least 20 skills (Technical: Windows 10/11, Networking, DNS; Soft: Customer Service, Technical Writing).
  • Take LinkedIn Skill Assessments to get "verified" badges.

5. Technical Interview Q&A

60 min â–¼

The Technical Screen

Interviewer's want to see your process, not just your knowledge. If you don't know the answer, explain how you would find it.

1. How do you troubleshoot a computer that won't turn on?

Answer: First, check the obvious: Is the power cable plugged in? Is the outlet working? If it's a laptop, is the battery charged? Then, check for lights or beep codes from the motherboard. Listen for fans. If there's power but no display, test with an external monitor. If there's no power at all, it could be a failed PSU or a dead motherboard.

2. A user can't connect to the internet. What do you check?

Answer: I follow the OSI model (Bottom-Up). Physical layer first: Is the Ethernet cable plugged in? Is Wi-Fi toggled on? Then, check IP configuration using ipconfig. Does it have a valid IP, or is it a 169.254.x.x address (APIPA)? Can I ping the default gateway? Can I ping 8.8.8.8 (connectivity check)? Can I ping google.com (DNS check)? Finally, check for browser settings or proxy issues.

3. How do you reset a user's password securely?

Answer: Always verify identity first according to company policy (ID badge, manager approval, or security questions). In Active Directory, I would find the user object, right-click, select 'Reset Password,' enter a temporary password, and ensure 'User must change password at next logon' is checked. I would then communicate the temporary password securely (e.g., via a secure message or over the phone, never via unencrypted email).

4. A user says their computer is running slowly. How do you diagnose it?

Answer: I'd open Task Manager to check CPU, Memory, and Disk usage. Are there specific processes hogging resources? Is the disk near 100% usage (possible failing HDD)? I'd check for too many startup programs. I'd also check for available disk space and run a malware scan. I'd ask the user when the slowness started and if it happens in specific apps or across the board.

5. How do you resolve a printer that won't print?

Answer: Check the physical status (Paper, Ink/Toner, Error lights). Check the print queue—are there stuck jobs? Clear the print spooler (stop/start the service). Verify connectivity (is it online in Devices & Printers?). If it's a network printer, can I ping it? Reinstall the driver if necessary. If it's a shared printer, check permissions.

6. A user can't access a network drive. What could be wrong?

Answer: Check network connectivity first. Can the user ping the server? Check if the drive is mapped correctly. Use net use to see status. Check the user's permissions in Active Directory/NTFS. Is the user's account locked or has their password expired? If others can access it, it's likely a local mapping or permission issue.

7. Explain DNS in simple terms to a non-technical user.

Answer: DNS is like the "Phonebook of the Internet." Computers use numbers (IP addresses) to talk to each other, but humans use names (like google.com). When you type a name into your browser, DNS looks up the number for that name so your computer knows where to go.

8. A user gets a "Blue Screen of Death." What do you do?

Answer: Record the Stop Code and the name of the failing file if provided. Restart the computer—does it happen again immediately? If so, try booting into Safe Mode. Check for recently installed hardware or drivers. Use the 'BlueScreenView' tool or check Event Viewer (System logs) for clues. Run hardware diagnostics (RAM/Disk) if it's recurring.

9. How do you handle a situation where a user is frustrated or angry?

Answer: I stay calm and professional. I listen without interrupting and acknowledge their frustration ("I understand this is preventing you from working, and I'm here to help"). I focus on the problem, not the emotion. I give them a clear plan of what I'm doing to fix it and keep them updated. If I can't fix it immediately, I set realistic expectations.

10. What steps do you take when setting up a new employee's workstation?

Answer: Follow the company checklist: 1. Provision hardware (PC, Monitors, Peripheral). 2. Install OS/Image. 3. Join the domain. 4. Install necessary software (Office, VPN, Line-of-business apps). 5. Map network drives and printers. 6. Verify security (Antivirus, Updates). 7. Test user login. 8. Leave a "Welcome" guide for the user.

11. A user reports that their email isn't working. How do you troubleshoot?

Answer: Is it a webmail issue or a desktop client (Outlook) issue? If desktop, is Outlook in 'Work Offline' mode? Check the internet connection. Can the user log into webmail? If yes, it's a local client/profile issue. If no, is the account locked? Check for service outages (Microsoft 365 status). Check if the user is over their storage quota.

12. What is the difference between RAM and hard drive space?

Answer: RAM is "short-term memory"—it's very fast but temporary; it's what the computer is using right now to run programs. The hard drive is "long-term storage"—it's slower but permanent; it's where your files and apps live when the computer is turned off.

13. How do you secure a workstation before leaving it unattended?

Answer: I always lock the screen (Windows + L). I ensure no sensitive documents are visible on the desk. I make sure no USB drives with sensitive data are left plugged in. In a high-security environment, I'd also ensure no "sticky notes" with passwords are under the keyboard!

14. A colleague's computer keeps freezing. What's your approach?

Answer: I'd look for patterns: Does it freeze when a specific app is opened? Is it a thermal issue (are the fans loud/is it hot)? I'd check Event Viewer for "Critical" errors around the time of the freezes. I'd run a memory test (MemTest86) and a disk health check (S.M.A.R.T.). I'd also check for driver updates or BIOS updates.

15. How do you stay organized when handling multiple tickets at once?

Answer: I use the ticketing system's priority levels (SLA). I address "High Impact/Urgent" tickets first (e.g., server down, entire department offline). I group similar tasks (e.g., several password resets) to be efficient. I always update my notes in the ticket so if I get interrupted, I know exactly where I left off, and others can see the progress.

6. Behavioral Interviews (STAR Method)

40 min â–¼

The STAR Method Explained

For behavioral questions ("Tell me about a time when..."), use the STAR framework:

  • Situation: Briefly set the scene.
  • Task: What was your specific responsibility?
  • Action: What exactly did you do? (Focus on your contribution).
  • Result: What was the positive outcome? (Use numbers/metrics if possible).

Common Behavioral Questions & Samples

Q1: Tell me about a time you handled a difficult customer.

Answer: (S) In my previous retail job, a customer was shouting because their return was rejected. (T) My task was to de-escalate the situation while following company policy. (A) I listened patiently, empathized with their frustration, and discovered the issue was a misunderstanding of the return window. I offered to call my manager to see if an exception could be made. (R) The manager approved a store credit, the customer calmed down, and they actually thanked me for my patience.

Q2: Tell me about a time you made a mistake at work.

Answer: (S) During a lab exercise, I accidentally deleted a test user from Active Directory instead of disabling them. (T) I needed to restore the user to verify a GPO. (A) I immediately admitted the mistake to my instructor, looked up the documentation for the AD Recycle Bin, and successfully restored the object. (R) I learned to always "double-check before clicking" and became the go-to person in my class for AD recovery procedures.

Q3: Describe a time you had to learn a new technology quickly.

Answer: (S) I was asked to help with a project involving Microsoft Intune, which I hadn't used before. (T) I needed to understand how to enroll mobile devices within 48 hours. (A) I spent the weekend watching Microsoft Learn modules, set up a trial tenant, and practiced enrolling my own phone. (R) I was able to successfully assist with the rollout on Monday, and I've since documented the process for the rest of the team.

Q4: Tell me about a time you went above and beyond for a user.

Answer: (S) A user's laptop failed right before a critical board presentation. (T) I needed to get them working immediately. (A) I provided them with a loaner, but noticed their local files hadn't synced to OneDrive. I stayed late to manually recover the data from their old hard drive and ensured it was on the loaner before their meeting. (R) The user aced the presentation and sent a commendation to my manager for the "save."

Q5: How do you handle a situation where you don't know the answer?

Answer: (S) A user asked me about a complex Excel macro error I'd never seen. (T) I needed to resolve it without guessing and causing more damage. (A) I told the user, "I haven't encountered this specific error before, but I'm going to research it and get back to you." I used the internal knowledge base, searched Microsoft forums, and eventually found the solution. (R) I fixed the error and created a new "how-to" article in our ticketing system for future reference.

Q6: Tell me about a time you had to prioritize multiple urgent tasks.

Answer: (S) On a Monday morning, our internet went down, and three users had "urgent" printer issues. (T) I had to manage the outage while addressing the users. (A) I prioritized the internet outage as it affected everyone, contacted the ISP immediately, and sent a broadcast message to the team. Once the ISP was working on it, I addressed the printer issues by order of arrival. (R) The internet was back in 20 minutes, and all printer tickets were closed by noon.

Q7: Describe a time you worked as part of a team to solve a problem.

Answer: (S) Our team was tasked with upgrading 50 workstations to Windows 11 in one weekend. (T) We needed to complete the task without errors. (A) We divided the labor: I handled the data backups, another colleague did the imaging, and a third did the post-install testing. We communicated via Slack to track progress. (R) We finished ahead of schedule and had zero "Monday morning" support calls related to the upgrade.

Q8: Where do you see yourself in 3-5 years?

Answer: I want to be a subject matter expert in IT. After mastering the foundations in this support role, I plan to pursue my Network+ and Security+ certifications with the goal of moving into a Systems Administrator or Cybersecurity Analyst role within the company. I want to contribute to larger infrastructure projects.

7. Mock Interview Scenarios

45 min â–¼

The "Whiteboard" Challenge

In many IT interviews, you'll be given a scenario and asked: "What do you do?"

Scenario 1: The CEO's WiFi isn't working

Candidate Response: "I'd treat this with high priority but stay calm. I'd first ask if other devices can connect to verify if it's a device issue or an AP issue. If it's just the CEO's laptop, I'd check the physical Wi-Fi toggle, then 'Forget' the network and reconnect. I'd verify they aren't in Airplane mode. If it still fails, I'd check if their account has been flagged in our NAC/Security system. Throughout, I'd keep them informed that I'm working to get them back online immediately."

Scenario 2: A suspicious email is reported

Candidate Response: "I'd instruct the user NOT to click any links or download attachments. I'd ask them to forward the email as an attachment to our 'Phish' inbox. I'd then examine the headers to check the sender's actual address and the destination of the links. If it's malicious, I'd check if anyone else in the organization received it and use our email security tool (like Defender for Office 365) to purge it from all inboxes."

Scenario 3: A server goes down during business hours

Candidate Response: "I'd immediately check our monitoring tools to see what services are affected. I'd notify my manager and the affected departments. If I have access, I'd check the hypervisor or physical console for error messages. I'd look at the most recent changes—did a patch just run? I'd try to restart services before a full reboot. I'd document every step taken for the Post-Incident Report (PIR)."

Scenario 4: You have a backlog of 20 tickets and a user walks up to your desk

Candidate Response: "I would politely greet the user but explain that I'm currently working on several high-priority issues. I'd ask them to briefly describe their problem. If it's a quick fix (under 2 mins), I might help. Otherwise, I'd ask them to submit a ticket (or I'd create one for them) so I can track it and ensure it gets addressed properly according to our queue. I'd never just ignore them, but I have to respect the ticketing process."

Scenario 5: A user wants you to install unapproved software

Candidate Response: "I would explain that we have a company policy regarding approved software for security and licensing reasons. I'd ask them what business problem they're trying to solve. I'd check if we have an approved alternative. If not, I'd direct them to the proper approval process (manager/security team) rather than just saying 'no' or bypassing the policy."

8. Salary Negotiation

25 min â–¼

Know Your Worth

Entry-level IT support salaries vary wildly by location and company size. Do your research before the "What are your salary expectations?" question comes up.

Role Typical Range (US - 2024) Factors
Help Desk Tier 1 $40,000 - $55,000 Certifications, Location, Shift.
Desktop Support $50,000 - $65,000 Hands-on experience, Hardware depth.
Junior SysAdmin $60,000 - $75,000 Scripting, AD/Cloud skills.

Negotiation Talking Points

  • The Value Add: "Based on my CompTIA A+ certification and my hands-on lab experience with Active Directory, I believe I can hit the ground running..."
  • The Market Rate: "I've researched similar roles in [City] and found the market range for this position is $X to $Y..."
  • Total Compensation: Don't just look at the salary. Consider 401k matching, PTO, certification reimbursement, and training budgets.
  • The Silence: After you state your number, wait. Don't immediately start talking yourself down.
When to Negotiate

Always wait for the official offer letter. Once they've chosen you, you have the most leverage. If the salary is firm, ask for a "6-month salary review" based on performance and additional certifications.

9. First Day Checklist

15 min â–¼

Making a Great Impression

The first 90 days are critical. Use your first day to listen, learn, and document.

What to Bring

  • A physical notebook and pen (shows you're taking notes).
  • A curious and helpful attitude.
  • Your own personal "Cheat Sheet" of common commands (just in case).

Mindset Tips

  • Ask "Why": Don't just follow steps; understand the logic behind the company's workflows.
  • Introduce Yourself: Meet the team. IT is a social job!
  • Look for the "Low Hanging Fruit": Are there outdated docs you can update? Small tasks you can take off a senior tech's plate?
  • Admit what you don't know: It's better to ask than to break a production server on Day 1.
Your First Day Goal

Your goal is NOT to fix everything. Your goal is to learn the team's tools, meet your coworkers, and understand how they define "Success."

📋 Appendix: Career Prep Assets

Resume Template: Clean, ATS-friendly IT format.
Interview Prep Checklist: 48 hours before the big day.
Question Bank: 50+ Help Desk questions.
STAR Worksheet: Prep your 5 best stories.

🔗 Essential Resources

🚀 Next Steps

Now that your resume is ready and your interview skills are sharp, it's time to build your application strategy.

  1. Review the Job Search Strategy module.
  2. Finalize your resume and have it reviewed by a peer.
  3. Start a mock interview session with a friend or using an AI tool.