So someone has asked why achievements are under education on Careers. I answered with a follow up:

Why not have Achievements for each Experience block? I was not getting any action, so I thought I would re-state the question.

I feel like I really started to get things done when I had a real job and that stuff doesn't really belong in Responsibilities.


The Achievements for the position should go under that position's Experience block, not as a separate heading.

Something like this:

Microsoft - 1994-1999

  • Created Excel VBA
  • Spent the next 9 years talking about it

This is a normal practice for HR, and I realize that as programmers we want to have things clearly delineated, but that's not normal practice for HR companies and hiring managers.

  • You are Joel's alter ego? ;) – DVK Oct 16 '09 at 14:29
  • so how do you delineate achievements and responsibilities? – RedBlueThing Oct 16 '09 at 14:36
  • perhaps responsibilities should just be achievements instead? – RedBlueThing Oct 16 '09 at 14:37
  • Responsibilities and acheivements go together, intermixed under that job heading. – George Stocker Oct 16 '09 at 14:46
  • I guess that would be my contention – RedBlueThing Oct 17 '09 at 3:25

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .