Help needed for my resume

I have been applying to multiple companies for a developer role but didn’t have any luck in getting an interview, let alone secure one.
I’d appreciate if you could take some time to go through my resume and tell me what I’m doing wrong, which lead me into this hopeless situation.
Here’s a link to my resume.
Appreciate your effort.

You would need to create a public link to your resumé to allow anyone to view it.

How can i do that @igorgetmeabrain?

Thanks. I managed to make it public.

Right click on the file on Google Drive which you want to share and select ‘Share’. Then click to change ‘Restricted’ to ‘Anyone with the link’. Then share the link with whoever you need to.

Appreciate for taking the time and effort to help me out. :slightly_smiling_face:

No worries. I have no expertise to tell you how good your resumé is in terms of securing employment, as I’m only learning to code and I’m not a professional (yet).

However, I noticed one typo in one of your headers:
Markdown Previwer…

Also, I guess you might want to include links on your resumé to your portfolio, GitHub and other accounts?

Thanks, for the feedback.
In the previous version of my resume I had links to my projects and accounts. And that was the application I sent out to most of the companies, but I changed it a bit cause the previous version was too plain. Anyways, I’m gonna keep in mind to include what I’m missing in the new one and fix the typo as well.

With so little experience, you should try to make your resume a one page document. Trying to making it two pages highlights your lack of experience.

You should have a summary for each project explaining the purpose and highlight the main skills used. Keep the summary short and to the point and add more projects. Also, make sure to add a link to the live versions of all the projects as well as links to the code (i.e. GitHub repos). Instead of listing your portfolio app as a project, have a link to the portfolio on your resume.

Get rid of the key skills section because your projects should highlight them. Get rid of the Interests section because employer only cares if you can code. Interests could be something you discuss if asked in an interview.


Thanks @RandellDawson .
Will make the necessary improvements.
And is providing skills section seen as a red flag?

It is just not necessary. If you write each project summary correctly, then you will have the skills covered there.

bro are u bengali? if its not a problem can u help me i saw in ur resume ur from commerce line and switching. Just wanna ask some question

1 Like

Yes, I’m.
And I’m ready to lend a helping hand for anything that’s within my scope.

its just i learnt html and css but when it comes javascript i am failing horribly. i just cant to seem to get the logic behind it like i can understand what the answer is given but if u ask me a question on logic i cant answer. do u have any suggestion where i can practice or where did u get to learn javascript

To understand javascript better I had to go to Codecademy, that’s where I understood some of the things I was having difficulty with. And then I came back to FCC and finished the JS curriculum. And I think javascript makes more sense when we know why it exists in the first place, from there things start getting more interesting.
Coming to the logic part of it - basic understanding of fundamentals should you help you with that.

To summarize,

  1. understand the programming fundamentals (how a programming language works).

  2. understand and know where the language you’re learning can be used.

and can u tell me any book or where did u get the basic fundamentals

Didn’t read any books for that. I just used FCC, read articles, checked documentation and more importantly, practiced.

1 Like

There are a couple things here which I’d call critical mistakes:

  • No one needs to know your date of birth, or should know that. That’s personally identifiable information that you shoud delete.

  • You wrote “A fullstack developer having 1.5 years of development experience” but there’s no actual experience shown on the resume. You can’t contradict yourself here, if you don’t have work experience then you can’t say you have experience.

Then some other points which aren’t “critical” but noticeable:

  • Your order of sections matters, and isn’t what it should be. Either your skills or projects should be first. I’d personally suggest Skills first, then Projects, then Education, then Languages. You don’t need an Interests section.

  • If you’re going to have a projects section, it should be much shorter with only high-level descriptions (and links to deployed versions). 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”. 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. 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). These are adding nothing to the resume, so you might as well delete anything else that’s obvious like them. Don’t fill the resume with lines that are obvious knowledge to anyone who’d be technical.

“Learning new technologies, Touch typing, Working on cognitive abilities” aren’t legitimate interests either and are best just deleted.

I know there is some disagreement about this, but I fall down on the side that a skills section is important. Putting them in your projects section can get repetitive - if you try to list them exhaustively.

But another problem is that, especially for entry level positions, the first person to read the resume, the gate-keeper, may be non-technical. They will often be a recruiter or an HR person that will not be able to infer things. Additionally, at that level, they are often looking at hundreds of resumes, sometimes thousands. They have a checklist of keywords from the engineering team and they are quickly scanning your resume for those keywords. If they don’t find them in 3 seconds, they just move onto the next one. My philosophy is to make it as easy as possible to find what they need, not to bury it in narrative.

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. I’m sure there are different places that operated differently, but I suspect there is a lot more of this than people care to admit. Heck, many of my first interviews were with people that had no idea what I was talking about - they were just asking about keywords and noting if I seemed to know what I was talking about.

I think as you get more advanced, it becomes less important, since your experience speaks much more loudly, and resumes probably get read more closely. At that level, it may even seem silly to have a skills list. But for a beginner, skills are often a strange hodge-podge and may even include skills that aren’t in one of the three projects you decided to list. The other advantage is that it fills out the page. True, it forces you to tighten up the other sections to make it fit, but that often improves the resume since many entry level resumes pad the other sections way, way too much, obscuring the information people want.

→ First improve your resume, i prefer use canva, you can make something like this for free

→ secondly i agree with @astv99, mention your working experience, where you worked from when to when and on what key technologies you worked with,
→ also keep projects description short,
→ when mentioning you technical skills maybe put a star in front of you best skills