[christophberger]

You don't need to measure your impact. It's enough to describe it. "Helped a large client improving their web presence for achieving increased conversion rates." Of course, you were part of a team and of course, you can't show precise statistics. But if they existed, would those stats be worth anything to a recruiter? Your next job will be different in many aspects. No recruiter will read some stats and say, "oh, that person's work increased the company's revenue by 1.5%, so we expect the same result at our company."

In a CV, the impact you made is a story to tell, not a number to calculate.

[em-bee]

i was not very clear. as a lowly developer i am so far removed from the outcome that i have no clue what the impact of my work is supposed to be. i don't know if the bug i fixed affects 1% or 90% of the user base, or if the feature, like that new credit card processing service brings in a few new users, or thousands or none at all.

if there is a story to tell, it doesn't reach our team.