3 ms·
Not sure if this will translate to your situation, but I eventually figured out that resumes need to show I created specific tangible benefits to whomever was m
by jamesbritt 17y ago
Not sure if this will translate to your situation, but I eventually figured out that resumes need to show I created specific tangible benefits to whomever was my employer at the time. For example, rather than say "Have 5 years of Blub", I'd was better off saying, "Wrote code in Blub that reduced transaction processing time, resulting in greater sales of foo."
Are there things in your experience that demonstrate the ability to add value (even if the overall project failed)?
Brought a product to market? Improved overall development time? Unless you're applying for some grunt cog coder job, I think (or hope, at least) that showing you are capable of producing value under pressure would be of most interest.
Whoever hires you can teach you the stuff you don't know.
- tjpick 17y ago> I'd was better off saying, "Wrote code in Blub that reduced transaction processing time, resulting in greater sales of foo." and better again by stating it as " wrote code in blub that increased sales by 25% and reduced transaction processing time by 50%" There are probably some smaller successful sub-projects within the startup failure.
- jamesbritt 17y agoYes, details can matter. Note to all of you working regular jobs that you will eventually leave: Pay attention now to the value you are adding, and keep notes. It's very hard to recall these sorts of details when you are depositing your final paycheck. It really does look better when you have some actual numbers, and better yet when you know they are true. Even if you can only say, "Was part of a team that ...", the fact that you pay attention value added, and not simply count the years spent sitting in a cube, speaks volumes.