Technical WritingUnit 611 min read
Unit 6 – Resume, Cover Letters & Job Applications: formats, content, and best practices
Unit 6 of Technical Writing: a comprehensive guide to drafting professional resumes, cover letters, and job‑application letters, with definitions, structure, examples, ATS tips, ethical considerations, and exam strategies for TU/PU/NEB students.
Key points
- A resume is a concise, achievement‑focused record that must be tailored to each job and pass Applicant Tracking Systems.
- A cover letter complements the resume by linking your skills to the employer’s needs and showing personality.
- A job‑application letter follows a formal business‑letter format and highlights suitability for a specific vacancy.
- Use action verbs, quantifiable results, and clear layout; avoid common pitfalls such as vague language or false claims.
- Real‑world hiring practices at companies like Ncell, Daraz, and Google illustrate how these documents are screened and evaluated.
1. Definitions
| Term | Purpose | Typical Length | Key Audience |
|---|---|---|---|
| Resume | Summarize education, experience, skills, and achievements to obtain an interview. | 1 – 2 pages (max 3 for senior roles) | Recruiters, HR, hiring managers, ATS |
| Cover Letter | Explain why the applicant is a good fit, connect resume highlights to the job description, and convey motivation. | ½ – 1 page | Same as resume; often read first by recruiter |
| Job‑Application Letter | Formal request for a specific vacancy, often when a job posting does not provide an online application form. | 1 page | Hiring manager or HR officer |
2. Resume Components
- Header – Full name, professional title, phone, email, LinkedIn or portfolio URL.
- Professional Summary / Objective – 2‑3 sentences that state the candidate’s core value proposition.
- Key Skills – Bullet list of hard and soft skills, preferably aligned with the job posting.
- Work Experience – Reverse‑chronological entries; each includes:
- Job title, company, location, dates (MM/YYYY – MM/YYYY)
- 3‑5 bullet points beginning with strong action verbs, quantifying results (e.g., “Improved page‑load speed by 30 %”).
- Education – Degree, institution, graduation year, GPA (if ≥ 3.5) and relevant coursework.
- Projects / Certifications – Especially for IT students; list project name, tools used, outcome.
- Additional Sections – Publications, languages, volunteer work, awards.
2.1 Resume Formats
| Format | When to Use | Advantages | Disadvantages |
|---|---|---|---|
| Chronological | Clear career progression; most industries | Easy for ATS; highlights steady growth | Gaps in employment become obvious |
| Functional | Career changers, limited experience | Emphasizes skills over dates | ATS may reject; recruiters view as “hiding” gaps |
| Combination | Mix of both; mid‑career professionals | Balances skills and timeline | Slightly longer; needs careful design |
3. Cover‑Letter Structure
[Your Name] [Street Address] [City, Postal Code] [Phone] | [Email] | [LinkedIn]
[Date]
[Hiring Manager’s Name] [Company Name] [Company Address]
Dear Mr./Ms. _______,
Paragraph 1 – Hook
State the position you are applying for, where you found the posting, and a compelling reason you are excited about the role.
Paragraph 2 – Match
Select 2‑3 key requirements from the job ad and illustrate how your experience meets each, using concrete numbers.
Paragraph 3 – Value Proposition
Explain what you will bring to the company (e.g., “I will reduce UI bugs by 40 % within the first three months”).
Paragraph 4 – Call‑to‑Action
Express eagerness for an interview, mention attached resume, and thank the reader.
Sincerely,
[Signature (if printed)]
[Typed Name]
3.1 Tone and Language
- Professional but personable – avoid slang, use “I” sparingly, focus on the employer’s needs.
- Active voice – “Developed a mobile app” rather than “A mobile app was developed”.
- Quantify – numbers, percentages, time frames give credibility.
4. Job‑Application Letter (Formal Business Letter)
[Your Name]
[Street Address]
[City, Postal Code]
[Phone] | [Email]
[Date]
The Principal
[School/College Name]
[Address]
Subject: Request for Logistic Support to Organize “Social Media Impact” Program
Dear Sir/Madam,
I am writing to request the use of the school auditorium, audio‑visual equipment, and volunteer assistance for a one‑day program titled “Impact of Over‑use of Social Media on Youths,” scheduled for 15 December 2026.
The program aims to raise awareness among 300 students, featuring a panel of experts, interactive workshops, and a short documentary screening. We anticipate collaboration with the Student Council and the ICT department.
In return, the school will receive a detailed post‑event report, promotional material, and a certificate of appreciation for the staff involved.
I kindly ask for your approval and the allocation of the mentioned resources. I am available to discuss the logistics at your convenience.
Thank you for considering this request.
Yours faithfully,
[Signature]
[Typed Name]
4.2 Key Parts
| Part | Content |
|---|---|
| Header | Sender’s address, date, recipient’s address |
| Subject line | Concise statement of purpose |
| Salutation | Formal (“Dear Sir/Madam”) |
| Opening | State purpose and reference (event, date) |
| Body | Details, justification, benefits |
| Closing | Polite request, gratitude |
| Signature | Hand‑signed (if printed) and typed name |
5. Writing Process & Revision Techniques
- Analyze the Job Description – Highlight required skills, keywords, and responsibilities.
- Draft the Resume – Fill each section using the highlighted keywords; keep layout clean (Arial/Calibri 10‑12 pt, 0.5 in margins).
- Create the Cover Letter – Mirror the language of the posting; use the “STAR” (Situation‑Task‑Action‑Result) method for achievements.
- Peer Review – Exchange drafts with a classmate; check for clarity, grammar, and consistency.
- ATS Test – Paste the resume into a free ATS scanner (e.g., Jobscan) to see match percentage; adjust headings and keywords accordingly.
- Final Proofread – Read aloud, use spell‑check, and verify contact details.
6. Ethical Considerations & Plagiarism
- Truthfulness – Fabricating degrees, dates, or achievements is unethical and can lead to termination.
- Originality – Do not copy resume templates verbatim; adapt language to reflect personal experience.
- Citation – If you quote a published project report, cite it in a footnote (rare in resumes but acceptable in academic CVs).
7. Worked Example: Building a Resume for a Computer Engineer
Scenario: You are a Computer Engineer with 2 years of experience at “TechSolutions Pvt. Ltd.”, holding a B.Sc. in Computer Science from ISM, and you have completed a certification in “AWS Solutions Architect”.
Step‑by‑Step
| Section | Content (filled) |
|---|---|
| Header | Ramesh K. Shrestha <br>Software Engineer <br>+977‑984‑1234567 <br>ramesh.shrestha@email.com <br>LinkedIn: linkedin.com/in/rameshks |
| Professional Summary | “Detail‑oriented Software Engineer with 2 years of experience developing scalable web applications using Java, Spring Boot, and AWS. Proven ability to improve system performance by 25 % and lead a team of 4 junior developers.” |
| Key Skills | • Java, Spring Boot, REST APIs <br>• AWS (EC2, S3, RDS) <br>• Front‑end: React, HTML5, CSS3 <br>• Database: MySQL, PostgreSQL <br>• Agile Scrum, Git, CI/CD |
| Work Experience | Software Engineer – TechSolutions Pvt. Ltd., Kathmandu (Jan 2024 – Present) <br>– Designed and implemented a micro‑service for payment processing, handling 10 k transactions/day, reducing latency by 30 %. <br>– Migrated legacy monolith to AWS, cutting hosting costs by 20 %. <br>– Mentored 4 interns, achieving 95 % project‑completion rate. |
| Education | B.Sc. Computer Science, Institute of Science and Technology, Pokhara (2019‑2023) – GPA 3.78/4.0 |
| Certifications | AWS Certified Solutions Architect – Associate (2024) |
| Projects | E‑Commerce Platform – Built a full‑stack online store using React & Spring Boot; integrated Stripe API, achieving 1 k daily users within 3 months. |
| Languages | English (Fluent), Nepali (Native) |
| Volunteer | CodeClub Mentor, Kathmandu (2022‑2023) – taught Python to high‑school students. |
Result: The resume now contains 12 keywords from a typical “Java Developer” posting (Java, Spring, AWS, REST, Agile, Git, MySQL, CI/CD, micro‑service, performance, team lead, cost reduction). An ATS scan shows an 88 % match, well above the 70 % threshold.
8. Comparison Table: Resume vs. Cover Letter
| Aspect | Resume | Cover Letter |
|---|---|---|
| Length | 1‑2 pages | ≤ 1 page |
| Focus | Facts, achievements, skills | Narrative linking skills to job |
| Structure | Fixed sections (Header, Experience, etc.) | Paragraph format (Hook, Match, Value, CTA) |
| Tone | Concise, bullet‑pointed | Slightly more personal, persuasive |
| ATS Interaction | Directly parsed | Usually not parsed; scanned by recruiter |
| Customization | Keywords per job | Specific examples per employer |
9. Advantages & Disadvantages of Common Formatting Choices
| Choice | Advantage | Disadvantage |
|---|---|---|
| PDF format | Preserves layout across devices; preferred by many recruiters | Some ATS cannot read PDFs; may miss keywords |
| Word (.docx) | ATS‑friendly; easy to edit | Layout may shift on different computers |
| Creative design (graphics, colors) | Stands out for design roles | ATS may reject; ATS sees graphics as noise |
| One‑column layout | Simple, ATS‑compatible | May look plain for creative positions |
| Two‑column layout | Saves space, looks modern | ATS may mis‑read right‑hand column content |
10. In the real world
- Ncell’s IT recruitment portal uses an ATS that automatically rejects resumes lacking the keyword “Java Spring Boot”. Candidates who tailor their “Key Skills” section accordingly receive a higher interview call‑rate.
- Daraz’s UX team asks applicants to submit a cover letter that explains a specific design problem they solved. The hiring manager looks for quantified impact (e.g., “Reduced checkout abandonment by 15 %”). Successful letters directly reference the company’s recent “Black Friday” sales data.
- Google’s software‑engineer hiring requires a concise “resume summary” that mirrors the job description’s “build scalable systems”. Recruiters have reported that candidates who use the exact phrase “scalable systems” in their summary are shortlisted 30 % more often.
Worked real‑world tie‑in: A Nepali bank’s loan‑officer position required applicants to list “customer‑service metrics”. By stating “Handled 150+ client inquiries daily with a 98 % satisfaction rating,” the applicant demonstrated measurable performance, mirroring the bank’s KPI of “≥ 95 % satisfaction”.
11. Common Mistakes & How to Avoid Them
| Mistake | Why it hurts | Fix |
|---|---|---|
| Using “Objective” instead of “Professional Summary” | Objective sounds generic and self‑focused. | Write a summary that highlights what you bring to the employer. |
| Listing duties instead of achievements | Recruiters want impact, not a job description. | Start each bullet with an action verb and add a result (e.g., “Implemented… resulting in…”). |
| Copy‑pasting the same cover letter for every job | Shows lack of research and personalization. | Tailor each paragraph to the specific role and company. |
| Including irrelevant hobbies | Takes up valuable space and distracts. | Only list hobbies that demonstrate transferable skills (e.g., “Team captain – leadership”). |
| Spelling/grammar errors | Signals carelessness. | Use Grammarly or peer‑review before submission. |
12. Tools & Resources
- Microsoft Word / Google Docs – Templates, style guides.
- Canva Resume Builder – Visual designs (use only for creative roles).
- Jobscan – ATS keyword matching.
- Grammarly – Grammar and tone checking.
- LinkedIn – Profile alignment with resume; recruiters often cross‑check.
13. Exam tip
- Understand the marking rubric: Examiners award points for (a) correct format (header, salutation, body, closing), (b) appropriate language (formal, active, quantified), (c) completeness of required sections, and (d) neat presentation (consistent fonts, alignment).
- Plan 5 minutes before writing: Identify the job title, pick 2‑3 key requirements, and decide which achievements match them.
- Use the “STAR” method in bullet points – Situation, Task, Action, Result – to ensure each statement is concise and result‑oriented.
- Leave a blank line between sections and underline the heading (e.g., Work Experience) to make the layout clear for the marker.
- Proofread aloud at the end; a single typo can cost marks in the “language accuracy” criterion.
Based on the TU BIT syllabus for Technical Writing (ENG305), unit 6.
Discussion
Loading…