Illustrative example · fictional profile, real scoring rubric

Full-stack engineer example

91
out of 100
Resume Readiness Score
Medium confidence · 4 repos · 4 READMEs

Maya, here's what we found

Maya, taskpilot is the project that proves the 'full-stack' label instead of just claiming it: a real database, auth, tests, and a container, front to back.

Splitline backs it up with a second end-to-end app, so the story holds up beyond one repository.

100
Project Quality
100
Technical Breadth
100
Documentation
60
Engineering Practices
95
Career Presentation
Turn this into a complete resume →

This is a fictional example. Run your own username above.

Standout project

taskpilot

The one to lead your resume with. It checks every box a recruiter skims for.

Substantial codebaseWell documentedDeployment-ready (Docker or infrastructure code)Engineering practices visible (tests or CI)External adoption or collaboratorsActively maintained

Top repositories

splitline★★★★substantial · documented
gateway★★★documented · CI
maya.devdeployable · active

Read like a code review

+Your deployment experience is visible: containerized or infrastructure-defined projects read as production-minded.
+Most of your top projects are documented, which is rarer than it should be.
+Recent, maintained work: your most important repositories show current activity.
+Automated pipelines show up in your work, a strong engineering-practice signal.
Presentation looks solid; the next lever is measurable impact statements in each README.

Strongest languages

TypeScript
84%
CSS
12%
JavaScript
3%
Dockerfile
1%

Detected stack

Frameworks
ExpressNext.jsReact
Data & infrastructure
PostgreSQLVercelDocker
CI/CD
GitHub Actions

Evidence used

Everything above is computed from this. Nothing else.

4repos analyzed
4READMEs
2Dockerfiles
2CI workflows
72stars
174 KBof code
What a recruiter probably sees
"An engineer who can own a feature from schema to deployed UI, comfortable with TypeScript across the stack and with the database and auth that most portfolios skip."

Based on the public repositories analyzed, a recruiter is likely to infer an engineer who can own a feature from schema to deployed UI, comfortable with TypeScript across the stack and with the database and auth that most portfolios skip. The gap is scale: a line in each README about users or data volume would turn capability into impact.

@ships-on-fridays · analyzed Jul 20, 2026zelume.io/github-resume

Recruiter visibility

100%

of expected frontend signals present · heuristic

Drafted from the evidence

Written only from the repository evidence. No invented numbers.

taskpilotBuilt a full-stack task manager with Next.js and PostgreSQL including authentication, containerized with tests running in CI
splitlineShipped an expense-splitting app with a React front end and a Node/Express API backed by PostgreSQL

Where it lands in the editor

Maya Chen
github.com/ships-on-fridays
Projects
  • Built a full-stack task manager with Next.js and PostgreSQL including authentication, containerized with tests running in CI
  • Shipped an expense-splitting app with a React front end and a Node/Express API backed by PostgreSQL
Skills
TypeScript, CSS, JavaScript, Dockerfile, Express, Next.js, React, PostgreSQL, Vercel, Docker, GitHub Actions
Experience
  • Software Engineering Intern, Freshbooks (Summer 2025)

That's the free analysis. The resume takes one more click.

  • Complete resume from all projects
  • ATS optimization
  • Tailoring to a posting
  • Cover letter
  • Full editor
Turn this into a complete resume →

Run your own username →