I'm a software developer. There are a few tools that I know how to use, but can't really configure.

Example: I use Jenkins. I can set up what I need to setup for my project - I know my way around the user interface. But I couldn't set up an entire Jenkins server from scratch to get it to the point where someone could use the user interface.

So could I still put that I can use the tool on my resume? If so, would I put some type of disclaimer?

  • Configuring something is just following their instructions. You could just do it jenkins.io/doc/book/installing/#docker. Usually takes me ~1-2hrs. – ignorance Dec 18 '19 at 18:44
  • 5
    Does the job you're applying for require you to be able to setup a Jenkins server from scratch? – BSMP Dec 19 '19 at 15:27

Yes, put it in. Don't put a disclaimer.

Just don't lie in your job description. People can tell the difference between "Used Jenkins to do regression testing" vs. "Installed Jenkins from scratch to set up a CI environment."

  • 1
    I had the same issue with operating systems. I added in brackets "user-level experience", I think that's a good balance between disclaiming everything and being thorough. – Bennet Dec 18 '19 at 14:57
  • 6
    @Bennet So you know how to use an operating system, but you don't know how to set one up from scratch? It seems pretty clear to me which one you mean if you write "Experience with windows 10". – R. Schmitz Dec 18 '19 at 15:38
  • 7
    I just write: IT skills: Python (advanced), C++ (intermediate), ..., Windows, Linux, Mac (user-level) . I think it fits together nicely, actually, but it's just my $0.02 – Bennet Dec 18 '19 at 17:22
  • 4
    @R.Schmitz that might depend on the context: programmer job, yeah, my first assumption would be 'usage', while my first assumption on a techops position would be 'administration', but for a devops position it would not be so clear. Or if the CV has some stints in different areas. The less you fit a normative type, where context gives a clear indication (and that indication is correct for yourself), the more explicit you typically need to be. – Frank Hopkins Dec 18 '19 at 19:17
  • "People can tell the difference between" And if they can't, that's maybe all better for you, or some warning flag, depending on what you wanna do. – Pac0 Dec 19 '19 at 17:00

Short answer: Put the technology/tool in the resume, and keep its discussion to the interview.

  • 1
    Exactly. when in doubt, they'll ask. That's the moment to tell what actual experience you got with it (not disclaimer style, keep talking from the perspective of the tasks completed). – Mast Dec 20 '19 at 15:46

Yes. Put it in without a disclaimer.

You’re applying for a software developer position so in most cases, there wouldn’t be any expectation that you know Jenkins from an administration perspective as that is more suited for roles like build/release engineers, devops engineers, etc.

All those roles are sometimes done by a single person in smaller operations so it’s something that you can clear up in the interview if not clear on the job posting.

For your specific case, putting in “Software Developer” plus Jenkins will also communicate the following:

  • you are familiar with automated builds
  • you are familiar with source control
  • high likelihood that you’re familiar with automated tests
  • you’re familiar with what happens next when builds break from a Software developer standpoint
  • 3
    It certainly helps to have end-to-end knowledge of how the technology stack works, but if it’s not part of the job description, there’s no need to advertise the fact that you don’t know it. – AffableAmbler Dec 18 '19 at 16:35

Resumes need to get through HR's bots and keyword searches to matter. Throw it on there.


I split the technical experience part of my resume into 3 sections

  • Proficient in
  • Familiar with
  • Tools and Technologies

That way (if someone actually reads it) the reader can at a glance get a feel for how much experience I have with anything listed.

For your case, I'd put Jenkins in the "Familiar with" category.

  • 1
    But what if I'm proficient in using something but only "familiar with" setting it up? For example, I can use it really well, but can't setup a really nice environment for it? – undefined Dec 19 '19 at 9:25
  • 1
    @undefined, In that case, I would list both use-cases under their corresponding headings. – Arnold Wiersma Dec 19 '19 at 12:04
  • @ArnoldWiersma thus generating a lot of duplicate entries, or needing to specify which aspect of the tool you're familiar or proficient with. I'd rather keep it brief and explain during the interview if needed. – undefined Dec 20 '19 at 8:32
  • @undefined I would avoid duplicate entries; this might look like a mistake. Instead, explicitly list what you are referring to. If you list a tool by name I would expect you to be a user of that tool only not an administrator. – Arnold Wiersma Dec 20 '19 at 10:13

You must log in to answer this question.

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