Resume templates, by role
A template is a starting point — the interviews come from tailoring it to each posting. Pick your role to see what a tailored CV looks like, line by line.
Built on public labor data
Role structure follows the U.S. Department of Labor’s O*NET-SOC occupational classification. Salary figures come from the Bureau of Labor Statistics (May 2025 OEWS release), with the federal occupation category named and linked on every page.
This site includes information from O*NET OnLine by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. O*NET® is a trademark of USDOL/ETA. snipecv is not affiliated with or endorsed by USDOL/ETA.
Engineering & AI
Software Engineer resume
Every engineering posting names a different stack and seniority. Keep one source CV and let snipecv re-emphasise the languages, systems, and impact each role screens for.
See the templateAI Engineer resume
Every AI posting means something different — LLM apps, RAG pipelines, fine-tuning, evals, or classic ML in production. Keep one source CV and let snipecv re-emphasise the stack and outcomes each posting actually screens for.
See the templatePrompt Engineer resume
Prompt engineering postings range from LLM app work to eval design to AI content ops. One source CV, re-weighted per posting — with measurable model-behavior wins up front.
See the templateMachine Learning Engineer resume
Training-heavy research role or deployment-heavy MLOps role? snipecv re-frames your models, pipelines, and production wins to mirror what each posting screens for.
See the templateDevOps Engineer resume
One posting means Kubernetes and Terraform, the next means CI/CD and developer experience. Keep one source CV and re-emphasise the pipeline, infra, and reliability outcomes each posting names.
See the templateSite Reliability Engineer resume
SRE postings split between ops-heavy on-call roles and software-heavy platform roles. Keep one source CV and re-weight the SLOs, tooling, and incident outcomes each posting screens for.
See the templateCloud Engineer resume
AWS shop, Azure enterprise, or multi-cloud? Keep one source CV and re-emphasise the provider services, infrastructure-as-code, and migration wins each posting actually lists.
See the templateCybersecurity Analyst resume
SOC monitoring, incident response, GRC, or vulnerability management — each posting weights them differently. Keep one source CV and re-emphasise the detections, response wins, and frameworks each role screens for.
See the templateSolutions Architect resume
Pre-sales SA, cloud architect, or enterprise architect? The title spans three jobs. Keep one source CV and re-weight the designs, migrations, and business outcomes each posting actually means.
See the templateFrontend Developer resume
React shop, Vue team, or framework-agnostic design-systems role? Keep one source CV and re-emphasise the frameworks, performance wins, and UI craft each posting screens for.
See the templateFull-Stack Developer resume
Every full-stack posting leans one way — React-heavy product work, API-heavy backend, or a bit of everything at a startup. Keep one source CV and re-weight the stack to match each lean.
See the templateQA Automation Engineer resume
Selenium legacy suite, Playwright greenfield, or API-test heavy? Keep one source CV and re-emphasise the frameworks, coverage wins, and release-confidence outcomes each posting names.
See the templateEntry-Level Software Engineer resume
With no full-time experience, projects and internships carry the screen. Keep one source CV and re-emphasise the stack, shipped work, and measurable outcomes each junior posting lists.
See the template
Data & Analytics
Data Analyst resume
Every analyst posting names a different stack — SQL, dbt, Tableau, Looker, Python. snipecv re-weights your skills and impact to mirror the one in front of you.
See the templateData Engineer resume
Batch warehouse shop or streaming-first stack? snipecv re-weights your pipelines, tooling, and reliability wins to match the platform each posting names.
See the templateAnalytics Engineer resume
Some postings want a dbt-first modeler, others an analyst who ships pipelines. Keep one source CV and re-emphasise the modeling, testing, and metric-layer wins each posting actually screens for.
See the template
Healthcare
Registered Nurse resume
Med-surg, ICU, and ER postings ask for different things. Keep one nursing CV and let snipecv re-emphasise the right specialty, certifications, and patient-load metrics for each application.
See the templateTravel Nurse resume
Every contract posting names a different unit, EHR, and license mix. Keep one source CV and re-emphasise the specialty, compact licensure, and adaptability each assignment screens for.
See the templateNew Grad Nurse resume
No staff experience yet doesn’t mean no evidence. Keep one source CV and re-emphasise the rotations, preceptorship hours, and unit-matching skills each residency or first-job posting screens for.
See the templateICU Nurse resume
MICU, SICU, CVICU, neuro — every critical-care posting names different devices, ratios, and certifications. Keep one source CV and re-emphasise the acuity evidence each unit screens for.
See the templatePharmacy Technician resume
Retail counter, hospital IV room, or specialty pharmacy? Keep one source CV and re-emphasise the certifications, volume, and accuracy evidence each setting screens for.
See the template
Business & Management
Project Manager resume
Agile shop or PMP-driven PMO? snipecv re-frames your delivery record in the methodology and tooling each posting asks for, instead of one generic CV.
See the templateProduct Manager resume
A growth PM role and a platform PM role want different stories. snipecv surfaces the metrics, surface area, and craft each posting values — from one source CV.
See the templateAccountant resume
Staff accountant, AP/AR, or controller track? snipecv emphasises the right systems, compliance scope, and close metrics each posting screens for.
See the templateMarketing Manager resume
Demand gen, brand, or lifecycle? snipecv re-frames your wins in the channels and metrics each posting cares about, instead of a one-size-fits-all CV.
See the templateTechnical Product Manager resume
Platform PM, API product owner, or data-product lead? Keep one source CV and re-weight the shipped outcomes, technical depth, and stakeholder wins each posting actually screens for.
See the template
Stop rewriting your CV from scratch for every application.
Keep one CV under version control and let snipecv tailor it, job by job.