Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a toolsUsed under work properties #37

Closed
lostphilosopher opened this issue Jul 7, 2014 · 10 comments
Closed

Add a toolsUsed under work properties #37

lostphilosopher opened this issue Jul 7, 2014 · 10 comments

Comments

@lostphilosopher
Copy link

This may be too "tech specific" for a general standard, but any resume I've written (and most I've reviewed) have included a section for listing out the tools / technologies used in a previous position.

This is helpful for passing resume filters, and gives the reviewer an at glance "have they used X random tool professionally" without eating up valuable page space.

Example:

Tools Used: GitHub, Zend Framework 2, Stripe, Bootstrap 3, PHPUnit

@vote539
Copy link

vote539 commented Jul 8, 2014

+1

@ocram
Copy link
Contributor

ocram commented Jul 9, 2014

I would say it's too tech-specific, as you already suggested. Why not just include the tools in your "skills" section? That's what it is: skills.

@osg
Copy link

osg commented Jul 10, 2014

Arguably, writing is a skill. I use tools, such as, DocBook, HTML, Markdown, nanoc, GitHub, and more to write documentation.

In the same light, vim is not a skill, it's a tool.

@thomasdavis
Copy link
Member

I think if you want to showcase which skills you used for different employers you could just mention them in your work summary and highlights e.g

  • Used Node.js and Bootstrap to build a modern web app

Otherwise we will get quite a bit of duplicate between work skills and the main skills object

@DonDebonair
Copy link
Member

As someone who's done a lot of job interviews from the interviewer side, I wonder if the tools someone uses are ever seriously looked at. When I'm interviewing someone for a Java position, I don't care if they used Java EE 7 or Spring, as long as they understand the principles behind Dependency Injection ;)
I don't want to dismiss the tools someone knows entirely, but I think those can easily be mentioned in the descriptions of the relevant work-entries.

edit: @thomasdavis seems to be a lot quicker than me this morning ;)

@olivif
Copy link
Collaborator

olivif commented Feb 18, 2016

There doesn't seem to be much support for this currently. I propose we add the revisit tag and close for now.

@aloisdg
Copy link
Contributor

aloisdg commented Feb 18, 2016

I am against for the original reason. It is a bit too "tech specific". By the way, I used python 4 years ago. I dont think It is relevant to write it. Tools will rise in the project section: "I made a tools to create themes with nodejs, nunjucks, ava and babel. I also used some bash scripts to build it."

@olivif
Copy link
Collaborator

olivif commented Feb 18, 2016

@aloisdg I agree, it seems very tech specific. I am not saying I don't want people to have it in their resumes if they want to, but I don't think we need a special field for it. As @thomasdavis mentions, this can easily be done in the work description section. Or the future projects section.

@aloisdg
Copy link
Contributor

aloisdg commented Feb 18, 2016

@olivif Yes! I agree to close it for now.

@stp-ip
Copy link
Member

stp-ip commented Feb 18, 2016

I'm with the reasoning here. Tell the story via projects and work sections instead of having tools as a non usable keyword list.

@stp-ip stp-ip closed this as completed Feb 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants