Menu

Individual skill

software-engineer-resume

0upvotes

Writes software engineering resumes for frontend, backend, full-stack, mobile, platform, DevOps, SRE and security engineering roles. Emphasizes technical decisions, delivered systems and defensible impact; use data-resume for analytics or model-focused work and resume-tailor for one specific posting.

plugins/reactive-resume/skills/software-engineer-resume/SKILL.md

Read pinned source

Source commit 77f5580a67d1e4379978e80410e0cd02ea3fd446

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
45,676
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Software Engineer Resume

Use the user's evidence, never facts or numbers from worked examples. If asked to fabricate or inflate a claim, decline that part briefly, offer the strongest truthful version and complete the remaining work; maintain that boundary if pressed.

Write a resume that lets a reviewer understand what the engineer built and owned. Work from supplied history and artifacts; no account or sibling skill is required.

## Find the engineering evidence

Establish the target specialty and level. For each relevant role or project, ask what shipped, the user's contribution, technical constraints, users or workload, and the observed result. Ask about a design choice or tradeoff rather than requesting a list of fashionable technologies.

| Target                 | Useful evidence to look for                                                                                                       |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Frontend/mobile        | User workflows, accessibility work actually tested, rendering or startup measurements, platform constraints and release ownership |
| Backend/platform       | Interfaces, data consistency, migrations, service boundaries, load and operational behavior                                       |
Back to top