-
Notifications
You must be signed in to change notification settings - Fork 275
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
Comments
+1 |
I would say it's too tech-specific, as you already suggested. Why not just include the tools in your |
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. |
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
Otherwise we will get quite a bit of duplicate between work skills and the main skills object |
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 ;) edit: @thomasdavis seems to be a lot quicker than me this morning ;) |
There doesn't seem to be much support for this currently. I propose we add the revisit tag and close for now. |
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." |
@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. |
@olivif Yes! I agree to close it for now. |
I'm with the reasoning here. Tell the story via projects and work sections instead of having tools as a non usable keyword list. |
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
The text was updated successfully, but these errors were encountered: