How best to indicate that I've been the "go-to person" on a resume

  • For the past 7 years or so, wherever I work, I end up becoming "the guy everyone goes to ask technical and programming questions". Because of that, I'm always "promoted" (sometimes formally, sometimes informally) to technical lead.

    How would you describe that trait in a resume? How would you describe this succinctly, and without sounding pretentious or snob? Is that even something you should put in your resume? BTW, here are the terms I though of:

    • Internal Technical Consultant
    • Internal Tech Guru (that's kind of snob, actually)
    • Main point of contact for technical questions (does that even achieve what I'm trying to tell the reader?)

    In my last application, i used he term "original gangsta" to describe this role. I wrote that CV in a bit of a rush late at night, i have to confess. I got the job.

    Excuse me, Mr. Officer.

  • Isaac Moses

    Isaac Moses Correct answer

    9 years ago

    I've used "resident expert" for this very purpose, along with some responsibility language along the lines of "consulted with colleagues on an as-needed basis." To make this really sing, include an accomplishment line that points to results that came from the company having you in this role, e.g. "Avoided hundreds of bugs in the design phase by providing guidance to colleagues who were working on [...]".

    I'm actually going to add this phrase to my CV right now...

    "Avoided hundreds of bugs" invites a question asking how you came about that number - be prepared to justify yourself.

    @JonStory, naturally, every factual claim in your resume should be something you can back up. Making up numbers just to have numbers is a bad idea.

    "hundreds of bugs" undoes the great image set by "resident expert" imho. I'm not saying it isn't true but it sounds like hyperbole, how about "Avoided considerable issues in the design phase..." or "considerable issue reports" if you want to keep to the concept of bugs or even "a considerable volume of bugs" if you don't mind the word bugs.

    @RyanfaeScotland If you know how many misunderstandings and incorrect assumptions you cleared up, you can directly correlate this to bugs. Bugs aren't always programming errors, if someone isn't implemented correctly that's also a bug. For a long-time "resident expert" I don't think hundreds of bugs is that wild of a number. In my experience, the amount of bugs you can prevent simply by asking the right questions at the right time is staggering.

    @Cronax - Like I said in my comment almost 2 years ago "I'm not saying it isn't true but it SOUNDS LIKE hyperbole..." I'm commenting on the wording used in the phrasing, not the legitimacy of the numbers.

License under CC-BY-SA with attribution


Content dated before 7/24/2021 11:53 AM

Tags used