📄 RESUME ROAST #5

> "Software Engineer | Company XYZ | 2019 - Present
> • Wrote code for various projects
> • Fixed bugs
> • Attended daily standups
> • Participated in code reviews"

Roast time - what's the core problem across ALL four bullets? 👇

.
.
.

The roast: Every single bullet describes an ACTIVITY, not an OUTCOME. "Attended daily standups" is something literally everyone on the team does - it says nothing about YOUR specific contribution or impact, and takes up a bullet point that could've held something valuable.

The test for every resume bullet: could this exact sentence apply to any random person on the team, doing the bare minimum? If yes, cut it or rewrite it.

✅ Rewritten with the same underlying work, framed around outcomes:

> • Redesigned the checkout flow, reducing cart abandonment by 18%
> • Diagnosed and fixed a memory leak in the notification service, cutting server costs by $2K/month
> • Led code review standards adoption across a 6-person team, catching 30% more bugs pre-merge

Same person, same actual job - completely different resume. Numbers and outcomes aren't decoration, they're the entire point.

Look at your own resume - how many bullets describe activities vs. outcomes? Be brutally honest 👇