Who & why
Owns the moment of shipping — getting changes to users safely and predictably, no prod surprises. Manages release risk: scope, order, rollback. A dispatcher between finished code and live users. Without one: chaotic releases, prod regressions, no rollback plan, no release notes.
A day in the life
Morning: verify the release scope and that every change has a rollback plan / feature flag. Day: coordinate the rollout, run the go/no-go checklist (reversible migrations? deps deployed? monitoring ready?), make the call. Evening: watch metrics/alerts for hours, ready to roll back, write release notes.
Key skills
Hard: release strategies (blue-green, canary, feature flags), CI/CD, semver, DB migrations & reversibility, release monitoring, rollback runbooks. Soft: calm at ship time, checklist discipline, coordination, saying "no-go", incident comms.
Artifacts
Release notes, release plan, readiness checklist, rollback runbook. Readiness builds on DoD; pairs with Delivery Manager and DevOps/SRE.
How AI / vibe-coding boosts the role
Release notes from commits; go/no-go checklist; rollback runbook; release-risk scoring; post-release summary — with ready prompts.
Growth: Junior → Middle → Senior → Lead
Junior: checklist & notes under guidance. Middle: owns one product's release cycle. Senior: builds & automates the process, multi-team releases. Lead/Head: release engineering, often merged with DevOps Lead.
Common mistakes
Friday-evening releases; no rollback plan; "ship it all at once"; release notes "later"; go without readiness check.
What to learn
Blue-green/canary, feature flags, semver, reversible migrations, release checklists, release monitoring. Read: Continuous Delivery (Humble/Farley); Google SRE; trunk-based development.
Salary (RU)
Junior ~130–190k₽/mo, Middle ~190–300k, Senior ~300–430k. Often merged with DevOps/SRE; varies — check current data.
Laskoff agent mapping
No direct mapsTo; ship safety is the house rule "backup/branch before anything irreversible" + the deterministic guard-dangerous.sh hook; readiness confirmed by quest-verifier.
🤖 Persona prompt
You are a disciplined Release Manager. Help me ship safely and predictably. Before any rollout demand: release scope, a go/no-go checklist, a rollback plan (especially for DB migrations), a rollout strategy (canary/feature flag for risky bits). Score each change's regression risk. After release, advise which metrics/alerts to watch for the first hours. Write human release notes flagging breaking changes. Have the courage to say "no-go" if readiness isn't proven. No Friday-evening releases without reason.