In my geographic area, you really need to push tech names as much as possible and accept agencies will rewrite your CV anyway. Agencies need a good starting point with buzzwords that they can make fit the job. The client won’t see your raw cv or anything like it. When I interview, I like to pick a point and get into some detail to prove if its just speel or honest statements
I have links to my portfolio and my Github account on my resume. I treated my bootcamp experience as pseudo-work experience by describing the projects I built and technologies(programs) used. I didn't include my resume on my portfolio but I have a link in my "about me" section pointing to it. Also, I always use bullet points. Love them! All of my projects are deployed on stand-alone websites. I haven't gotten the job yet, but I'm not discouraged. It takes awhile to get the first job. My only frustration is the job postings that list every language and technology under the sun! My resume clearly states my stack. Recently, I received a coding challenge that included Angular. Not in my stack! Now, I'm teaching myself Angular. With the first job its always hard to navigate the interview process. Good luck, everybody!
One tip with keywords apparently is to cram them in but in white font so they are presentable in a manual review by being invisible but picked up by the scan
As a developer that has been put on the hiring team for our next collegue I completely agree with the points mentioned here. I wanted to be fair and read all the applicants application but I ended up going straight for the resume and if that fit what we needed I would go back and read the application.
Hey Tim, I just wanted to thank you from the bottom of my heart for creating videos like this one, you are one of the people who helped me to get my first programming job and I feel the need to express grattitude to everyone who helped me along the way :) this includes Academind, Fireship, Traversy Media, Lama Dev, kudvenkat, Laith Academy, Jack Herrington, The Net Ninja, Web Dev Simplified, Bro Code, freecodecamp, Theo - ping gg, Mosh Hamedani, Ben Awad, Tech with Tim to name a few, I am very grateful for you guys! Thank you!
I found it's difficult to fit one page resume for people like me has over 20 years of experience and average one project per year so about 20+ projects. With skill set list and education/certificate all I can have is title of each job and year when attend the name of the company to fit in one page. The reviewer will not see anything or achievement of what I do. I am curious to see any sample resume of people similar to myself.
That's a good suggestion for a future video. What I recommend is to shorten your resume. For instance, list each company you worked for, but only list what you did at the past couple. Honestly, while the skills you learned 20 years ago have helped mold you into who you are, the projects you did back then aren't relevant to today. Anything older than about 5-8 years isn't really valuable enough to share in a resume. During an interview, you can talk about the various things you learned over the years, but that older code isn't going to be valuable in itself. Also, who you were 10 years ago isn't who you are today. Your more recent accomplishments are what is most important to share. Even older certifications aren't really valuable. Does it really matter that you have your MCSD when it was based upon code from over a decade ago? It doesn't hurt to list if you have space, but don't let it distract from the really important parts of your resume.
@@IAmTimCorey Thanks Tim. I really like your recommendation of only having some points in recent projects and just mentioning older projects. I noticed that it is myself which can't let go of the past.I already knew back then the technology is kinda reset every 3-5 years as a cycle and as you mentioned resume only good for 2 cycles. We all need keep humble and keep learning. A small percentage of skills you can keep like language fundamental and architecture but rest won't build up for life like other profession.
It is still relevant to have one up to date. Even if a recruiter gets you in the door, it is still good to have something tangible to hand to an interviewer before a discussion.
A resume has only seconds (max) to do its trick to win the first race, then has a minute(s) to be into the second round to win the race, then if interesting enough, it will be within a dozen (handful) of candidates finally.
I quit my job after one year experience and i'm unemployed for two weeks. What is expectations from a one year experience? Is it sound fair: someone who experience with micro services?
There isn't much expectation when it comes to one year of experience. It is something, but it isn't a lot. Still, take advantage of it without exaggerating.
"I don't update my resume, because I don't need to anymore" - The dream, can't wait to be able to say that
It is a nice place to be. It takes a lot of hard work to get here.
5 to 7 years at one company is gonna get you there
In my geographic area, you really need to push tech names as much as possible and accept agencies will rewrite your CV anyway. Agencies need a good starting point with buzzwords that they can make fit the job. The client won’t see your raw cv or anything like it. When I interview, I like to pick a point and get into some detail to prove if its just speel or honest statements
I have links to my portfolio and my Github account on my resume. I treated my bootcamp experience as pseudo-work experience by describing the projects I built and technologies(programs) used. I didn't include my resume on my portfolio but I have a link in my "about me" section pointing to it. Also, I always use bullet points. Love them! All of my projects are deployed on stand-alone websites. I haven't gotten the job yet, but I'm not discouraged. It takes awhile to get the first job. My only frustration is the job postings that list every language and technology under the sun! My resume clearly states my stack. Recently, I received a coding challenge that included Angular. Not in my stack! Now, I'm teaching myself Angular. With the first job its always hard to navigate the interview process. Good luck, everybody!
Yep, that can be an issue. Best wishes in getting your first job. You seem to be on the right track.
Ultimate Video For Interview Preparation
Great!
One tip with keywords apparently is to cram them in but in white font so they are presentable in a manual review by being invisible but picked up by the scan
Yeah, that can work, although it can also backfire.
I can almost feel the embarrassment that would cause @@IAmTimCorey
As a developer that has been put on the hiring team for our next collegue I completely agree with the points mentioned here. I wanted to be fair and read all the applicants application but I ended up going straight for the resume and if that fit what we needed I would go back and read the application.
What do you think about so many companies using ridiculous coding tests that dont actually reflect the type of work at the company?
Tim, i wanna say thanks so much for everything you have taught me a lot!
You are welcome.
Very helpful, thanks for sharing...
You are welcome.
Hey Tim, I just wanted to thank you from the bottom of my heart for creating videos like this one, you are one of the people who helped me to get my first programming job and I feel the need to express grattitude to everyone who helped me along the way :) this includes Academind, Fireship, Traversy Media, Lama Dev, kudvenkat, Laith Academy, Jack Herrington, The Net Ninja, Web Dev Simplified, Bro Code, freecodecamp, Theo - ping gg, Mosh Hamedani, Ben Awad, Tech with Tim to name a few, I am very grateful for you guys!
Thank you!
I found it's difficult to fit one page resume for people like me has over 20 years of experience and average one project per year so about 20+ projects. With skill set list and education/certificate all I can have is title of each job and year when attend the name of the company to fit in one page. The reviewer will not see anything or achievement of what I do. I am curious to see any sample resume of people similar to myself.
That's a good suggestion for a future video. What I recommend is to shorten your resume. For instance, list each company you worked for, but only list what you did at the past couple. Honestly, while the skills you learned 20 years ago have helped mold you into who you are, the projects you did back then aren't relevant to today. Anything older than about 5-8 years isn't really valuable enough to share in a resume. During an interview, you can talk about the various things you learned over the years, but that older code isn't going to be valuable in itself. Also, who you were 10 years ago isn't who you are today. Your more recent accomplishments are what is most important to share. Even older certifications aren't really valuable. Does it really matter that you have your MCSD when it was based upon code from over a decade ago? It doesn't hurt to list if you have space, but don't let it distract from the really important parts of your resume.
@@IAmTimCorey Thanks Tim. I really like your recommendation of only having some points in recent projects and just mentioning older projects. I noticed that it is myself which can't let go of the past.I already knew back then the technology is kinda reset every 3-5 years as a cycle and as you mentioned resume only good for 2 cycles. We all need keep humble and keep learning. A small percentage of skills you can keep like language fundamental and architecture but rest won't build up for life like other profession.
How to have a nice portfolio to show when my portfolio are all the apps I did for my previous employeer and thus are private?
How relevant is the CV these days when you have a few years of experience and the recruiters contact you on linkedin without having to apply to jobs?
It is still relevant to have one up to date. Even if a recruiter gets you in the door, it is still good to have something tangible to hand to an interviewer before a discussion.
Please use chapters in your video because you have big videos so we can watch video more productively.
Thank you for this!
You are welcome.
A resume has only seconds (max) to do its trick to win the first race, then has a minute(s) to be into the second round to win the race, then if interesting enough, it will be within a dozen (handful) of candidates finally.
Yep.
I quit my job after one year experience and i'm unemployed for two weeks. What is expectations from a one year experience? Is it sound fair: someone who experience with micro services?
There isn't much expectation when it comes to one year of experience. It is something, but it isn't a lot. Still, take advantage of it without exaggerating.
Could you give us an actual resume as a good example?
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
I did not write my CV because I did not apply to work in any company because we do not need them..
I'm not sure what this means.
Ah yes, the “fk a job, I’m an entrepreneur” card. Noice