HTML Resume & Advices

View how the template looks at https://omaryasser.github.io/html-resume/resume.html.

Table of contents

• Usage
• Resume Advices
• Contributing

Usage

1. Edit the Template: Open the HTML template file and replace the information with your own details.

2. Preview the Changes: Use a web browser to open the edited HTML file and check that everything looks correct.

3. Print to PDF:

   • Once you're happy with the changes, open the HTML file in your browser.
   • Use the browser's Print function (Ctrl+P or Cmd+P on Mac).
   • Choose Save as PDF from the list of printers.
   • Set the layout and margins as desired, then save the file as a PDF.

This will give you a polished PDF version of the template with your custom information.

Resume Advices

Note: I am not an expert in building resumes, but I've seen a lot of them. I have reviewed many resumes and found myself giving some common comments and tips that I'll share in this post.

1. Use Simple Style

Recruiters and resume reviewers may have different preferences regarding the template and the colors. So, choose a simple black and white template (and blue for links) and try to impress the resume reviewer with the content rather than the colors.

Add enough spacing between lines and enough margin so that the resume is satisfying for the reviewer’s eyes. You don't want the reviewer to skim your resume because it is not comfortable for their eyes.

2. Keep it Professional

Resumes are good indicators of how keen and organized the candidate is. Don’t use smiley faces or slang language. Don’t make grammar mistakes. Even small mistakes like punctuation mistakes may leave an impression.

3. Keep it Relevant & Short

If you are a fresh graduate, then I'd recommend having a one-page resume.

Mention only the information that is relevant and would be interesting considering the interests of the company you are applying to. Prioritize what you will include or exclude in your resume based on the company's interests and the specific role you are applying for. This means that you may end up building different resumes for different companies or different job roles.

Resumes are never exhaustive of your history. Don't try to add every tiny detail, or it may leave an impression of a shortage of accomplishments.

Add links to your profiles on LinkedIn, GitHub, and others (e.g., a competitive programmer should add a link to their profile on one of the online judges like Codeforces). Make those links visible (at the beginning of the resume). Those links don't take significant space in the resume but are rich sources of information about you.

4. Describe your Contributions Clearly

Don’t just say that you have contributed to project X or that you were part of a team who worked on project X. Say exactly what you did and what your main responsibility was in it. Without specifying, a reviewer may get the feeling that you were not a key contributor to the project, so they may not consider the project as an indicator of one of your skills.

Clarify your mastery level of every skill, tool, and language you mention (e.g., Main: Java, C++. Others: Python).

5. Key Components of Project Description

Make the descriptions of your projects consistent with each other (i.e., structure them in the same way). Key components of a project description are:

• A descriptive name of the project (i.e., not the project's nickname because this will add no information to the reviewer)
• A brief summary of the goal of the project
• The number of team members
• Your main responsibility in the project
• Technologies and skills demonstrated in this project
• If it is a coding project, add a link to the project code on GitHub.

6. Sort the Sections

This is again related to trying to optimize how relevant your Resume structure is to your reviewer. I'd add the sections that include the most impressive accomplishments at the beginning.

7. Selected-courses Section

If you are a fresh graduate, consider adding a section in which you mention some non-basic and non-introductory courses that are as relevant as possible to the interests of the company you are applying for.

8. Get ATS Insights

Warning: Before using these systems, hide your personal information like email address, phone number, and home address to not get spammed later and to not have them collected and used without your consent.

Many companies use software to filter resumes in the screening phase. These systems are called Applicant Tracking Systems (ATS), and there are some free and some paid versions of them on the internet. Run your CV against some of them to get some insights into what can be improved to pass these systems' tests.

Contributing

We welcome contributions! To get started:

1. Fork the Repository: Click on "Fork" at the top right of this page to create your own copy of the repo.
2. Clone Your Fork: Clone your forked repository to your local machine with:

   git clone https://github.com/your-username/repo-name.git

3. Create a New Branch: Create a branch for your changes:

   git checkout -b your-branch-name

4. Make Your Changes: Edit the code or documentation as needed.
5. Commit and Push:
   • Commit your changes with a descriptive message:

     git commit -m "Brief description of your changes"

   • Push the branch to your fork:

     git push origin your-branch-name

6. Open a Pull Request: Go to the original repository and open a pull request with a clear description of your changes.

Thank you for contributing! 🎉