I work in IT. I’m not a pro­gram­mer, so I end up doing the odd jobs that no one else has any desire to do nor any idea how to do.  One item on the long list of my de facto respon­si­bil­i­ties is trou­bleshoot­ing. I help trou­bleshoot code that is still in devel­op­ment; I help the val­ida­tors trou­bleshoot while they test the sup­pos­edly fin­ished code; I trou­bleshoot secu­rity issues that come up in the field across the coun­try when the offi­cial sup­port per­son­nel are out of ideas.

I would like to lever­age that expe­ri­ence on my resume — high­light­ing the dynamic, problem-solving aspect of the job and down­play­ing the tech­ni­cal knowledge/experience aspect. Take two hypotheticals:

“I have expe­ri­ence trou­bleshoot­ing soft­ware through­out all stages of its devel­op­ment and I sup­port pro­duc­tion per­son­nel in trou­bleshoot­ing end-user issues.”

“I have expe­ri­ence trou­bleshoot­ing issues that come up across all lev­els of my team and our clients. I dynam­i­cally uti­lize my problem-solving skills by think­ing out­side the box to achieve busi­ness results.”

The first one is dry and more attuned for an IT job. The sec­ond makes me sound like a pre­ten­tious jerk with a thesaurus.

How do you trans­late what you do into resume-speak?