![]() When I worked my first job, I happened to end up at lunch sitting next to a person that worked in HR and we talked about the process. My philosophy is to make it as easy as possible to find what they need, not to bury it in narrative. If they don’t find them in 3 seconds, they just move onto the next one. They have a checklist of keywords from the engineering team and they are quickly scanning your resume for those keywords. Additionally, at that level, they are often looking at hundreds of resumes, sometimes thousands. They will often be a recruiter or an HR person that will not be able to infer things. Putting them in your projects section can get repetitive - if you try to list them exhaustively.īut another problem is that, especially for entry level positions, the first person to read the resume, the gate-keeper, may be non-technical. I know there is some disagreement about this, but I fall down on the side that a skills section is important. “Learning new technologies, Touch typing, Working on cognitive abilities” aren’t legitimate interests either and are best just deleted. Don’t fill the resume with lines that are obvious knowledge to anyone who’d be technical. These are adding nothing to the resume, so you might as well delete anything else that’s obvious like them. And second, for anyone who does actually know what Passport.js and Bcrypt are, you’re actually just re-stating the obvious on these (technical folks will already know that Passport is an authentication library, and Bcrypt is a password library). First of all, you have to make your project descriptions high-level because most of the time it’s HR personnel or recruiters who are reading your resume, not other developers. A bunch of bulleted list items on detailed technical info doesn’t do anything useful, especially when you’re just saying things like “Implemented user authentication using PassportJs” or “Encryption of user passwords using Bcrypt module”. If you’re going to have a projects section, it should be much shorter with only high-level descriptions (and links to deployed versions). I’d personally suggest Skills first, then Projects, then Education, then Languages. Either your skills or projects should be first. Your order of sections matters, and isn’t what it should be. Then some other points which aren’t “critical” but noticeable: You can’t contradict yourself here, if you don’t have work experience then you can’t say you have experience. You wrote “A fullstack developer having 1.5 years of development experience” but there’s no actual experience shown on the resume. That’s personally identifiable information that you shoud delete. No one needs to know your date of birth, or should know that. There are a couple things here which I’d call critical mistakes:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |