2 min lesson
Quantify or it reads as junior
Name the parts in "Quantify or it reads as junior" and give the practical job of each one.
Step 1 of 2
Quantify or it reads as junior
Senior IC stories have numbers; junior stories have adjectives. "Improved onboarding" is a non-answer. The fix is to attach a metric to every story before you walk in, even if it's an honest estimate you can defend.
- "Made offboarding faster"
- "Access revoked across 20+ SaaS apps within 5 minutes of the HRIS termination event, down from same-day manual."
- "Reduced manual work"
- "Eliminated ~6 hours/week of provisioning clicks across the IT team."
- "Improved security"
- "Cut standing admin grants by 70% with just-in-time access, with no new tickets."
- "Helped with the acquisition"
- "Migrated 140 users and 160 devices to our tenant in 9 days with zero lockouts."
Defensible estimates beat vague adjectives every time.
When you tell the automation story, name the failure mode you designed against. "The script was idempotent and ran in dry-run first, because a deprovisioning job that double-fires or partially completes is a security and lockout risk." That one sentence separates an engineer from someone who once wrote a Bash script.
"Onboarding went from a two-day manual checklist to fifteen minutes, and every step is audited. I owned it because new hires were losing their first two days, and a missed offboarding step left live access behind. I built it on an HRIS webhook: a hire or termination event fires a job that creates or revokes accounts over SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition.. The job is idempotent, so a retry never double-provisions, and it runs in dry-run first so I can diff the plan before it touches the tenant. Looking back, the win wasn't the script. Offboarding stopped being a thing a human remembers to do. I kept a human approval only on the irreversible step, wiping the device, because that's the one I wanted a second pair of eyes on."
Don't let every story be a solo heroics tale. On a flat team, the ability to disagree with Security or Eng and still land a shared decision is a graded skill. If you can't name a time you were wrong or changed course after a partner pushed back, you're missing the story that carries most of the collaboration signal.