Resume writing guide
Computer Skills on a Resume: Examples That Show What You Can Do
List computer skills that matter to the vacancy, and show the tasks you can perform with them. “Excel: tables, filters and basic formulas” gives more information than “computer literate.” Support important skills with a work or project example so a reader can understand how you used the software.
Start with the task the employer needs
Read the job description for the work behind each tool. Maintaining a contact list, analyzing data, preparing presentations and managing a support queue require different capabilities. Choose the skills that support those tasks rather than listing every app you have opened.
Make three notes for each skill: the tool, an action you can complete and a real example. For a spreadsheet, that might be filtering an order list and checking totals. For a shared document, it might be resolving comments and maintaining a clear revision. If you cannot name an action, the software name alone is weak evidence.
Group skills when it makes the list easier to read
A short list can fit on one line. If several categories matter, use labels such as Documents, Spreadsheets, Collaboration and Technical Tools. Keep the groups specific to the application; an office administrator does not need a programming category unless the work calls for it.
The following entries are examples to adapt, not a checklist of skills everyone should claim. Keep only tools and tasks you have actually used. Replace a product name when your experience was with a different tool, and do not imply that similar software is identical.
Task-based computer skill entries
Documents: Microsoft Word — styles, tables and tracked edits
Spreadsheets: Microsoft Excel — tables, filters and basic formulas
Collaboration: Google Docs — comments, suggested edits and shared document review
Presentations: [Actual tool] — slide layouts and charts from verified source data
Technical: Python — CSV processing and unit tests in personal projects
Office example: show how the software supported the work
An administrative applicant can connect software skills to records, scheduling or document preparation. The fictional example below describes a workflow without inventing a time saving or claiming responsibility for the organization’s entire information system.
Administrative experience — illustrative bullets
Maintained an Excel appointment list, filtered outstanding requests and checked duplicate entries before the weekly review.
Prepared Word meeting notes using consistent headings and recorded action owners and due dates from the discussion.
Collected comments on a shared Google document and updated the draft after the owner approved the changes.
Analytical example: distinguish formulas from analysis
Using a spreadsheet does not automatically establish advanced analysis. Describe the question, input and checks. If you used a lookup, pivot table or chart, explain what it helped you do. Include only functions and methods that were part of your work.
Microsoft’s official guidance treats sorting and filtering as specific operations. Name those operations when they match your experience instead of using an undefined “advanced Excel” label. For more complex work, explain the additional evidence, such as a checked model or reproducible report.
Analysis project — fictional pattern
Grouped a public sample dataset by month in [actual spreadsheet tool] and checked the totals against the original records.
Created a chart of the monthly values and documented missing entries so the reader could see the limits of the comparison.
Technical example: state the environment and scope
For a technical role, separate programming, databases and development tools. “Python, SQL, Git” may be an appropriate skills line, but the projects should show what you wrote or maintained. A browser-based tutorial is different from using the tool independently in a project.
If your evidence comes from coursework or a personal project, label it. If you maintained a production system, explain your responsibility without sharing private code or credentials. Keep access administration, user support and software development distinct; familiarity with an app does not mean you administered its systems.
Technical project evidence — illustrative format
Personal project: Wrote a Python script that validates required fields in a CSV file and saves rejected rows for review.
Database task: Wrote SQL queries that summarize [actual dataset] by [category] and checked the output against [reference].
Version control: Used Git branches and reviewed changes before merging a project update.
Check your claimed level with a small exercise
Before calling a skill proficient, try a representative task without copying a completed solution. For spreadsheet work, make a small synthetic table, add a calculation, filter a category and check the result manually. For document work, create a short formatted document, add comments and export a readable copy.
This is a private self-check, not a certification or an employer assessment. It helps you identify which actions you can explain and which need practice. Use synthetic information; do not upload workplace records to a personal account just to create a sample.
If you need occasional reference material, that does not erase the skill. Be ready to explain your process and limits. Avoid percentages and star ratings that offer no definition of ability. A precise task description is easier to discuss in an interview.
Keep the final list focused and current
Remove obsolete or irrelevant entries when they crowd out stronger evidence. You do not need to claim basic email use for every role, but it may be relevant when the vacancy specifically needs appointment communication or shared inbox handling. Let the job’s work determine the detail.
Check that the tools in Skills agree with your experience bullets. If a course is your only exposure, label the training accurately instead of implying work experience. Then inspect the exported resume for readable text and follow the employer’s requested file format.
Questions, answered
Should I write “computer literate” on my resume?
Specific tools and tasks are usually clearer. Explain whether you maintain spreadsheets, prepare documents, handle shared files or write code, and support the relevant skills with an example.
How do I describe Excel skills without overstating them?
Name the features you actually use and a task you completed. Sorting, filters and basic formulas are different from building a complex model or automating a workflow. Avoid an unexplained advanced label.
Can I include software learned through a course?
Yes, when you can use it and the skill is relevant. Label the course or project accurately. Completing training does not automatically demonstrate professional proficiency.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.