Zelume
Log inCreate resume
BuilderTemplatesHow it worksFree ToolsPricingBlogLog inCreate resume

Illustrative example · fictional profile, real scoring rubric

Backend engineer example

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

River, here's what we found

River, your profile reads like someone who ships services, not exercises.

The bookkeeping API is the anchor: documented, tested, and containerized, with infrastructure code sitting right next to it.

92
Project Quality
100
Technical Breadth
75
Documentation
50
Engineering Practices
82
Career Presentation
Turn this into a complete resume →

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

Standout project

ledgerline

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

queue-peek★★★★substantial · documented
infra★★documented · deployable
dotfiles★

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.
→A short README on each highlighted project would help a recruiter understand it in the thirty seconds they'll give it.

Strongest languages

Python
78%
HCL
14%
Shell
6%
Dockerfile
1%

Detected stack

Frameworks
FastAPI
Data & infrastructure
PostgreSQLRedisAWSDockerTerraform
CI/CD
GitHub Actions

Evidence used

Everything above is computed from this. Nothing else.

4repos analyzed
3READMEs
2Dockerfiles
2CI workflows
50stars
152 KBof code
What a recruiter probably sees
"A backend engineer comfortable owning a service end to end: API design, a real database, tests, CI, and the Terraform to stand it up."

Based on the public repositories analyzed, a recruiter is likely to infer a backend engineer comfortable owning a service end to end: API design, a real database, tests, CI, and the Terraform to stand it up. What the profile does not yet show is scale or production consequences, which a single sentence per README could fix.

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

Recruiter visibility

100%

of expected backend signals present · heuristic

Drafted from the evidence

Written only from the repository evidence. No invented numbers.

ledgerlineBuilt a double-entry bookkeeping API with FastAPI and PostgreSQL, containerized with CI running tests on every push
queue-peekCreated a Redis stream inspection tool with a terminal UI, covered by automated tests

Where it lands in the editor

River Osei
github.com/river-ships
Projects
  • Built a double-entry bookkeeping API with FastAPI and PostgreSQL, containerized with CI running tests on every push
  • Created a Redis stream inspection tool with a terminal UI, covered by automated tests
Skills
Python, HCL, Shell, Dockerfile, FastAPI, PostgreSQL, Redis, AWS, Docker, Terraform, 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 →