Ask HN: What is wrong with my resume and portfoilo?
This is my resume https://drive.google.com/file/d/0B8b4MJypbW9Yc1FFYjM3aUZ1ZzA/view?usp=sharing , I would like to know what is wrong with it? I been applying to lots of jobs, and haven't got any offers yet. Earlier I applied to full stack developer, now I am just applying to junior web developer. This is the website I build for my portfolio: opusworkspace.herokuapp.com.
This is my GitHub page: https://github.com/Sujinthan
11 comments
[ 8.2 ms ] story [ 44.2 ms ] threadThe book stacking and library work don't seem to sell your programming abilities.
Your english (here) isn't perfect. That's not a huge problem, if you are smart, but it is something people pick up on quickly.
As another data point, I would disregard your application immediately upon being asked to 'Sing In' and 'Sing Up', which is clearly a rookie typo/shows a lack of attention to detail.
https://i.imgur.com/Pwwmsda.png
Regardless of what anyone says, keep going at it and get better every day.
I think he is applying as a developer, not as an English teacher.
ps. I've read a lot of comments like this one, in various threads here and on reddit. I really wonder if the people who make those remarks are equally austere with themselves.
As for your PS, yes.
Keep your resume one page. Don't add stuff that's not related to tech.
I think putting projects that are in progress/incomplete are fine as long as you have dug into it enough to talk about some technical/issues you've faced.
I can help you construct at least a decent resume...
I know a lot of people say it should be plain but you can still make it look nicer while staying simple. Maybe a bit of colour or a better font.
You also have some weird lines in your work experience section.
Check out Represent.io, you don't have to use their templates but they are a nice reference point.
Also, there are probably more good posts on resume writing here: https://hn.algolia.com/?query=resume&sort=byPopularity&prefi...
Condense Current/Previous projects into 'experience'. Leave out all non-technical jobs (including your volunteer experience).
Your resume's primary job is to show if your technical skills line up with what they are looking for. It's up to you to pass their tests/interviews, NOT your resume. Don't give them a reason to exclude you. Just have your current skills, contact info and experience. Maybe an objective or technical interests.
Imagine a site with one button. The recruiter clicks on that button and gets a random fact about you. They'll click the button 6-10 times and then make a "pass" or "continue" decision.
What would you populate your site with? This is basically what your resume should look like.
Every bullet should stand alone and have high impact. When I click on the button, I should get a sentence that makes me say, "Wow, I want to talk to this person."
Compare the impact:
"Online IDE to allow users to develop applications in real time."
"Solo created a cloud based IDE which supports multiple programming languages and allows real time application development."
Be ruthless about cutting out things which fail the "button test" and your resume will look a lot better.