> if you consider common skills like Jupyter notebook and git your competitive advantage (the only reason to include them in your resume), I would automatically assume that you have no other competitive advantage
I get this, yet, at the same time, I've been asked by recruiters if I was comfortable working with "git flow with Gitlab and Jira" since I did not name any of those in my Resume.
I wonder if I've ever been filtered at first instance for small annoyances like this, it's hard to build a good resume when everyone is looking for something different so I would appreciate if things like adding keywords would not count as a deterrent.
Now I thinking how I can put that I've been the unofficial git guru in several jobs in the resume without sounding like I'm just playing the keyword game.
Maybe under "Skills" I'll add something like "git is my bitch and I eat merges and shit rebases". Or is it too formal? XD
> I've been asked by recruiters if I was comfortable working with “...Jira"
Great question - I might start asking this, and shitcanning anyone who claims to be both experienced and comfortable with the idea of working with Jira.
You can optimize for this one guy who has something of an axe to grind, or you can optimize for the 99.99% of employers who look at education, relevant skills and employment history. It's almost definitely worth ignoring everything in this post.
I get this, yet, at the same time, I've been asked by recruiters if I was comfortable working with "git flow with Gitlab and Jira" since I did not name any of those in my Resume.
I wonder if I've ever been filtered at first instance for small annoyances like this, it's hard to build a good resume when everyone is looking for something different so I would appreciate if things like adding keywords would not count as a deterrent.