🔴 Originally published on FullStack.Cafe - Kill Your Tech & Coding Interview
Hey guys. Today I want to grab your attention and talk about ...
For further actions, you may consider blocking this person and/or reporting abuse
I completely disagree with this entire post. You can't exibit technical ability by hiding behind resume fluff. Any decent dev manager will see this a mile away and may actually hurt your chances more than help.
While there may be different opinions regarding the usefulness of the author's tips and they will probably be more effective in certain cultures and contexts than others, I think he was rather honest in stating that the point of a CV is to get you an interview, not the job. Of course you still need to prove your skills in the interview process.
Where I live, most of the time somebody in HR is filtering the CVs and making first contact, and the dev manager only sees the CV once a first interview is scheduled. Thus, the goal of the CV is to peek the recruiter's interest, not the dev manager's.
It can be useful for developers trying to get a foothold in industry. Entry-level coding jobs have bad HR screening where the HR blindly checks resumes for certain keywords and bins the non-conforming ones. The result is an arms race of adding more and more keywords to resumes.
Once you have your first job, the situation is different. In such a situation, more keywords attract spammy recruiters/bots.
I agree with your point of being careful before sending such a resume. Best advice will be to read the job description carefully. If it is buzzword heavy, keep a buzzword heavy resume ready to send.
Good advice.
As others have alluded, applying for jobs fresh out of university and mid-career are very different beasts. Early on you're going to rely heavily on school projects, part-time jobs, trivial personal projects, etc.
Addressing two different audiences (HR and then technical staff) is a must. Many HR staff don't have a technical background and are looking for keywords from a list they were given with the JD.
Be concise. Every couple of months I see a resume that reads like Beowulf. A paragraph of flowing prose to say they "fixed bugs".
Be memorable. 90% of resumes for a position are similar (not a real statistic). Anecdotes:
Don't lie. If you get caught in a lie it's game over. The rest of your application doesn't even matter.
Useful! Thanks <3
I've only worked in one internship so far, so do you think it would be OK to include work I've done for my school's computer club? (I made a couple of interesting projects for the club that got me hired for the internship in the first place). If yes, how do you think I should put them in? Should I put them in like regular work experience?
The ONLY time you include personal details is when the job calls for skills that you've done in your hobby that you havent been able to practice in a paid gig - this is usually softer skills, for example, maybe you havent done any management at work, but the job you want requires it, so you include your time in scouts where you led a team, or such.
That said - you're effectively talking about a side gig. Side gigs demonstrate you are really passionate about your career (with the minor quibble of don't make them worry you'll never be in the office because you are working on it instead... :)) and can be really useful to demonstrate a skill the job requires that you are still building.
If its relevant to the ad - go for it :)
Even if you decorate your CV like that you still have to pass the technical interview and check if you like the company you apply for. There is no magic bullet.
I see how you got the title of this post :D
Hey! I've noticed that in this post you use "guys" as a reference to the entire community, which is not made up of only guys but a variety of community members.
I'm running an experiment and hope you'll participate. Would you consider changing "guys" to a more inclusive term? If you're open to that, please let me know when you've changed it and I'll delete this comment.
For more information and some alternate suggestions, see dev.to/seankilleen/a-quick-experim....
Thanks for considering!
What would you say is the rate of people picking proud or ashamed? I immediately thought of a few places I've been meaning to refactor that I'd love to talk out why they suck and how I'd do it better (assuming I ever got the time to do so)
Constructive post. I like the point:
Stop DOing, start ACHIVEing. I should change my Resume according to this tip.Thanks.
Regarding point 2, I've always believed skill clouds to be worthless. Could you elaborate on how different was the response between having it and not having it, and why you think it works?
I even find the name horrendous
If I was looking at a CV with a big list of keywords my eyes would roll heavily.
It gives me no indication of how proficient you are with them or what you've actually done with them.
Not only that but specific experience in technologies, whilst interesting; are not the most important thing to me. If a person is clever, they'll be able to learn it on the job anyway
Yeah I don't want 90% response rate. I just want the 10% best companies.
is misspelled. Just FYI, not trying to be negative. :)
It's awesome!!.Thanks for sharing your experience.