Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
F197391915dFirstly yes, feel free to rant about anything.
Now bunch of things on your résumé. Let's get to refining it.
1. Remove the summary. It serves no purpose and hogs space. Add one or two sentences, if you must.
2. Make sure your resume is ATS friendly. Keywords, keywords, and then some more keywords.
3. Not a fan of side bar. However, if you are using such kind of template make sure the content is evenly distributed.
4. Categorise your skills. Devs are unable to sell themselves well. Add key skills, soft skills, hard, and technical skills.
5. I am sure those links are clickable (because it didn't work on my phone). If not then make them clickable.
6. Now the most important of all that'll get your foot in the door:
6.a The sole purpose your résumé serves is to land you interviews. Nothing beyond that.
6.b Use X-Y-Z format. Yeah we get it that you did bunch of things. Tell me what impact did you achieve.
Achieved/Impacted X with measure of Y by doing Z.
All the best.
gibus3305d-blurb thing should go in a cover letter.
-Timeline, how long were you working?. When did you graduate.
-I'd remove the stack overflow link as you're not above and beyond most people.
Agree with all of @F1973 points, in addition:
- People care way more about your education than a few GitHub projects, especially this early in your career. Talk about what kind of degree you have, what modules you took, etc. and do that in place of your GitHub projects if necessary.
- Don't bother linking to a Stackoverflow account unless you've got a lot of great Q&A. I'd say anything less than 5 figures isn't worth putting on there as a rough guide.
- Never talk crap about a past job on a CV or in an interview. Save that for here. Always talk positives. Otherwise you come across as a potentially difficult employee, and noone wants to work with someone difficult.
I don't like ranting: You'd expect from your employees the same. If not, consider as a matter of professionalism.
Personally, I'd avoid using terms like "legacy" - not because of speaking negatively about your job, but you also speak negatively about you; it might even be interpreted that you only have experience in old technology. I'd suggest to avoid being seen as always complaining.
The resumé seems overloaded:: I don't know where to look first.
If you look at a word processor empty page, it has restrictions on both sites, where you should not place content: Not only because it allows printing the document (some companies still do), but to avoid the reader being distracted.
Regarding your skills: Give some indicator about your experience (but no fantasy indicators like "93% of Python!). Especially for natural languages it, is easy ("fluent in reading and writing", "mother tongue", "C1"...).
C0D4616565dFirstly, this is why I hate the 1 page resume format, way to much information, and no where to put it.
As everyone else has said, give details, not just headings.
And I think the most important thing I look for is time in previous companies.
The timeline sets expectations and reassurance of your abilities - or lack of.
Layout-wise you have a truckload of whitespace in the middle, while your content is crammed up the sides, top and bottom, might want to consider redistribution of it.
Also don't speak poorly of ANYTHING in your cover letter. Is that really the most important thing you want to say? "My past job was shit" well then why did you have it? Speak of your accomplishments instead, you're not trying to scare them away from your former employer, talk about YOU!
ElPapi422425dYou all guys have lot of reason, i will fix this resume, i will take all the recommendations you mentioned here, thanks for your help!
I sent a connection on Linkedin, maybe we can chat a little about how to fix your resume
Looks perfect. Good luck with your job search.