What are your dos and don'ts for an effective resumé?
For further actions, you may consider blocking this person and/or reporting abuse
What are your dos and don'ts for an effective resumé?
For further actions, you may consider blocking this person and/or reporting abuse
Christine Belzie -
francheese9289 -
rathod ketan -
Rishi karanam -
Latest comments (60)
The more experienced you are the less lines you should have don't have 5 pages for resumé for example nobody has the patience to read it all ;)
Congratulations to those who benefited from out platform this week
Never depend on a single income
I can still help more 30 people earn $8000 in 7days,but you will pay me 20% when you recieve it
No scam
Ask me how?
WhatsApp +1 (782) 800‑6361
DO's
DONT's
For more information you can also visit:
boardinfinity.com/blog/15-quick-ch...
Always include your contact information clearly at the top of your resume/CV to make it possible for people to contact you!
At the company I currently work for applications get sent in to our recruitment software from various sources (i.e. recruitment websites) and while the resume document uploaded as part of the submission is sent to us, I have found that some of these sites do not seem send us contact information for candidates in addition to the resume.
Last year I was not able to contact several interesting candidates for Dev roles we had open because their resume did not contain contact details.
You need to consider what will happen if the resume is printed or downloaded and saved elsewhere and candidates screened that way; if your name and contact details are not included on your resume how can you expect to be contacted for interview?
I now put my Linktree at the top of my resume I believe that is one of the BEST things you can do. Because the recruiter or hiring manager will have full access to all of your profiles. GitHub, portfolio, social media, blogs etc...
It's makes for a good first impression.
John Comeau has an excellent free downloadable book on the subject. A genuinely insightful read.
joshwcomeau.com/effective-portfolio/
That my online portfolio below, you Guys can follow me on Twitter via, "Dav101xf",
davecwebhub.netlify.app/
Looking to collaborate with some one.
Do 90 interviews.
I have spent considerable time reading resumes on the interview panel, doing resume reviews and talking to recruiters and here are some things that will help folks stand out.
Some pre-conditions
You can now leverage this information to improve your resume.
Some steps that will help you stand out.
1. Sections:
If you have any experience, add it before any other section on the resume. Make sure the top half of the resume is crisp and gives the right set of information to the reader.
2. Target:
Hiring managers and the team spend a lot of time crafting Job Descriptions. Take a look at it and see if your resume is missing some relevant skills and add a point around it in your resume if it applies.
If you are applying to an Android role, have mostly Android related projects and experience points. Some resumes tend to have a lot of different technologies and projects that does not align with the role.
3. Experience Points:
Experience Section is a great place to talk about what you did and how it impacted the business you worked at. Use numbers and other quantifiers to drive a solid point related to your previous work. This will help catch the recruiter's attention and show how impactful you have been. Read the wiki on STAR format.
4. A/B Test
Some of these tips will help you, but it is always better to test if your resume is working for you. If it does, double down on it or else modify and try.
These are some tips that I followed in the middle of the pandemic to get a bunch of offers from big tech companies and startups and I hope it helps someone here.
Based on my job search journey and challenges I ended up building an app resumepuppy.com with my classmates to help others land interviews. If anybody checks it out, happy to hear feedback.
All the best!
"Recruiters spend only a few seconds on each resume to see if you are a fit."
I've never understood this attitude, and I never will. You want to hire good people, you have to invest some time to understand what people have done and in a few seconds this cannot be done.
However I do agree, the resume needs to capture the attention of the reader within the first few paragraphs of whatever structure that has been applied.
I agree with you on this! If you want to hire great people you need to be able to put in the extra effort to get signals from the resume.
From what I understand, this issue is usually for internships, new-grad and other entry-level jobs. These job postings get 1000s of resumes and the recruiters need to sift through them pretty quickly.
I do see that there are tech solutions trying to help recruiters here and I hope it gets better over time so that deserving candidates get interview calls.
Dos:
Don't:
When hiring I found there's talkers and doers, and the rare people who are both. I want to sift out the talkers, and hire the doers. Talking about code or elaborate setups don't ship products. I've wasted a lot of time on people who talk a lot but code very little. And I've seen unbelievable productivity from people who didn't say very much.
The interesting thing about skill bars is the disparity between having to show proficiency in relevant technology, while also gauging said proficiency. It comes with the natural problem of quantifying things: how do you know what you don't know, and what is the reference the recruiter is using?
I found that focusing on relative skill is helpful: if you're vastly more proficient in, say, React than in Vue, or Laravel than Symfony, make that visible. Word clouds help, though they're horrible for machine reading. Even something as simple as "+" vs "+++" can illustrate that. (Though I'd recommend avoiding 3 or 5 as your max, as that again implies a 100% value. Also, naturally, don't show a reference chart or legend).
If you list your github, I will probably poke through it. If its good I might get excited, if its not, i am not going to really hold that against you as its likely all side projects you are not getting paid for.
If I find dangerous stuff in there like leaked passwords, tokens, or keys in plain sight, I am going to recommend not calling back for an interview. I want people on my team that I can trust above all else.
Most of the time When I poke through someone's gh profile, it was all one commit repos, from a few days ago, and half the code is commented out. I'm not really going to get excited either way for this.
Get some reccomendations as close to the person as who is hiring you as you can. I've really made some great impressions with this in the past.
Don't make it too long, list the roles you have had, what made you great at them, and the value you brought.
Give an actual message to the person trying to hire you. Tell them why you want to be there, and why you are a great person for the role. Let them know you did your research for the position, and what value you can bring to them. It's more about selling yourself to this person than just selling yourself.
I'm a hiring manager, so I have a slightly different angle on this.
I think most of my advice is centered around "don't make me think". You want your resume to be so easy to read and parse that an HR system or a person can easily skim and find what they need.
List your technology, products, operating systems, frameworks, programming languages, etc. clearly. This should evolve overtime since you may write C in a university program and then never again, just like you may eventually decide you want to specialize in a particular JS framework.
Similarly, for projects and experience you may want to bold the items above if written in sentences.
Also for projects or experience, write exactly what you did on the team, not what the team did as a whole. It's more impactful if you write "led release automation" than "executed the full project lifecycle" or something cumulative. In the interview you can tell me a quick summary of what the whole team did if it necessary.
Avoid multiple columns. Software readers can completely miss anything not in the left column.
Use keywords wherever you can fit them in. Tools, languages, deployment environments, use keywords that are popular in the job listings that you are seeing for your desired new positions.
Front load the things that make you look better. If you have a degree then put it near the top half, and explain what things you did in completion of that degree that make you a good developer. If you are light on experience, but have lots of projects then you should have a projects section. This is especially beneficial as it allows you to fit in lots of keywords.
When describing a job/position you write the bullet points as achievements. These achievements should explain the goal achieved and the means of accomplishing it.
If you use a summary/objective then it should be specific to you and not things that EVERY developer could say about themselves.
Watch this video:
Some comments may only be visible to logged-in visitors. Sign in to view all comments.