The computer questions office, support and entry-level IT interviews ask, what each one tests, short model answers, and how skills tests work.
Most basic computer knowledge questions in job interviews fall into five groups: hardware and memory, operating systems and files, the internet, security, and troubleshooting. For an office, admin or customer-support job, the interviewer is mostly checking two things: can you explain a term in plain words, and have you really used the tools named in the job ad. For an entry-level IT job, the same questions come with follow-ups, and the troubleshooting question carries the most weight. Below are the ten questions worth preparing, each with what it tests and a short answer to adapt.
How computer skills get checked
In the conversation. A definition, a habit ("How do you organise your files?") or a scenario ("A coworker's computer is slow. What do you do?"). Definitions are the easy part. Scenarios show whether you have done the work.
In a skills test. Test vendors such as eSkill sell typing tests that measure speed and accuracy, 10-key data entry tests, and Microsoft Office tests, some of them built as simulations of the software. If the posting mentions a typing speed or "proficiency in Excel", assume you may be tested on it and practise in the real program.
"Basic" is vague, so borrow a checklist. Northstar Digital Literacy, an assessment used by libraries, adult education centres and workforce centres, splits basic skills into 18 areas. The essentials are basic computer skills, internet basics, email, Windows or Mac OS, and Word, Excel, PowerPoint and Google Docs, with cybersecurity basics among the daily-life areas. That list is a fair map of what non-technical roles expect.
What gets asked depends on the job:
- Job — What to expect — Where to spend your prep time
- Office, admin, data entry — Software, files, email, often a typing or Office test — Excel and Word tasks in the real program; your typing speed
- Customer support — Troubleshooting walkthroughs, explaining tech to non-technical people, security — Question 9 below, said out loud in plain words
- Entry-level IT or help desk — Everything above, plus deeper hardware and networking — The IT help desk questions and desktop support questions
- Software or CS graduate roles — Programming concepts, data structures, networking models — The CS fundamentals questions
O*NET's profile of general office clerks lists Microsoft Office, Excel, Word, PowerPoint, Outlook and Google Workspace as in-demand software, and one listed task is to "troubleshoot problems involving office equipment, such as computer hardware and software." For IT support, CompTIA's A+ Core 1 exam, a common certification for support roles that recommends 12 months of hands-on experience, weights hardware at 25%, networking at 23% and hardware and network troubleshooting at 28% of the exam.
Hardware and memory
1. What are the main parts of a computer?
What they're testing: whether you know what each part does, not whether you can recite a list.
Model answer: "The processor, or CPU, carries out the instructions programs give it. RAM is the short-term working space for whatever is open right now. Storage, an SSD or a hard drive, keeps the operating system and files when the power is off. The motherboard connects everything, and then there are input devices like the keyboard and output devices like the monitor. In practice, when someone tells me their computer is 'out of memory', I first check whether they mean RAM or disk space, because the fix is different."
The last sentence lifts the answer: it uses the vocabulary to solve a real problem.
2. What's the difference between RAM, ROM and storage?
What they're testing: the classic mix-up between memory and storage.
Model answer: "RAM is fast, temporary memory. It's volatile, so it loses everything when the power goes off, which is why unsaved work disappears in a power cut. Storage is non-volatile: an SSD or hard drive keeps data without power but is much slower than RAM, so the computer uses both. ROM is a small amount of non-volatile memory holding the startup firmware, such as the BIOS, which starts the machine and loads the operating system into RAM."
Common mistake: saying a phone "has 256 GB of memory". That's fine in a shop, but in an interview, call it storage.
Operating systems, files and software
3. What does an operating system do, and which ones have you used?
What they're testing: the definition, then an honest account of your experience.
Model answer: "The operating system manages the computer's hardware and gives other programs a platform to run on. It handles memory, files, input and output, and the interface I work in. I use Windows 11 every day, mainly for Office and our browser-based systems, and I'm comfortable on a Mac for everyday tasks, though I haven't set one up from scratch."
Name versions and tasks. "I know Windows, Mac and Linux" with nothing behind it invites an awkward follow-up.
4. How do you organise files so you and others can find them?
What they're testing: whether you'll make a mess of a shared drive.
Model answer: "I save work to the shared or cloud folder for the project, not my desktop, so other people can find it and it doesn't live only on my laptop. I name files consistently, with the date written year first, like 2026-03-14, so they sort in order, plus a short description. And I share a link instead of emailing attachments, so there's one current version instead of five."
5. Which software are you comfortable with, and how would you rate your Excel skills?
What they're testing: whether your self-rating will survive a skills test or your first week.
Model answer (illustrative): "Word and Outlook every day. In Excel I'm comfortable with sorting, filtering, basic formulas and simple pivot tables; I used them for a weekly sales summary in my last job. I haven't written macros. If the role needs them, I'd want a couple of weeks to get up to speed."
Rate yourself by tasks, not a number out of 10. Saying where your skills stop makes the rest more believable.
Internet and networks
6. What's the difference between the internet and the World Wide Web?
What they're testing: precise use of everyday words.
Model answer: "The internet is the infrastructure, the global network of connected computers. The web is one service built on top of it: websites you open in a browser. Email is another service that uses the internet without being part of the web. The web was invented by Tim Berners-Lee at CERN in 1989."
7. What is an IP address, and what does DNS do?
What they're testing: whether you know how a device finds a website.
Model answer: "An IP address is a number that identifies a device on a network, a bit like a street address. People can't remember those numbers, so we use domain names instead. DNS keeps track of which domain names go with which IP addresses, so my computer can look up where a web address points."
Security
8. How would you spot a phishing email, and what would you do with one?
What they're testing: whether you'll be the weak point in the company's security.
Model answer: "I look for the signs CISA lists: urgent or emotional pressure to act now, a request for personal or financial details, shortened links I don't trust, and addresses or links that are slightly off, like 'amazan.com'. I don't rely on spelling mistakes anymore, because AI tools can write a polished scam. I don't click anything in it, not even 'unsubscribe'. If it might be real, I contact the company through details I look up myself. Then I report it with the email's report option and delete it. If I had already clicked, I'd tell IT straight away rather than hope it was nothing."
Likely follow-up: "What makes a strong password?" CISA's answer: at least 16 characters, either random or a passphrase of four to seven unrelated words, different for every account, and kept in a password manager so you only have to remember one. Add multifactor authentication, which CISA recommends because a stolen password alone is then not enough to get into the account.
Troubleshooting
9. A coworker says their computer is really slow. What do you do?
What they're testing: method. It separates candidates because it can't be answered from a glossary.
Weak answer: "I'd restart it, and if that didn't work I'd reinstall Windows." It skips diagnosis, and the second step wipes the coworker's setup over a problem nobody understands yet.
Strong answer, in order:
- Identify the problem. "Slow at what? Since when? Everything, or one program? Did anything change, like an update or a new app?"
- Start with the obvious causes. Too many programs open, low disk space, a pending update, too many apps launching at startup.
- Test one theory at a time. On Windows, open Task Manager with Ctrl + Shift + Esc and look at what is using the processor and memory on the Processes tab.
- Fix it. Close what isn't needed, restart, install updates, free up disk space, turn off unnecessary startup apps, run a malware scan. These are all on Microsoft's own list of fixes.
- Check it worked, with the coworker, on the task that was slow.
- Write down what you found so the next person doesn't start from zero.
If it's an old machine and nothing helps, say so: Microsoft notes that older PCs with outdated hardware may not improve much from these steps, and that upgrading may be the best long-term fix.
Those six steps follow the shape of CompTIA's troubleshooting methodology: identify the problem, form a theory, test it, fix it, verify the fix, and document what you found. CompTIA treats a structured troubleshooting methodology as standard practice for IT support work, and it is a good habit to show in an interview. Check the current A+ objectives for exactly how it is covered in the exams. Walking through it shows a method, not a bag of tricks.
10. Tell me about a time you solved a computer problem or learned new software quickly.
What they're testing: whether you take on tech problems or wait for someone else.
Model answer (illustrative): "Our team switched to a new scheduling system with a week's notice. I worked through the vendor's help pages over two evenings, built a one-page cheat sheet of the five things we did most often, and walked two colleagues through it. By the go-live day, nobody on our shift needed to call support."
Use a real story of your own: the situation, what you did, and what changed.
A one-week preparation plan
- Day 1: read the job ad as a checklist. List every tool it names, and check O*NET for what software is typical for the occupation.
- Days 2 and 3: say your answers out loud, 30 to 60 seconds each, in words a non-technical manager would follow.
- Day 4: practise the test you might get. A timed typing test, plus the Excel and Word tasks from the job ad in the real software. If your library or workforce centre offers Northstar assessments, take the matching ones.
- Day 5: prepare your troubleshooting walkthrough and one story for question 10.
- Days 6 and 7: rehearse under pressure. A friend asking questions works. So does an AI mock interview: in Verve AI, an AI recruiter asks one question at a time from a question bank you choose, which can include your own custom questions, and gives you a report with feedback and scoring afterwards.
If you can't answer something, say what you do know and how you'd find out. That beats a confident guess.
Sources
- Northstar's 18 skill areas and who uses the assessments: https://www.digitalliteracyassessment.org/
- Typing, 10-key, Office and simulation tests sold to employers: https://www.eskill.com/blog/what-is-a-basic-computer-skills-test
- Office clerk software and tasks: https://www.onetonline.org/link/summary/43-9061.00
- CompTIA A+ Core 1 (220-1201) domain weights, recommended experience, troubleshooting methodology: https://lecbyo.files.cmp.optimizely.com/download/34be017cb73211ef8985a6f347fbf652
- CPU definition: https://www.techtarget.com/whatis/definition/processor
- RAM is volatile, SSDs and hard drives are not, RAM is faster: https://www.corsair.com/us/en/explorer/diy-builder/memory/volatile-vs-non-volatile-memory-whats-the-difference/
- ROM holds startup firmware (BIOS), which loads the OS into RAM: https://www.techtarget.com/whatis/definition/read-only-memory-ROM
- Operating system definitions: https://csrc.nist.gov/glossary/term/operating_system
- Internet as infrastructure, the web and email as services, IP addresses and domain names: https://developer.mozilla.org/en-US/docs/Learn_web_development/Howto/Web_mechanics/How_does_the_Internet_work
- DNS definition: https://developer.mozilla.org/en-US/docs/Glossary/DNS
- IP address definition: https://developer.mozilla.org/en-US/docs/Glossary/IP_Address
- Tim Berners-Lee invented the web at CERN in 1989: https://home.cern/science/computing/the-birth-of-the-web/short-history-web/
- Phishing signs and what to do: https://www.cisa.gov/secure-our-world/recognize-and-report-phishing
- Strong passwords and password managers: https://www.cisa.gov/secure-our-world/use-strong-passwords
- Multifactor authentication: https://www.cisa.gov/secure-our-world/turn-mfa
- Fixes for a slow Windows PC, Task Manager shortcut, older hardware: https://support.microsoft.com/en-us/help/4002019
- Verve AI mock interview (AI recruiter, question banks, performance report): https://docs.vervecopilot.com/features/mock-interview
Ryan
CEO of Verve AI









