Skip to content

Latest commit

 

History

History
29 lines (23 loc) · 2.75 KB

File metadata and controls

29 lines (23 loc) · 2.75 KB

Examples

Fictional, generic samples you can copy or use as a structural template. Replace all contact details and narrative with your own before applying.

File Purpose
cv-example.md Full CV in markdown — ML / platform engineer profile
cv-example-backend-engineer.md Full CV — backend / distributed systems profile
cv-example-fullstack-engineer.md Full CV — full-stack (web UI + APIs + data) profile
cv-example-data-engineer.md Full CV — data / analytics engineering profile
cv-example-frontend-engineer.md Full CV — frontend / UI engineering profile
cv-example-mobile-engineer.md Full CV — native iOS / Android / mobile profile
cv-example-devops-engineer.md Full CV — DevOps / platform / SRE-style profile
cv-example-product-manager.md Full CV — product / platform PM profile
cv-example-engineering-manager.md Full CV — engineering management / tech-lead-to-EM profile
cv-example-security-engineer.md Full CV — application / cloud security engineering profile
cv-example-qa-engineer.md Full CV — QA / test automation engineering profile
cv-example-solutions-architect.md Full CV — solutions / enterprise architecture profile
article-digest-example.md Optional proof points digest for evaluations
sample-jd.md Fictional job description in markdown — template shape for local:jds/… pipeline entries (real JDs live under jds/, gitignored)
sample-report.md Illustrative evaluation report layout

To start from a template: copy one of the CV files to the repo root as cv.md, then edit every section. See docs/SETUP.md for the full setup flow.

For contributors

Pull requests that add more fictional CV archetypes (same idea as the table above) are welcome. See CONTRIBUTING.md for branch workflow and the npm run verify gate.

Keep samples obviously synthetic: placeholder contact fields (example.com, generic company names), no real people or employers, and roughly the same markdown shape as the existing files (header contact block, Summary, Experience, Projects, Education, Skills — adjust section titles only if the role genuinely needs a different layout). Optional digests and sample-report.md should stay illustrative, not copies of real evaluations.