Hiring managers and recruiters look for evidence of initiative, collaboration, and real-world coding. Open-source contributions and side projects demonstrate exactly that—especially for junior engineers or career-changers who may lack traditional work experience. But listing them poorly can hurt more than help.
A dedicated section titled “Open-Source Contributions” or “Key Projects” (placed after work experience) is the clearest way to organize these. Avoid lumping them under “Hobbies” or burying them at the bottom.
Every project entry should mirror a job entry. Follow this template:
Open Source
Open-Source Contributor – React (facebook/react)
Notice the shift from vague to specific. Quantify impact (number of PRs, percentage improvement, issue count).
If you have 2+ notable open-source contributions, create a separate “Open-Source Contributions” section right below “Work Experience.” Side projects that are not open-source can go in a “Projects” section. For early-career engineers, it’s acceptable to put “Projects” before “Experience” if you lack relevant job history.
Rule of thumb: If a project or contribution is directly relevant to the job you’re applying for, give it a line in the summary or top third of the resume. Otherwise, list it in a dedicated section near the bottom.
Side Projects
Projects
Applicant Tracking Systems (ATS) can parse projects sections if you use standard headings and avoid graphics or tables. Use a plain text format with consistent bolding for project names. Avoid PDFs with non-text elements (like icons or columns) that ATS may misread.
ATS Checklist:
Yes, but prioritize relevant contributions. If you’re a senior engineer, limit to your most impressive 2–3 open-source contributions and place them near the bottom. Work experience should take the primary spotlight.
Don’t list unfinished projects. Only showcase projects that are complete enough to be used or demonstrate a clear outcome. A half-finished project can signal lack of follow-through.
Only if those changes are notable and merged. A fork with one typo fix is not impressive. Focus on projects where you added significant functionality or solved a real problem.
If you have permission, list it generically without revealing proprietary details. Describe the architecture, the languages used, and the impact (e.g., “Reduced load time by 30% for an e-commerce frontend”). If you can’t even do that, skip it.
Always include a link if the project is public. Use a short URL or a LinkedIn link if your GitHub is clean. Make sure the repo has a good README and clean code.
Want to make sure your resume is ATS-friendly? Check it for free with PrismResume—no sign-up required.
Not sure how your resume reads? Check it for free on PrismResume to spot missing keywords and formatting issues.
Wondering how your own resume holds up?
Check it free — no sign-upLearn how to convert a Chinese university capstone project into a US-format resume entry that competes with industry internships.
Learn how to write a data engineer resume from scratch when your past job titles don't say 'data engineer.' Concrete before/after examples, checklist of transferable skills, and formatting tips to…
Learn the exact 3-part formula for writing a resume objective when transitioning from accounting (Chinese background) to data analytics in the US. Includes before/after example, ATS formatting tips, a
Loading…