Portfolio and GitHub for International Jobs
How to pick projects, write clear READMEs, organize your GitHub profile, and place your links on your resume and LinkedIn for jobs abroad.
By G3 Infotech
4 minute read
When you apply for jobs abroad, your resume says what you have done. Your portfolio and your GitHub profile show how you do it: code, decisions, documentation and, for design, the process. The person reviewing your application may open those links before a technical interview, and what they find there counts for or against you.
The goal is not to show everything you have ever built. It is to show, with a few well-chosen examples, that you solve problems in a clear and organized way. A presentation that makes sense in a few minutes makes the reviewer's job easier.
Pick a few projects, and the right ones
Do not put every experiment, old study project and abandoned repository in your portfolio or at the top of your GitHub. Choose the ones closest to the role you want.
- Pick three to five main projects.
- Prefer projects where you can explain the problem, the solution and the result.
- If you have open source contributions, include the ones that show code review and collaboration.
If you are a designer, show the process, from research to the final solution. If you are a developer, show the architecture, the code organization and the documentation. A small project that is well built and well explained says more than a large, confusing one.
The README is the project's shop window
The README is the first thing people see when they open a repository. It should answer, in a few minutes, what the project does and how to see it working. A good README has:
- A clear title and a short description of what the project does.
- Simple instructions to run the project locally.
- The list of technologies used.
- Screenshots or a short video of the project running, especially for design and front-end.
- The link to the live version, if there is one.
For jobs abroad, write in English. Use short, direct sentences without unnecessary jargon. If the reader has to guess how to run the project, you lose the chance to show what it does.
Organize your GitHub profile
Your profile is the page that brings everything together. Keep your bio up to date, with a link to your portfolio or personal website.
- Pin the repositories you chose to your profile. GitHub lets you pin up to six.
- Review the repository descriptions: one sentence on what each one does.
- Archive, or make private, repositories that are empty or no longer represent your work.
- Create a profile README: a repository with the same name as your username and a README.md file. GitHub shows that text at the top of your profile, which is a good place for a short introduction, your contacts and your main projects.
An organized profile shows care for details, which matters for people who code and for people who design.
Where to place your links
Your links need to be where reviewers look for them.
- At the top of your resume, next to your name or contact details.
- In the "About" section of your LinkedIn profile.
- In your LinkedIn contact info, in the website field.
- In your email signature, if you write directly to recruiters.
Use the same links everywhere. If you have a personal website, it can work as the central point, linking to your GitHub, your LinkedIn and your portfolio.
Common mistakes
Simple presentation details get in the way more than you might think. Avoid:
- Broken links or links to pages that are down.
- READMEs that do not explain how to run the project.
- Repositories with no description or with generic names like "test" or "project1".
- Low-resolution images, or images without context, in a design portfolio.
Before you send an application, test every link on a computer and on a phone.
How G3 Apply helps with this part
In G3 Apply, your GitHub and portfolio links go in as answers in Copilot training, in the section Answer the questions application forms ask most, in the Profiles and links group. Once you save them, the copilot uses those answers in your next applications, so you do not have to type the same links into every form that asks for them.
Wrapping up
A portfolio with a few well-chosen projects, an organized GitHub and links that are easy to find show care for the person reviewing your work. Set aside some time to review each part before your next batch of applications.