Computer skills on a resume should describe software work you can actually complete. A recognisable product name helps a reader identify the environment; a specific task helps them understand your capability. Choose the tasks that matter to the vacancy, then write claims you can demonstrate without exposing someone else's information.
This guide focuses on computer tasks, sample resume wording and small checks you can perform yourself. It does not assign universal proficiency levels, promise an ATS score or assume that every Indian office requires the same tools.
Editorially revised on 9 October 2026. All candidate examples and practice datasets below are fictional.
Start with the work in the vacancy
Read the responsibilities before copying software names into your skills section. An office assistant vacancy might ask for document preparation and spreadsheet maintenance. A design vacancy might specify a particular editing application and portfolio format. A reporting role may require queries or dashboards. These are different tasks, even when each uses a computer.
Make a short requirement list. Separate essential software from preferred software and from tasks that do not name a product. If the employer supplies an assessment or application template, follow that instruction. Do not turn familiarity with one application into proficiency across an entire suite.
For example, preparing slides in PowerPoint does not establish that you can build spreadsheet models in Excel. Using a browser-based customer record does not establish database administration. Opening an AI application does not demonstrate accurate research, secure handling of information or independent judgement.
Computer skill categories and honest wording
Use categories only when they help the reader. A short, relevant line is often more useful than a long list of every application you have encountered.
| Area | Example task to describe if true |
|---|---|
| Documents | Format headings, tables and page numbers; review an exported file |
| Spreadsheets | Sort and filter a complete dataset; use checked formulas |
| Presentations | Organise slides and check readability in the required output |
| Files | Name versions consistently and share through approved access settings |
| Collaboration | Manage comments and action items in an agreed team workflow |
| Specialist software | Identify the product, task and actual level of responsibility |
These are editorial examples, not a list of mandatory skills. Use the product and version you actually used when that distinction matters. If you practised in an alternative application, name it accurately rather than implying access to a different commercial product.
Replace a broad label with a bounded claim
A fictional fresher initially writes: “Expert in computers and Microsoft Office.” The candidate has used Word for assignments and Excel for a small club expense list. The claim is much broader than the evidence.
A clearer skills line is: “Word: document headings and tables. Excel: sorting, filtering and SUM formulas in a student expense worksheet.” If the vacancy needs more advanced spreadsheet work, this candidate can identify a learning gap without pretending to have already closed it.
A fictional experienced office coordinator might write: “Excel: maintained a departmental tracking workbook and checked weekly totals; Word: prepared recurring reports using the team's template.” A separate experience bullet can explain ownership and review. Do not invent a percentage reduction in errors because the task sounds more impressive with a number.
A designer might list one application used to prepare layouts, then link a permitted sample explaining the brief and contributions. Software familiarity and the quality of a design portfolio are related but distinct claims. An application name alone does not establish professional production experience.
A practical spreadsheet check
Microsoft's basic Excel guidance covers entering data, calculations, sorting, filtering and tables. Use it to practise a specific task in your available version. The documentation explains features; it does not award a resume proficiency level.
Create a fictional expense sheet with columns for item, date, category and amount. Include several categories and at least one blank amount. Save a copy before changing the dataset. Check which rows should be included in a total and decide how missing values will be recorded.
Sort the complete data range by date and confirm that item names remain attached to their amounts. Filter one category, then explain whether your total represents all records or only the displayed records. If you use a formula, check a small set manually and examine what happens when a new row is added.
For fictional amounts of ₹120, ₹80 and ₹200, the simple total is ₹400. That arithmetic demonstrates a check of those three entries, not accuracy across an organisation's accounting records. If a formula excludes a row or includes a header incorrectly, correct the range and describe the problem you found.
Your resulting resume claim might be: “Excel: built a fictional expense worksheet with sorting, category filters and checked totals.” Do not call this paid finance experience. Do not claim pivot tables, macros or data validation unless you actually used and can explain them.
Check document preparation beyond typing
Prepare a short fictional report with a title, two heading levels, one table and page numbers. Export it in the format requested by the employer or practice brief. Reopen the exported file and check line breaks, missing symbols, table splitting and whether the text remains readable.
Then edit the source document and give the revised copy a clear version name. If you have used comments or change review, explain what you reviewed and who approved the final content. A student peer review is still a student activity; describe it accurately.
A possible wording is: “Word: formatted a two-page coursework report with headings, a table and page numbers; checked the PDF export.” The page count is relevant only if it is true. A sample with clear structure is useful evidence even without a claim that it impressed a recruiter.
File sharing and collaboration are concrete tasks
Describe what you did: maintained a folder convention, resolved comments, recorded decisions or prepared a handover. Avoid describing yourself as an expert in collaboration because you attended video calls.
For a shareable sample, use invented names and records. Check the recipient scope of the link and follow the platform and organisation's access rules. Screenshots of a real customer system, internal email or employee list can disclose information you are not entitled to share. A recreated demonstration should be labelled as a demonstration.
For an interview, prepare a brief explanation of how you prevented confusion between versions. You might describe a naming convention and a review step. If you did not administer permissions, say you followed the existing process rather than claiming security administration.
Specialist skills and learning in progress
For SQL, design applications, CAD, coding tools or a CRM, state the actual task and setting. “Practised SELECT queries on a fictional dataset” is narrower than “database management.” “Updated records under supervision” is narrower than “implemented a CRM.” Both can be worthwhile evidence when written truthfully.
A course certificate demonstrates completion of the stated course or assessment. It does not automatically establish professional proficiency in every topic listed in a syllabus. Place relevant training in education or certifications and describe practical work separately.
If learning is incomplete, identify the gap plainly. Do not list a planned certification as awarded. You can omit a tool until you have enough evidence or describe relevant completed practice under a project heading.
Decide where each claim belongs
Put concise, relevant software tasks in the skills section. Put contributions, context and outcomes in experience or projects. Avoid repeating the same long description in three places.
Use the technical domain skills guide to distinguish tools from work context. For a fresher's document structure, see the resume format guide. Neither guide overrides the employer's instructions.
Questions before submission
Should I write basic, intermediate or advanced? Only if the label helps and you can define the tasks behind it. These labels do not have one universal hiring definition.
Should I include typing speed? Include a measured speed when relevant and truthful, with the test conditions if needed. A practice result is not an official recruitment typing qualification.
Can I list AI tools? Describe a completed, permitted task and how you checked the output. Do not imply that generating text established expertise in its subject or that confidential material was safe to upload.
What if I cannot demonstrate a listed task? Narrow the wording, complete relevant practice or remove the claim. Check every remaining line against something you can explain and, where permitted, show.