Zelume
Log inCreate resume
BuilderTemplatesHow it worksFree ToolsPricingBlogLog inCreate resume

Illustrative example · fictional profile, real scoring rubric

DevOps engineer example

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

Priya, here's what we found

Priya, this reads like infrastructure someone actually operates, not a tutorial follow-along.

The GitOps cluster with ArgoCD is the anchor, and the reusable Terraform modules and shared Actions workflows show the instinct to make automation repeatable rather than one-off.

80
Project Quality
80
Technical Breadth
100
Documentation
30
Engineering Practices
90
Career Presentation
Turn this into a complete resume →

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

Standout project

k8s-homelab

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

tf-modules★★★★★substantial · documented
action-kit★★★documented · CI

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.
→Adding automated tests to your public repositories would strengthen your engineering story.

Strongest languages

HCL
72%
Shell
21%
TypeScript
4%
Dockerfile
3%

Detected stack

Data & infrastructure
AWSKubernetesTerraform
CI/CD
GitHub Actions

Evidence used

Everything above is computed from this. Nothing else.

3repos analyzed
3READMEs
0Dockerfiles
3CI workflows
55stars
76 KBof code
What a recruiter probably sees
"A platform engineer fluent in Kubernetes, Terraform, and CI/CD who thinks in reusable modules and pipelines."

Based on the public repositories analyzed, a recruiter is likely to infer a platform engineer fluent in Kubernetes, Terraform, and CI/CD who thinks in reusable modules and pipelines. The clearest next step is a README note on what these systems run in production and at what scale.

@yaml-whisperer · analyzed Jul 20, 2026zelume.io/github-resume

Recruiter visibility

60%

of expected frontend signals present · heuristic

Missing: A UI framework, Tests

Drafted from the evidence

Written only from the repository evidence. No invented numbers.

k8s-homelabRan a GitOps-managed Kubernetes cluster with ArgoCD and sealed secrets, provisioned as infrastructure-as-code
tf-modulesWrote reusable Terraform modules for AWS networking and IAM, validated in CI

Where it lands in the editor

Priya Nair
github.com/yaml-whisperer
Projects
  • Ran a GitOps-managed Kubernetes cluster with ArgoCD and sealed secrets, provisioned as infrastructure-as-code
  • Wrote reusable Terraform modules for AWS networking and IAM, validated in CI
Skills
HCL, Shell, TypeScript, Dockerfile, AWS, Kubernetes, 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 →