Ebazhanov/it-vacancies

Add best practices for writing CVs for IT jobs and tips for passing application filters

Open

#1 opened on Jul 27, 2025

View on GitHub
 (0 comments) (1 reaction) (1 assignee) (0 forks)github user discovery
good first issue

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We should create a guide or markdown file in the repo that includes:

📄 CV Writing Best Practices for IT Roles Tailor your CV for each job (use keywords from the job description)

  • Start with a strong summary (tech stack, years of experience, specialization)
  • Highlight measurable achievements (e.g., "Reduced load time by 40%...")
  • Keep formatting clean and ATS-friendly (no tables, minimal graphics)
  • List relevant tech skills and tools (including versions where helpful)

🔍 Tips for Passing Automated Filters / ATS (Applicant Tracking Systems) Use standard section headings: Experience, Skills, Education, etc.

  • Include keywords from the job description naturally in your CV
  • Avoid images, headers/footers, and columns
  • Use a common file format (PDF unless stated otherwise)

📌 Deliverables:

  • A new markdown file (e.g., cv-tips.md) or a new section in README.md
  • Optionally include sample CV snippets or templates
  • This could really help job seekers in tech fields and increase the repo’s value.

Contributor guide

Research direction
Create a new markdown file (e.g., cv tips.md) with sections on CV writing best practices for IT roles and tips for passing ATS filters. Include sample snippets or templates if helpful.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90