About resumefromgit.com
Why this exists, how it works technically, and what it deliberately does not do.
resumefromgit.com turns any public GitHub profile into a visual CV and an ATS-safe PDF resume. There is no signup, no account, and nothing to install. Type a username, get a page.
Why it exists
Most developers already have years of evidence about how they work sitting in public: the languages they actually write, the projects other people depend on, how consistently they contribute. That evidence is spread across a profile page, a repository list and a contribution graph, none of which is laid out to be read quickly or handed to someone in a hiring process.
This site assembles it into one page, and then into a resume that an applicant tracking system can parse. That second part matters more than it sounds: a great deal of well-designed resume output is unreadable to the software that screens it first.
How it works
When you request a profile, the server makes a single GraphQL query to GitHub’s public API and caches the result for twelve hours. Every chart - the language donut, the repository bars, the contribution heatmap - is plain SVG rendered on the server. No charting library is shipped to your browser, which is why the pages load as quickly as they do.
The PDF is built entirely in your browser. The library that generates it is only downloaded when you click the button, and the resume fields you fill in are stored in your own browser rather than on our servers.
What it deliberately does not do
- No accounts. There is nothing to sign up for and no password to lose.
- No access tokens. We never ask you to authorise anything against your GitHub account. The tool only reads what GitHub already publishes.
- No scoring or ranking of people. The charts describe activity; they do not grade anyone, and a quiet contribution graph is not a verdict on an engineer.
- No private data. The credential the server uses cannot read private repositories.
Limits worth knowing
GitHub’s public contribution calendar excludes a lot of real work: private repositories (unless the owner opts in), commits on non-default branches, work in unmerged forks, and any commit authored with an email that is not registered to the account. If a profile looks emptier than it should, that is usually why - we wrote up the details separately.
Get in touch
Corrections, removal requests and bug reports are welcome via the contact page.
Not affiliated with GitHub
This is an independent project, not affiliated with, endorsed by, or associated with GitHub, Inc.