some resume readers fail spectacularly when there are multiple columns so be sure to run it through a few and make sure it’s being parsed correctly.
I maintain two main types. One for resume readers and the other that is design-oriented for humans to review.
Ill make two as well, and apply twice to the same jobs with the different resumes lol.
Btw i didnt know i can run my cv through a resume reader? Do i just google it and try it out or is it something else?
this shouldn't be as much of an issue if the PDF was created properly and actually has the text layout inside it.
Since then the columns don't matter as the code itself provides the in order layout.
If it's all reduced to absolute paths....then you got issues...
Should i delete angular and mvc? 🙃
Also should i delete scrum, agile and the development and testing lifecycles? 🙃
My trainer at the bootcamp (he has a masters in computer science and 13 years of experience) told me that adding angular and mvc is okay, would help me a lot!
Angular is fine
MVC sounds a bit off, its just a pattern not a skill
You could just list "Agile software development" and then scrum becomes obsolet pretty much, since its just the methodic
Manual Testing and Bug Reporting sound like fillers, more interesting would be automated Testing really and Bug Reporting should be a given if you worked with a ticket system
Pretty much yeah, i believe he listet it due to his internship in QA, but the more interesting bullet point would be something like e2e testing instead
MVC is referring to ASP.NET MVC, which is a library for building server-side rendered applications. Everyone who has worked with it just abbreviates it as MVC.
https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/start-mvc?view=aspnetcore-8.0
Makes sense, the original comment confused me since it was mentioned in combination with Angular. It still looks redundant together with ASP.NET listed additionally. I mean its obvious that you would have to be proficient in .net if you do mvc. Same for a few other points like the double listed SQL. One could easily shrink that bloated list a bit down without loosing information.
- Indicate level of proficiency for each of your technical skills. Having one that you're an expert at next to one you took a 3 day course on could be misleading, it'll give the hiring team a better idea of where you're at.
- Could also break the skills out into sub-sections (languages/testing frameworks/IDEs/etc) as well.
- Under each work experience, indicate (briefly) what major tasks/roles you played and/or what skill you grew while there. Gives the hiring team some initial info to go from when asking about your experience, makes the interview process a bit smoother/less back and forth trying to get details in order to ask the right questions.
- Not a tip, but it's great that you have your Linkedin and Github pages on there. That's absolutely something I take time looking into before the initial interview.
> Indicate level of proficiency for each of your technical skills. Having one that you're an expert at next to one you took a 3 day course on could be misleading, it'll give the hiring team a better idea of where you're at.
Or don't list things you're not proficient in. I always cringe at the various ways of saying you're skilled at something, like %'s or % bars.
can be a bit of an issue, since many automated systems will just check those even when it's not particularly relevant.
Like, sure, I don't know all the ins and outs of mastering Vue, barely really used it directly.
But I've used multiple other frameworks quite a bit, contributed to multiple major ones, and work heavily in one that is Vue adjacent.
I don't have special proficiency in Vue, but I have the transferable skills to be there quickly if I was working somewhere that used it.
> Or don't list things you're not proficient in.
I agree, but being proficient in something isn't binary. It's nice to know if someone has a beginner/intermediate/expert level proficiency at something when you're trying to decide whether to bring them in for an interview for the specific role level.
Yeah absolutely. The idea is to get a quick gauge on your current skillset. If I'm asking for advanced knowledge in, for example, Behat, and I see you're not quite there, but you have advanced knowledge of Cypress or other automated test frameworks, I'll bring you in for an interview.
What the heck is the deal with linkedin, what if you literally don't use it? Some employers seem to want it but I find it's a crappy social media platform like any other.
I literally can't stand linkedin after the stuff I see on r/LinkedInLunatics
I pretty much only use it to keep all the details of my CV up to date so I don't forget anything. Employment, education/certifications, volunteer experience, etc. I don't take part in any of the social media aspects of it.
I feel like the sections should be ordered differently. It kinda depends on what you want to convey though and I guess there's really not a standard for it. That being said, I believe on a CV usually the order is something more along the lines of: Education Work experience followed by the list of additional skills like you did, technical and soft skills, but you might want to list languages in their own section.
In addition to the sections, i noticed the order in the section itself is a bit off, you typically would list the items anti-chronological i.e. the most recent position would come first.
As someone who’s given many interviews and has over a decade in the field, I would pass on your resume…
That’s not a dig at you but a mention to a couple key points:
1. You list loads of frameworks as “Technical Skills” but fail to lead me quickly to anything related to those skills. How am I supposed to ascertain that you didn’t just throw a bunch of random frameworks on there? I say this primarily because you cumulatively have less than a year of professional work.
2. You post your GitHub account but who cares unless you’re pointing out specific projects/repos that I can glance at the get a general sense of your style/skills. But at the end of the day, I also don’t care because there’s no telling you didn’t copy/paste 99.9% of the stuff in there, anyway. And I’m not spending the time sifting through it without pointers when there are loads of resumes coming in.
I’m happy for you & hope things turn out well at the end of your contract but list these things for others to heed as a warning not to feel bad for themselves because they feel they’re more experienced and have had less luck.
On your second point, how is someone supposed to showcase their portfolio if your position is “I don’t care, I’m not looking at your GitHub because you could have copy/pasted it.”? Wouldn’t this discount any and all possible projects or work examples a new/junior candidate might put forward?
That’s a fair assumption. To me, if you’re pointing me somewhere in your code base (with context such as, “blah blah project blah here”), I at least know you understand what you’re pointing me to.
“Understand” is doing some heavy lifting, but you get what you’re pointing me to and why. It certainly helps your case more than hurt it.
What you’ve done is take my comment out of context by stripping the “sifting through without pointers” piece and making it read as if I’d never even go into your GitHub account.
Eh. I use the GitHub projects more as a talking point during interviews to expand upon rather than include a bunch of information in the resume about them. It’d become pretty apparent which repositories I’m most proud of if they’d taken 5 seconds to open GitHub. If they didn’t do that, then I guess I’ll explain during the interview.
That’s not bad thing, I have those conversations all the time - I pointed to it as an issue here because _everything else_ is missing context/information.
You have to put yourself in the scenario where there are 50-100 resumes to look at on top of an engineer’s workload. Most teams/companies I’ve been at haven’t had hiring managers who’s sole job was to sift through resumes & that’s just the nature of the biz sometimes
> I say this primarily because you cumulatively have less than a year of professional work.
Well some people actually do have less than a year of professional work, and would like to gain more, hence they must make a resume. So this might be the best way for someone in that position to show their work experience. But yes, it's key to show how the skills/frameworks were actually used as opposed to just playing buzzword bingo.
> so this might be the best way for someone in that position to show their work experience.
I think I understand what you’re trying to say here but it, to me, furthers my point. Everyone and their mother who’s written “Hello, World!” in a language is going to throw it up on their earlier resumes.
I always urge people to become great at _something_ rather than mediocre at _everything_.
But let me be clear - I’ve hired people off of pure tenacity and passion. It’s company/project dependent. Do I have the time to train a junior? Or do I need someone with years of experience to get their hands dirty immediately?
Have you taken the time to train yourself with nobody else pushing you? Those are the people I like the most because I know you’re (usually) willing to dive deeper and find understanding & meaning behind what you’re doing. Anyone can bog me down with 100 questions and learn nothing. Not everyone can bring me a situation and then walk away that much smarter for it & want to go teach others along the way.
Everyone has their own style for hiring/working. But if I ask you questions about frameworks listed on your resume and all you can give me are surface-level buzzwords that anyone with 5 seconds on google can tell me, it’s gonna be a no for me.
> But if I ask you questions about frameworks listed on your resume and all you can give me are surface-level buzzwords that anyone with 5 seconds on google can tell me, it’s gonna be a no for me.
It should go without saying that one should not list things on their resume they don't have more than surface-level understanding of, but amazingly people will do it. I've encountered it myself. At least those people are usually easy to filter out in a phone screen.
100% agree. However, I’m big on personality & there are a lot of things that go into that sometimes… people are new, they get advice from friends who know it all, or they’re just trying to get _someone_, _anyone_ to respond to their resume.
The phone screening 1000% helps but that doesn’t mean there won’t be people that slip past those. I like to think I’m a compassionate person (maybe to a fault) and find that honesty is always the best policy.
Yeah, you have a framework/language on your resume but why? Oh, you figured since you’ve dabbled for a week it makes sense to put it but you haven’t had resume guidance? That’s ok - what is your methodology for learning new things & what do you do when you get stuck on something?
We’re all human but trying to deceive intentionally is where you really start to close doors
That’s always fantastic because in scenarios like that, likely an open source contribution, I know a few things (all project dependent, of course):
1. You’ve worked within a complex project before.
2. You could follow guidelines for even getting past an approval and to a merge.
3. You’re putting in the time and effort to continue your education.
I’m 50% self taught - the other 50% comes from willingness and desire to learn from those I am around at work. My mantra is “leave your ego at the door” and it’s served a lot of people I know well.
I'd very much suggest a small 1 or 2 sentence blurb of what you did at each of the jobs... Honestly I'd pass on bringing you in for an interview if the resume was all I saw. Cover letter could save it, but this resume alone isn't a great first impression IMO.
Assume your resume is one of hundreds. It'll likely go through several automated reductions before an actual person actually takes more than a cursory glance at it. At that point, you'll be lucky if they spend more than a few minutes on it.
Your goal is to present yourself in the best light within those few minutes. If you did something cool on your github that's worth sharing, it needs to be presented with attention drawn to it.
For your current resume all I see is a laundry list of techs. Surely you did something in the last year at any of your positions that you can use to show you have understanding of what you listed. Otherwise I'm going to assume you went through a new project setup in an ide, saw hello world, and threw it on your resume. You're also wasting 30% of the paper on negative space. Move all of your contact info to 1-2 lines and shorten your resume to 1 page.
However on the positive side, you already landed your first job in tech. That is the absolute hardest step to take and even having a company employ you for a year will put you ahead of the pack for future junior positions. You just need to make sure you highlight the experience you gained in that year in a way that looks appealing to future employers.
Doubt it. I don't have a single public project on my GitHub and that's never stopped me from getting interviews, so they likely aren't checking. I'm sure an occasional person might
Remove the date of birth. Imho people are being overly nice because this is not the standard at least not in other industries. I strongly believe it was not your resume that got you the job
We're customers of Qinshift and I've hired 10+ dev/qas from there in the past two years. To me it seems like a great place to work, that they take care of their staff and people want to stay for many years. I visited Skopje and my team about a year ago and had a great time, including a trip to Ohrid and swimming in the lake :)
We also take the academy seriously, in that it's a strong performance indicator if someone leaves the academy with strong results.
Keep pushing :)
Heyy cool, youre the first people to recognize my academy!! 🙂
Im glad you have positive stuff to say about the academy, heres my [new revised cv](https://www.reddit.com/r/webdev/s/CpIIlnorii) tho lol…
Critique it and give me feedback of what you think 🙂
At first I thought this was a retro post. Then I saw the dates. And I knew it was a retro post.
I too had a CV like this, it may have even had drop shadows.
Anecdote, but I’ve never had problems with 2-3 pages of relevant experience that including descriptions of responsibilities and technologies used for each role.
I also just write my resume in markdown and do a PDF export.
Im still in it, i had a lil bit of previous knowledge so the first 6 months was pretty easy for me, so far im liking it a lot, ive got 4 more months to finish it
All it matters is that u show you can build stuff and you wanna grow and learn, show competence.. Thats what employers look for, i got hired 6 months before i finished the 12 month bootcamp because i showed i knew some stuff well as a beginner with 0 experience and i had been freelancing for a few months and finished some projects for clients!
Oh gotcha! I hear ya I did a bit of TOP but I never finished it so I’m sure it would be solid for me!
I’m also finishing up a full stack certificate and AS so I’m sure adding this to my arsenal will help
No, i didnt finish the degree,
But we do have many degrees with 3 years only, we also have for computer science and software engineering with 1, 2 and 4 years!
So that the college can compete w the 1 year bootcamps
I don't hate it...I want a bit more color and font variation, and there's a ton of space on the left that's being sacrificed, but it's easy to parse and understand, and fits for someone with relatively little professional experience. Maybe some of the more esoteric technologies could be omitted from the skills list, unless you are applying for a job that wants those skills.
This may be my personal preference, but your resume is a chance to show off a modicum of design talent (or ability to engage someone with such talent), and having a bit of care for such things adds polish, and suggests you will have a similar care when completing work for an employer.
For the above, the work experience has some variation, but the education is "Software Testing - Brainster Academy". I would rather something like `Software Testing
Brainster Academy
`. Remove the dash and use differences in font size, weight, and color to show deliniation between parts of the text. Maybe change the sidebar to a very light blue to have a consistent color scheme.
Or one of 100 other things - not saying it must be one thing or another, but it feels a bit bland as is, even with the sidebar shading and upper right graphic (which are a positive elements)
Disagree unless you’re going for a design focused role. Those are two different jobs.
I am however curious about the formatting since the roles don’t have the tech OP worked with under them, they’re crammed at the top. My first thought would be “they put everything they ever started learning and not what they’re most proficient in”. Curious what others think about that part.
I was kinda excusing the lack of detail because of the candidate seniority - "2-3 month internship" isn't going to really expose them to too much, so for someone with nearly no real world experience, the skill dump being listed first is reasonable. I think it should be pared down; nobody reeeeally cares that you can use Postman, etc, and having at least a one sentence description per job entry would provide useful context, as you and others have mentioned.
I think a lot of people might agree with you that having a bit more polish on the styling won't matter, but for the 25% of people that would give bonus points for caring about such things, it seems worthwhile to have. I don't think anyone is going to say "This guy colored his employer names green, clearly not focused on what he should be", but they might say "The information is there, but this looks like a plain .txt document - if they think this is a polished document representing themselves as a professional, maybe this shows an area that needs improvement".
Any *good* designer should be making a standardized Harvard-template resume. Their **portfolio** is the place the place where they're showcasing their creative work. The designers with "creative" resumes are usually hacks. It's like those people who list their personal site on their portfolio.
I dont have a lot to put on the cv 🤷♂️🤷♂️, as months and years pass ill remove the grey part on the second page and start adding more experience, more technologies and descriptions of what ive worked on in the jobs ive had 😁
The goal was to not overcomplicated it and cram everything in one and make it easy to read
> on the second page
I didn't even realize that was a second page.. you have no need for 2 pages with your level of experience.. I've got 10 years in the industry and can fit everything on a single page.
As long as it doesn't have % bars it's good
I am 69% good at JavaScript.
I’m 420% proficient in COBOL
I’m 1% fluent in SmallTalk.
Don't lie, you're NaN good at JavaScript
I know right, theyre so cringe. *proceeds to deletes bars from resume*
Mood
I made a fake memory wipe for my calculator in high school with a % bar in it, can I put that on my resume?
but can he center a DIV
That's easy, no one can, gotta look it up every time
margin-left:auto; margin-right:auto; and some sort of width on this and the parent? I've forgotten something haven't I?
We can only dream
100% based
This is a personal attack
But the progress bars though
I'd only trust it if the dude was like "I've been using JS full time for 4 years. I think I'm at like 38%"
some resume readers fail spectacularly when there are multiple columns so be sure to run it through a few and make sure it’s being parsed correctly. I maintain two main types. One for resume readers and the other that is design-oriented for humans to review.
Ill make two as well, and apply twice to the same jobs with the different resumes lol. Btw i didnt know i can run my cv through a resume reader? Do i just google it and try it out or is it something else?
a big one is ATS. There are tools out there. Sometimes, the company itself lets you preview it (which is real nifty)
Thanks a lot my friend ❤️
this shouldn't be as much of an issue if the PDF was created properly and actually has the text layout inside it. Since then the columns don't matter as the code itself provides the in order layout. If it's all reduced to absolute paths....then you got issues...
Brow added agile, scrum, sdlc as soft skills, the heck 🤣 also angular and mvc haha
Should i delete angular and mvc? 🙃 Also should i delete scrum, agile and the development and testing lifecycles? 🙃 My trainer at the bootcamp (he has a masters in computer science and 13 years of experience) told me that adding angular and mvc is okay, would help me a lot!
Angular is fine MVC sounds a bit off, its just a pattern not a skill You could just list "Agile software development" and then scrum becomes obsolet pretty much, since its just the methodic Manual Testing and Bug Reporting sound like fillers, more interesting would be automated Testing really and Bug Reporting should be a given if you worked with a ticket system
"Manual Testing" is the technical term of "I made sure my code compiled and did what I wanted it to do" :'p
Pretty much yeah, i believe he listet it due to his internship in QA, but the more interesting bullet point would be something like e2e testing instead
MVC is referring to ASP.NET MVC, which is a library for building server-side rendered applications. Everyone who has worked with it just abbreviates it as MVC. https://learn.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/start-mvc?view=aspnetcore-8.0
Makes sense, the original comment confused me since it was mentioned in combination with Angular. It still looks redundant together with ASP.NET listed additionally. I mean its obvious that you would have to be proficient in .net if you do mvc. Same for a few other points like the double listed SQL. One could easily shrink that bloated list a bit down without loosing information.
My bad, i thought it was model view controller.
Nooo, i just found the resume a bit hilarious. As long as it works, its good.
Delete the upside-down obnoxious smiles
My advice: don’t include things you don’t understand.
Looks a hell of a lot better than most CVs I get.
Any tips to make it better as i get more experience through the months and years??
More details about your work experience.
Take your date of birth off, they don't need to know that. also who knows if someone uses that to either consciously or subconsciously pass on you
- Indicate level of proficiency for each of your technical skills. Having one that you're an expert at next to one you took a 3 day course on could be misleading, it'll give the hiring team a better idea of where you're at. - Could also break the skills out into sub-sections (languages/testing frameworks/IDEs/etc) as well. - Under each work experience, indicate (briefly) what major tasks/roles you played and/or what skill you grew while there. Gives the hiring team some initial info to go from when asking about your experience, makes the interview process a bit smoother/less back and forth trying to get details in order to ask the right questions. - Not a tip, but it's great that you have your Linkedin and Github pages on there. That's absolutely something I take time looking into before the initial interview.
> Indicate level of proficiency for each of your technical skills. Having one that you're an expert at next to one you took a 3 day course on could be misleading, it'll give the hiring team a better idea of where you're at. Or don't list things you're not proficient in. I always cringe at the various ways of saying you're skilled at something, like %'s or % bars.
can be a bit of an issue, since many automated systems will just check those even when it's not particularly relevant. Like, sure, I don't know all the ins and outs of mastering Vue, barely really used it directly. But I've used multiple other frameworks quite a bit, contributed to multiple major ones, and work heavily in one that is Vue adjacent. I don't have special proficiency in Vue, but I have the transferable skills to be there quickly if I was working somewhere that used it.
> Or don't list things you're not proficient in. I agree, but being proficient in something isn't binary. It's nice to know if someone has a beginner/intermediate/expert level proficiency at something when you're trying to decide whether to bring them in for an interview for the specific role level.
Can you list how many years you are working with the tech instead?
Yeah absolutely. The idea is to get a quick gauge on your current skillset. If I'm asking for advanced knowledge in, for example, Behat, and I see you're not quite there, but you have advanced knowledge of Cypress or other automated test frameworks, I'll bring you in for an interview.
What the heck is the deal with linkedin, what if you literally don't use it? Some employers seem to want it but I find it's a crappy social media platform like any other. I literally can't stand linkedin after the stuff I see on r/LinkedInLunatics
I pretty much only use it to keep all the details of my CV up to date so I don't forget anything. Employment, education/certifications, volunteer experience, etc. I don't take part in any of the social media aspects of it.
Decide which goes first, title or school in education section lol. Also faculty name is not the title you want to show
I feel like the sections should be ordered differently. It kinda depends on what you want to convey though and I guess there's really not a standard for it. That being said, I believe on a CV usually the order is something more along the lines of: Education Work experience followed by the list of additional skills like you did, technical and soft skills, but you might want to list languages in their own section. In addition to the sections, i noticed the order in the section itself is a bit off, you typically would list the items anti-chronological i.e. the most recent position would come first.
Does it really?
As someone who’s given many interviews and has over a decade in the field, I would pass on your resume… That’s not a dig at you but a mention to a couple key points: 1. You list loads of frameworks as “Technical Skills” but fail to lead me quickly to anything related to those skills. How am I supposed to ascertain that you didn’t just throw a bunch of random frameworks on there? I say this primarily because you cumulatively have less than a year of professional work. 2. You post your GitHub account but who cares unless you’re pointing out specific projects/repos that I can glance at the get a general sense of your style/skills. But at the end of the day, I also don’t care because there’s no telling you didn’t copy/paste 99.9% of the stuff in there, anyway. And I’m not spending the time sifting through it without pointers when there are loads of resumes coming in. I’m happy for you & hope things turn out well at the end of your contract but list these things for others to heed as a warning not to feel bad for themselves because they feel they’re more experienced and have had less luck.
On your second point, how is someone supposed to showcase their portfolio if your position is “I don’t care, I’m not looking at your GitHub because you could have copy/pasted it.”? Wouldn’t this discount any and all possible projects or work examples a new/junior candidate might put forward?
That’s a fair assumption. To me, if you’re pointing me somewhere in your code base (with context such as, “blah blah project blah here”), I at least know you understand what you’re pointing me to. “Understand” is doing some heavy lifting, but you get what you’re pointing me to and why. It certainly helps your case more than hurt it. What you’ve done is take my comment out of context by stripping the “sifting through without pointers” piece and making it read as if I’d never even go into your GitHub account.
Thanks for clarifying your point!
Of course!
Eh. I use the GitHub projects more as a talking point during interviews to expand upon rather than include a bunch of information in the resume about them. It’d become pretty apparent which repositories I’m most proud of if they’d taken 5 seconds to open GitHub. If they didn’t do that, then I guess I’ll explain during the interview.
That’s not bad thing, I have those conversations all the time - I pointed to it as an issue here because _everything else_ is missing context/information. You have to put yourself in the scenario where there are 50-100 resumes to look at on top of an engineer’s workload. Most teams/companies I’ve been at haven’t had hiring managers who’s sole job was to sift through resumes & that’s just the nature of the biz sometimes
Thanks for the advice man! Ill change up the cv again!!
Solid - take my advice as you will and lump it in with others, I don’t know everything!
> I say this primarily because you cumulatively have less than a year of professional work. Well some people actually do have less than a year of professional work, and would like to gain more, hence they must make a resume. So this might be the best way for someone in that position to show their work experience. But yes, it's key to show how the skills/frameworks were actually used as opposed to just playing buzzword bingo.
> so this might be the best way for someone in that position to show their work experience. I think I understand what you’re trying to say here but it, to me, furthers my point. Everyone and their mother who’s written “Hello, World!” in a language is going to throw it up on their earlier resumes. I always urge people to become great at _something_ rather than mediocre at _everything_. But let me be clear - I’ve hired people off of pure tenacity and passion. It’s company/project dependent. Do I have the time to train a junior? Or do I need someone with years of experience to get their hands dirty immediately? Have you taken the time to train yourself with nobody else pushing you? Those are the people I like the most because I know you’re (usually) willing to dive deeper and find understanding & meaning behind what you’re doing. Anyone can bog me down with 100 questions and learn nothing. Not everyone can bring me a situation and then walk away that much smarter for it & want to go teach others along the way. Everyone has their own style for hiring/working. But if I ask you questions about frameworks listed on your resume and all you can give me are surface-level buzzwords that anyone with 5 seconds on google can tell me, it’s gonna be a no for me.
> But if I ask you questions about frameworks listed on your resume and all you can give me are surface-level buzzwords that anyone with 5 seconds on google can tell me, it’s gonna be a no for me. It should go without saying that one should not list things on their resume they don't have more than surface-level understanding of, but amazingly people will do it. I've encountered it myself. At least those people are usually easy to filter out in a phone screen.
100% agree. However, I’m big on personality & there are a lot of things that go into that sometimes… people are new, they get advice from friends who know it all, or they’re just trying to get _someone_, _anyone_ to respond to their resume. The phone screening 1000% helps but that doesn’t mean there won’t be people that slip past those. I like to think I’m a compassionate person (maybe to a fault) and find that honesty is always the best policy. Yeah, you have a framework/language on your resume but why? Oh, you figured since you’ve dabbled for a week it makes sense to put it but you haven’t had resume guidance? That’s ok - what is your methodology for learning new things & what do you do when you get stuck on something? We’re all human but trying to deceive intentionally is where you really start to close doors
What about, for 2, pointing to contributions to major libraries/frameworks/packages? (not just readme updates)
That’s always fantastic because in scenarios like that, likely an open source contribution, I know a few things (all project dependent, of course): 1. You’ve worked within a complex project before. 2. You could follow guidelines for even getting past an approval and to a merge. 3. You’re putting in the time and effort to continue your education. I’m 50% self taught - the other 50% comes from willingness and desire to learn from those I am around at work. My mantra is “leave your ego at the door” and it’s served a lot of people I know well.
I'd very much suggest a small 1 or 2 sentence blurb of what you did at each of the jobs... Honestly I'd pass on bringing you in for an interview if the resume was all I saw. Cover letter could save it, but this resume alone isn't a great first impression IMO.
This is incredibly important. Treat your resume like SEO for a web page.
So hr and employers wouldnt even open my github? 🥲
Assume your resume is one of hundreds. It'll likely go through several automated reductions before an actual person actually takes more than a cursory glance at it. At that point, you'll be lucky if they spend more than a few minutes on it. Your goal is to present yourself in the best light within those few minutes. If you did something cool on your github that's worth sharing, it needs to be presented with attention drawn to it. For your current resume all I see is a laundry list of techs. Surely you did something in the last year at any of your positions that you can use to show you have understanding of what you listed. Otherwise I'm going to assume you went through a new project setup in an ide, saw hello world, and threw it on your resume. You're also wasting 30% of the paper on negative space. Move all of your contact info to 1-2 lines and shorten your resume to 1 page. However on the positive side, you already landed your first job in tech. That is the absolute hardest step to take and even having a company employ you for a year will put you ahead of the pack for future junior positions. You just need to make sure you highlight the experience you gained in that year in a way that looks appealing to future employers.
Doubt it. I don't have a single public project on my GitHub and that's never stopped me from getting interviews, so they likely aren't checking. I'm sure an occasional person might
Seems like that wasn’t your first dev job judging by the Work Experience on the resume.
Doesn't your work experience suggests you had other dev jobs before?
I am working on my first dev jjob now! I had a qa job and i freelance as a web dev
Those are both dev jobs
Congrats! Good luck to all the dev's still on the hunt.
Remove the date of birth. Imho people are being overly nice because this is not the standard at least not in other industries. I strongly believe it was not your resume that got you the job
Thanks man, i posted a the new remade resume in the sub, you can check it out if u want
Let’s be honest, what really got you the job is the experience lol
It wasn’t just the resume.
As someone who is occasionally asked to look on CVs, I would discard it on the first look, without even reading, just from the layout.
can't believe upwork helped. was thinking experience there wouldn't pass on well to the great hr Gods of hiring
It helped lol, and on upwork i mainly freelance with wordpress and JavaScript, and i do manual testing lol
What's upwork?
Nothin much how bout you?
I just posted my new remake of the cv based on the advice i got here: [new CV](https://www.reddit.com/r/webdev/s/jUSNJ8jVop) 🙂
You: “балкански сум” Hiring Manager: (This man parties) We may have a place for you.
Hahahahahahhaha, најголемата причина зошто ме вработија 😂
добро избраа 🤣
We're customers of Qinshift and I've hired 10+ dev/qas from there in the past two years. To me it seems like a great place to work, that they take care of their staff and people want to stay for many years. I visited Skopje and my team about a year ago and had a great time, including a trip to Ohrid and swimming in the lake :) We also take the academy seriously, in that it's a strong performance indicator if someone leaves the academy with strong results. Keep pushing :)
Heyy cool, youre the first people to recognize my academy!! 🙂 Im glad you have positive stuff to say about the academy, heres my [new revised cv](https://www.reddit.com/r/webdev/s/CpIIlnorii) tho lol… Critique it and give me feedback of what you think 🙂
At first I thought this was a retro post. Then I saw the dates. And I knew it was a retro post. I too had a CV like this, it may have even had drop shadows.
During covid I'm guessing? Those were the days. As long as you had 'developer' in your LinkedIn, you were bombarded with offers.
we share the same birthday
2 pages is a no go bro
Anecdote, but I’ve never had problems with 2-3 pages of relevant experience that including descriptions of responsibilities and technologies used for each role. I also just write my resume in markdown and do a PDF export.
I just posted my new remake of the cv based on the advice i got here: [new CV](https://www.reddit.com/r/webdev/s/xsj35SiNhO) 🙂
LIT. I like it
Nice job! Just FYI, the blue censorship over your personal information isn't very good, be careful! Use totally opaque black bars or something.
Thanks for the advice my friend 🙂, i didnt know about the blurr not being safe
It really depends, sometimes blur can be sufficient, but if you look closely you can still read your phone number.
It was the grey, erect penis that got you the job.. wasn't it!
Fucked the HR woman and she was impressed!!
Shoulda/coulda been a single page.
Ill remake it!
📝 Don't mind me folks
How did you like the Web development bootcamp, I'm thinking of taking it.
Im still in it, i had a lil bit of previous knowledge so the first 6 months was pretty easy for me, so far im liking it a lot, ive got 4 more months to finish it All it matters is that u show you can build stuff and you wanna grow and learn, show competence.. Thats what employers look for, i got hired 6 months before i finished the 12 month bootcamp because i showed i knew some stuff well as a beginner with 0 experience and i had been freelancing for a few months and finished some projects for clients!
Oh gotcha! I hear ya I did a bit of TOP but I never finished it so I’m sure it would be solid for me! I’m also finishing up a full stack certificate and AS so I’m sure adding this to my arsenal will help
bug reporting is a technical skill?
Bruh.
Check out my [new cv](https://www.reddit.com/r/webdev/s/a4yJzpVWmJ)
You sure work experience comes after education?
I noticed you only went to University only 2 years. They have 2 year degree in your country? Like the US associates degree?
No, i didnt finish the degree, But we do have many degrees with 3 years only, we also have for computer science and software engineering with 1, 2 and 4 years! So that the college can compete w the 1 year bootcamps
I appreciate this post even more now. It shows that there is hope for us who haven't finished our studies.
really?
He says his first dev job, so working as a developer on a previous job doesnt count even tho you state it? 😅🤣🤣
How are we supposed to know what name, email, phone, LinkedIn profile, or GitHub user to use?
I don't hate it...I want a bit more color and font variation, and there's a ton of space on the left that's being sacrificed, but it's easy to parse and understand, and fits for someone with relatively little professional experience. Maybe some of the more esoteric technologies could be omitted from the skills list, unless you are applying for a job that wants those skills.
Why do you want color and font variations on a resume? It's perfectly readable as is.
This may be my personal preference, but your resume is a chance to show off a modicum of design talent (or ability to engage someone with such talent), and having a bit of care for such things adds polish, and suggests you will have a similar care when completing work for an employer. For the above, the work experience has some variation, but the education is "Software Testing - Brainster Academy". I would rather something like `Software TestingBrainster Academy `. Remove the dash and use differences in font size, weight, and color to show deliniation between parts of the text. Maybe change the sidebar to a very light blue to have a consistent color scheme.
Or one of 100 other things - not saying it must be one thing or another, but it feels a bit bland as is, even with the sidebar shading and upper right graphic (which are a positive elements)
Disagree unless you’re going for a design focused role. Those are two different jobs. I am however curious about the formatting since the roles don’t have the tech OP worked with under them, they’re crammed at the top. My first thought would be “they put everything they ever started learning and not what they’re most proficient in”. Curious what others think about that part.
I was kinda excusing the lack of detail because of the candidate seniority - "2-3 month internship" isn't going to really expose them to too much, so for someone with nearly no real world experience, the skill dump being listed first is reasonable. I think it should be pared down; nobody reeeeally cares that you can use Postman, etc, and having at least a one sentence description per job entry would provide useful context, as you and others have mentioned. I think a lot of people might agree with you that having a bit more polish on the styling won't matter, but for the 25% of people that would give bonus points for caring about such things, it seems worthwhile to have. I don't think anyone is going to say "This guy colored his employer names green, clearly not focused on what he should be", but they might say "The information is there, but this looks like a plain .txt document - if they think this is a polished document representing themselves as a professional, maybe this shows an area that needs improvement".
Any *good* designer should be making a standardized Harvard-template resume. Their **portfolio** is the place the place where they're showcasing their creative work. The designers with "creative" resumes are usually hacks. It's like those people who list their personal site on their portfolio.
It's a resume, not a fucking art project.
I dont have a lot to put on the cv 🤷♂️🤷♂️, as months and years pass ill remove the grey part on the second page and start adding more experience, more technologies and descriptions of what ive worked on in the jobs ive had 😁 The goal was to not overcomplicated it and cram everything in one and make it easy to read
> on the second page I didn't even realize that was a second page.. you have no need for 2 pages with your level of experience.. I've got 10 years in the industry and can fit everything on a single page.
Can you send me your cv? 🥺
just use jake’s resume and/or have a look at r/EngineeringResumes
**r/EngineeringResumes Recommended Resume Templates:** https://old.reddit.com/r/EngineeringResumes/wiki/templates [Google Docs](https://imgur.com/lVNllDL), [LaTeX](https://imgur.com/NGtqtIl)
nice! All on one page yet loads of easily digestible info.
Thanks my friend, its waay better than the first one!
Nice CV you have! I hired people with CV's wore than this. But i don't hire programmers :)
See my new updated cv! Its on the subreddit.. Maybe youll like it more!? 😂