How to Write a Resume in Pakistan with No Experience (Fresh Graduate Guide)

You have finished university, found a vacancy and opened a blank document. The work-experience section looks like the hardest part. Start somewhere else: your final-year project, internship, coursework or student activities. These give you something concrete to write about.

This article walks through that writing process. If you want a finished section layout to follow, use the graduate CV sample. For more ideas beyond your final-year project, see the no-work-experience guide.

Step 1: choose one target role

A resume for a graduate software role should emphasise different evidence from a bank trainee or operations role. Choose a real vacancy and note its essential qualification, responsibilities, location and application format.

Do not start by choosing every skill from a generic list. Start by asking which requirement you can support with something you have built, analysed, tested, organised or communicated.

Step 2: describe your education accurately

Write the degree, institution, dates and current completion status. Students from FAST, NUST, UET, LUMS, COMSATS and other institutions can use the same evidence-based approach. The name of a university does not replace an explanation of your work, and this guide does not claim an endorsement from those institutions.

Use the campus and awarding institution as they appear in your records. If you are still studying, write an expected graduation date. Include relevant coursework when it helps establish a skill; avoid listing every course on the transcript.

A fictional entry could read:

BS Computer Science — [actual university and campus] 2022–2026 · [actual CGPA and scale, if included] Relevant coursework: databases, software engineering and data structures.

Step 3: turn the final-year project into evidence

Record the problem, team size, your role, tools, tests and completed outputs. Distinguish what the team delivered from what you personally implemented.

Fictional example:

Final-year project: Campus room booking Four-person team · September 2025–May 2026

• Implemented a React booking form with validation for invalid date and time ranges.
• Built Node.js reservation endpoints and tested duplicate booking requests.
• Wrote the schema notes and setup instructions for the team's PostgreSQL database.

Weak version: “Made an excellent FYP using modern technology.”

Improved version: “Built Node.js reservation endpoints and tested duplicate booking requests.”

The improved sentence identifies the work. A grade, prize or measurable result can be added when accurate, but a fabricated percentage weakens the evidence. If a project is not yet complete, label it In progress and describe finished work only.

Step 4: use university achievements in context

Include a competition, scholarship, teaching activity or society contribution when it supports the application. Name what you achieved and the scope. “Selected for [actual scholarship] in [year]” is clearer than “Award-winning student” without a named award.

For a LUMS business student's bank-trainee application, a coursework reconciliation or analysis project may be more relevant than a web-development certificate. For a UET engineering student, test procedures and a design contribution may matter more than unrelated society membership. These are examples of selecting evidence, not claims about any institution's curriculum or hiring outcomes.

Step 5: include internships honestly

Give the title, organisation and dates. Explain tasks you actually completed and any supervision context needed to avoid overstating responsibility.

Fictional example: “Updated form-validation rules under supervision and recorded reproducible defects against the team's acceptance criteria.” This is more informative than “Managed the company's software department.”

If you never completed an internship, omit the section. A classroom project is not an internship, even if you used professional tools. Label freelance client work, volunteering and personal projects separately.

Step 6: select supported skills

Choose tools and methods demonstrated by the entries. A graduate software resume might list React, Node.js, SQL and Git when those appear in projects. A business resume might list Excel lookups, chart preparation and record checking when those are supported by coursework.

Avoid rating yourself “90%” in communication or Python. Describe your experience and provide evidence. Use the software engineer guide for a technical version and the tailoring guide to connect evidence to a particular vacancy.

Step 7: export and check the application

Choose a readable template and follow the first-resume walkthrough. Open the exported file, confirm its text is selectable and inspect it on a phone. Test your email and project links.

Check the vacancy for academic thresholds, required documents, deadlines and file format. For a bank or public-sector application, complete the specified form as well as any requested CV. Do not assume a general resume replaces official eligibility fields.

Create your graduate resume after collecting your evidence. If you have a previous document or LinkedIn PDF, the import guide explains how to reuse it; review imported details carefully.

Common questions

Should I hide that I have no paid experience?

No. Use accurate section labels and present relevant projects prominently. Graduate hiring teams can assess the evidence without a fabricated job title.

Can I include a low CGPA?

Provide it if requested. If you choose to include it, use the correct scale and figure. Do not alter or conceal mandatory eligibility information.

Do I need a two-page resume to look professional?

No. A readable page with useful evidence can be enough. Expand only when the extra content supports the application.

Preview the Quiet Space template. Its spacious single-column layout gives your final-year project, internship and education entries room for useful evidence. Keep the finished document concise and check the page count with your own content.