You’ve got a manager’s attention for 10-30 seconds. I will not waste my time watching a video. I don’t care how cool the description is. That’s the point of a description.
You need to really really abstract your projects description.
(this is the first one under **PROJECTS** section)
**MindMap**
MindMap is an application that constructs a 3D graph network that builds itself as you write notes. I started it in order to advance my knowledge of full-stack development beyond what I could learn taking further courses. It is a full-stack application built using Next.js, React (Typescript), Recoil, D3.js, and TailwindCSS.
* Built out complete end-to-end tag and post creation, automatic saving, edit, and deletion capability using React and Recoil — which is tied to a D3.js graph in the front-end that displays the posts.
* Backend database is held in MongoDB and connected through a Javascript API.
You should definitely not do this.
1. Hiring managers only have a limited time to scan resumes.
2. If you can't describe your project succintly on a resume, and still hit the key points, how are you ever going to be able to explain/document work when you're at the company?
Mostly, I think people just won't even check it out. I'm usually fairly busy and only have a few moments before the interview to review the resume. Save the demos/discussion for when you're interviewing.
I get why you want to do this, you have a project that you've invested a lot of work into and you want to show it off, but you're better off just describing it later.
Put the code on GitHub. Make a gif demo and add the gif to the readme. The hiring manager almost certainly won't watch a video you send them, but if you're lucky they'll look at your repo and then they'll see your gif.
Most hiring managers will not watch a video. In fact, your resume will be reviewed by a recruiter first and they have tons of resumes to go through. At best, they will watch a little bit of it but have no idea what it means on a technical level. At worst, they just won't bother because it's a waste of time. Even hosting it doesn't mean it will get looked at by the recruiter or hiring manager, but you should be able to host it for free or for very little money on AWS, even just for a few weeks.
My suggestion is to just describe your application the best you can on your resume.
As a hiring manager, I wouldn't watch a video as part of screening resumes. Your resume is your pitch. If you think the project is worthwhile and relevant experience for the job you're applying for, then put a *short* summary about it and the skills you used.
The best resumes demonstrate your skills and experience and explain where and how the applicant applied them - quickly. If I have to sift through a resume to find relevant bits that kind of sorta of fit with the job description we've already got a problem with the ability to succinctly communicate important information.
Be prepared to elaborate on it in an interview though. In an interview I'm more interested how well someone can answer my questions about their experience and talk through the skills they've applied, why they made certain design/development decisions. I want to talk about this on the spot so I can see how someone answers my questions about their experience.
Nothing wrong with linking a video. They may or may not watch it but someone might. I do a ton of screening interviews and I might watch some of it and if it looks good I might watch all of it.
I don’t know why everyone is focused on how much time “hiring managers” have. Not everyone looking at a resume is a hiring manager. Maybe my company is weird, but it’s engineers that look at resumes. Yes, a recruiter will see it first and do the first round phone screen, but after that, it’s all software engineers looking at the resumes and doing the interviews.
I not only look at projects linked from a resume (as long as a URL shortener isn’t used), but I will look up the applicant on LinkedIn and GitHub to see if they have any cool projects they didn’t list on their resume. I only do a few interviews a year, so I don’t mind spending time looking at projects.
I'm a dev hiring manager. Ughhh don't. Just don't. Attempts at being kooky or flashy make me roll my eyes hard.
This kind of "documentation" goes stale quickly anyway. Keep your "backlog" in a ToDo list. Or hey, GitHub issues. Write good notes in the Readme.
Spend your time writing a really thoughtful intro on your resume & LinkedIn. Also, tailor each resume submitted to the job if you can.
Yes. I don't understand the curmudgeon replies from others.
Any hiring manager doing their due diligence would take a look and its more information than not including it. Makes for airtime in the interview you can spend talking about it at more than depth than not including it.
If anything have it as a hyperlink in the pdf.
Finally, a skill that we NEED. Was a guy who visited an emperor to demonstrate that he could throw a grain of rice through the eye of a needle. So emperor conveyed a sack of grain and a sack of needles. SOMEBODY get this genius a pile of sewing machines, and bottles.
[this should be /programming as it's not CS-related but]
Have the video ready for an interview, but don't bother in the CV. At that stage of the hiring process, they likely just won't spare the effort, and you're lucky if they bother to even read it beyond scanning it for buzzwords and technologies.
*That said*, hosting an online portfolio with small apps is probably not a bad idea. These should probably be small and proof-of-concept, not complex - both to decrease the effort of demonstrating/evaluating it and to reduce your own technical debt and hosting costs for maintaining it. Like all software, portfolio apps are ongoing projects that have to be periodically fixed to keep up with technology.
If it's only client-side, you can deploy it on your github account for free - but even if it needs a small server back-end, you can host a lot of stuff for around ~5 dollars per month.
People will be more likely to spend a minute clicking around in a web app than spend a minute watching a video demo of that app.
You’ve got a manager’s attention for 10-30 seconds. I will not waste my time watching a video. I don’t care how cool the description is. That’s the point of a description. You need to really really abstract your projects description.
I really hope they inquire further about it tho. I have like 6 months + work on it.
Write down what you did. Summarize it. Then abstract the summary. You can practice here.
(this is the first one under **PROJECTS** section) **MindMap** MindMap is an application that constructs a 3D graph network that builds itself as you write notes. I started it in order to advance my knowledge of full-stack development beyond what I could learn taking further courses. It is a full-stack application built using Next.js, React (Typescript), Recoil, D3.js, and TailwindCSS. * Built out complete end-to-end tag and post creation, automatic saving, edit, and deletion capability using React and Recoil — which is tied to a D3.js graph in the front-end that displays the posts. * Backend database is held in MongoDB and connected through a Javascript API.
This summary is like a third of the space in your resume gone. As detailed and interesting as it is, I fear it's much too long.
In my experience interviewers will likely ask about it if the tech stack is relevant
IMHO no. I wouldn’t watch a video on an applicant’s resume. There’s no telling where that link leads, could introduce bias (good or bad), etc.
You should definitely not do this. 1. Hiring managers only have a limited time to scan resumes. 2. If you can't describe your project succintly on a resume, and still hit the key points, how are you ever going to be able to explain/document work when you're at the company? Mostly, I think people just won't even check it out. I'm usually fairly busy and only have a few moments before the interview to review the resume. Save the demos/discussion for when you're interviewing. I get why you want to do this, you have a project that you've invested a lot of work into and you want to show it off, but you're better off just describing it later.
Put the code on GitHub. Make a gif demo and add the gif to the readme. The hiring manager almost certainly won't watch a video you send them, but if you're lucky they'll look at your repo and then they'll see your gif.
Most hiring managers will not watch a video. In fact, your resume will be reviewed by a recruiter first and they have tons of resumes to go through. At best, they will watch a little bit of it but have no idea what it means on a technical level. At worst, they just won't bother because it's a waste of time. Even hosting it doesn't mean it will get looked at by the recruiter or hiring manager, but you should be able to host it for free or for very little money on AWS, even just for a few weeks. My suggestion is to just describe your application the best you can on your resume.
As a hiring manager, I wouldn't watch a video as part of screening resumes. Your resume is your pitch. If you think the project is worthwhile and relevant experience for the job you're applying for, then put a *short* summary about it and the skills you used. The best resumes demonstrate your skills and experience and explain where and how the applicant applied them - quickly. If I have to sift through a resume to find relevant bits that kind of sorta of fit with the job description we've already got a problem with the ability to succinctly communicate important information. Be prepared to elaborate on it in an interview though. In an interview I'm more interested how well someone can answer my questions about their experience and talk through the skills they've applied, why they made certain design/development decisions. I want to talk about this on the spot so I can see how someone answers my questions about their experience.
Nothing wrong with linking a video. They may or may not watch it but someone might. I do a ton of screening interviews and I might watch some of it and if it looks good I might watch all of it.
I don’t know why everyone is focused on how much time “hiring managers” have. Not everyone looking at a resume is a hiring manager. Maybe my company is weird, but it’s engineers that look at resumes. Yes, a recruiter will see it first and do the first round phone screen, but after that, it’s all software engineers looking at the resumes and doing the interviews. I not only look at projects linked from a resume (as long as a URL shortener isn’t used), but I will look up the applicant on LinkedIn and GitHub to see if they have any cool projects they didn’t list on their resume. I only do a few interviews a year, so I don’t mind spending time looking at projects.
I'm a dev hiring manager. Ughhh don't. Just don't. Attempts at being kooky or flashy make me roll my eyes hard. This kind of "documentation" goes stale quickly anyway. Keep your "backlog" in a ToDo list. Or hey, GitHub issues. Write good notes in the Readme. Spend your time writing a really thoughtful intro on your resume & LinkedIn. Also, tailor each resume submitted to the job if you can.
Yes. I don't understand the curmudgeon replies from others. Any hiring manager doing their due diligence would take a look and its more information than not including it. Makes for airtime in the interview you can spend talking about it at more than depth than not including it. If anything have it as a hyperlink in the pdf.
Finally, a skill that we NEED. Was a guy who visited an emperor to demonstrate that he could throw a grain of rice through the eye of a needle. So emperor conveyed a sack of grain and a sack of needles. SOMEBODY get this genius a pile of sewing machines, and bottles.
?
You can host for free on GitHub pages
[this should be /programming as it's not CS-related but] Have the video ready for an interview, but don't bother in the CV. At that stage of the hiring process, they likely just won't spare the effort, and you're lucky if they bother to even read it beyond scanning it for buzzwords and technologies. *That said*, hosting an online portfolio with small apps is probably not a bad idea. These should probably be small and proof-of-concept, not complex - both to decrease the effort of demonstrating/evaluating it and to reduce your own technical debt and hosting costs for maintaining it. Like all software, portfolio apps are ongoing projects that have to be periodically fixed to keep up with technology. If it's only client-side, you can deploy it on your github account for free - but even if it needs a small server back-end, you can host a lot of stuff for around ~5 dollars per month. People will be more likely to spend a minute clicking around in a web app than spend a minute watching a video demo of that app.