3 ms·

thanks. Front end skills are obviously not my highlight as can be seen from the content of the resume, but I wanted to demonstrate that I have at least good cod

by gr3yh47 12y ago

thanks. Front end skills are obviously not my highlight as can be seen from the content of the resume, but I wanted to demonstrate that I have at least good coding style/organization and have some front end chops to complement my other skills. What of the general content of my resume?

adrianpike 12y ago
At the same time showing off your chops can be a liability this early in the game. In the interest of full transparency, the first typo colored the rest of the read for me - I also noticed and got a bad taste from the inconsistent spacing and indenting in your code.
aesthetics1 12y ago
The content honestly isn't great. It looks like you have some experience, but you haven't told a potential employer about any of your projects or accomplishments. Your bullet points read like job descriptions, and anyone else who submits a resume that has had a job remotely similar to yours will sound about the same. Focus on your projects and accomplishments while employed, and make it look less like a job post. I know you aren't emphasizing the front end skills, but leaving them out in the open if you aren't great, and aren't up to date with your front-end skills (tables, adding classes to make paragraphs look like headings - just use headings) can make any semi-critical resume reviewer cry "eek!.." Showcase what you are best at, and don't try to justify your hiring with things you "kind of, sort of" know how to do. As others have said, tailor your bullet points to the job you are applying for. I don't care about your systems engineer work if you're applying to be a junior dev. Talk about your internal tools and app development. Those should be your bullet points - not that you "started and completed projects" or "were a member of a team". Focus on your strengths and your goals!
- gr3yh47 12y ago
  >but you haven't told a potential employer about any of your projects or accomplishments. did you not read the whole resume? tons of coding projects i've done are listed.

by gr3yh47 12y ago

adrianpike 12y ago

At the same time showing off your chops can be a liability this early in the game. In the interest of full transparency, the first typo colored the rest of the read for me - I also noticed and got a bad taste from the inconsistent spacing and indenting in your code.

aesthetics1 12y ago

The content honestly isn't great. It looks like you have some experience, but you haven't told a potential employer about any of your projects or accomplishments. Your bullet points read like job descriptions, and anyone else who submits a resume that has had a job remotely similar to yours will sound about the same. Focus on your projects and accomplishments while employed, and make it look less like a job post. I know you aren't emphasizing the front end skills, but leaving them out in the open if you aren't great, and aren't up to date with your front-end skills (tables, adding classes to make paragraphs look like headings - just use headings) can make any semi-critical resume reviewer cry "eek!.." Showcase what you are best at, and don't try to justify your hiring with things you "kind of, sort of" know how to do. As others have said, tailor your bullet points to the job you are applying for. I don't care about your systems engineer work if you're applying to be a junior dev. Talk about your internal tools and app development. Those should be your bullet points - not that you "started and completed projects" or "were a member of a team". Focus on your strengths and your goals!

gr3yh47 12y ago
>but you haven't told a potential employer about any of your projects or accomplishments. did you not read the whole resume? tons of coding projects i've done are listed.