I've been interested in IT for years, but life circumstances led me into hospitality. Since 2018, I've worked with both Windows and Linux systems and built a small homelab, although I don't currently have an IT degree or certifications. I'm hoping to earn a diploma or CompTIA A+ certification soon.
I recently applied for an IT Executive position at an automobile dealership. My online application was initially rejected because I lacked formal IT qualifications, but I visited HR in person, answered some questions, and they shortlisted me for an interview.
During the interview, they asked about computer hardware, network discovery, sharing printers and folders, disk imaging, IP classes, and crimping LAN cables. I struggled with the IP classes question because I misheard it over the phone, and I haven't learned the wire order for Ethernet cables because I've never had access to the proper crimping tools. I do understand the tools and cable-testing process.
The interview otherwise seemed positive. They told me to study those topics and said they would contact me again. The role appears to involve handling the company's Windows computers and basic infrastructure, along with some unrelated errands. The pay is close to what I currently earn in hospitality, and the company's IT environment seems to need significant improvement.
I'm feeling nervous and dealing with some imposter syndrome. What should I study, ask during the next interview, or do to improve my chances of breaking into IT?
5 Answers
Keep applying elsewhere while you wait. This opportunity may be useful, but the lower pay, mixed duties, and apparently neglected systems are reasons to evaluate it carefully. Ask whether there is training, who owns the infrastructure, what software and hardware you’ll support, and what success looks like in the first few months. Don’t let the title alone convince you to accept a role with unreasonable expectations.
This could be a good first IT job, even if the title sounds more impressive than the actual duties. If you take it, try to get as much hands-on experience as possible: document the systems, improve the network carefully, learn proper backup and recovery procedures, and keep records of the projects you complete. That experience can help you move to a better support role after a year or so.
Before accepting, make sure you understand the real responsibilities, working hours, equipment, reporting structure, and whether you’ll have any budget or support. If you’re effectively the only IT person, you don’t want to be blamed for problems without having the access or resources to solve them.
That makes sense. I’m planning to treat it as a chance to build real experience while continuing to study for a certification.
A nontraditional route into IT is definitely possible. Many people start in hospitality, retail, or other service jobs and move into help desk or first-line support through self-study, volunteering, and a little luck. Look for opportunities at schools, charities, small businesses, or community organizations where you can safely help with computer upgrades, troubleshooting, or basic administration. Real-world exposure and references can compensate for not having a degree.
When applying, present your homelab and past computer work as projects rather than just saying you’re self-taught. Explain what you built, what problems you solved, and what technologies you used. A CompTIA A+ or similar entry-level certification can help get your résumé past initial screening, but it isn’t the only route.
For the technical questions, learn the practical basics rather than memorizing isolated definitions. Know what the old IP class ranges represented, while also understanding that modern networks normally use CIDR and subnet masks. For Ethernet cables, study the T568A and T568B color orders and practice making straight-through cables with inexpensive tools. Also be ready to explain how you would test a cable, troubleshoot a device that cannot reach a shared folder, and safely image or restore a computer.
You don’t need to know everything for a junior role. If you don’t know an answer, explain how you would investigate it, check documentation, test safely, and ask for help when necessary.
Feeling like an imposter is pretty normal when you’re moving into a new field. The fact that you know what you don’t know is actually useful. Review IP addressing, Ethernet wiring standards, imaging, printer and folder sharing, and basic Windows troubleshooting before they call again. Be honest about the gaps, but emphasize that you learn quickly and have already built practical experience through your homelab.
Your hospitality background is also valuable. Communication, patience, dealing with frustrated people, and staying organized are major parts of entry-level IT support. Technical knowledge can be developed, but those people skills are harder to teach.
The title can help your résumé, but the actual work matters more. Try to leave with concrete accomplishments you can describe, such as imaging a set of computers, organizing accounts, improving backups, or standardizing printer and network setup.