You don’t need to lie on your resume for it to stand out and be impressive.
First, stop listing “duties” and generalized things for the role. As somebody that’s done a few hundred interviews, I quickly bin those resumes. I have a good understanding of what a related role’s duties are that would make you qualified for a role I’m interviewing for.
Your goal in a resume is to show the hiring team of what you can provide to the team/company if you are brought on board.
What you should do is keep track of you work successes and KPIs and periodically update your resume with those successes and metrics for that role. Got a top performer review status, log it. Increased sales for the department by some % for the year, log it. Delivered a highly complex & valuable project, log it.
If you do the above, I can have a good understanding of what you’re actually capable of and how you utilize the skills you have within a role.
Are you sure not including duties and what you actually did is recommended?
Like, “Software Engineer” could mean bloody anything if you don’t specify what you actually did. You could have been mindlessly doing minor Jira tickets and running import tools, or you could be architecting entire pieces of enterprise software.
Listing your successes, metrics, and accomplishments will drive home your actual work duties and capabilities.
If you’re listing the following, you’ve failed in writing a solid entry to tell me that you’re a bugfix and data import wizard:
Utilized Jira to fix bugs.
Used company import tools to move data between systems.
Instead, you could write entries like:
Took ownership and closed x bug tickets over y months which was z% over the organizational goal.
Created and documented a Workflow to speed up the process of importing data by x%, making me the go to person for company data imports.
I’m not saying to lie or embellish either. I’m saying that you need to think about how you market your skills for sale as a service. If I’m looking for somebody with those skills, the latter two bullet points are going to stand out a far lot better than the former.
I live in the USA. I use the process I’ve described on my resume. I’ve also just landed a new job and started within the last month. When sending out resumes on my latest job search I had a 90% response rate, all for jobs I’d actually like to work at. The job I accepted was after the recruiter that reviewed my resume reached out to me to tell me the role I applied for had been filled but that they had another role that I’d be a fit for in the process of being written and wanted to get the ball rolling so I could be at the front of the interview process for it.
I’d say it’s “standard” because people were poorly trained on what to put on their resumes starting in high school and even college. I even used the “standard” before and struggled to land interviews early in my career. It wasn’t until about 15 years ago that I did a deep dive into resume writing and job searching techniques that I completely overhauled my resume and started actually getting call-backs/emails and interviews that would eventually wind up in landing jobs that I actually wanted.
Just because something is “standard” doesn’t mean it’s what we should be doing, or is the right way. The job market has changed over the years and ATSs reviewing resumes meant that people had to figure out how to get past those systems 20 years ago. As LLMs have been added to ATSs it’s only gotten harder to get past the initial gate with a resume drop.
A Kagi search for “resume accomplishments vs duties” will give you a plethora of sources discussing this from job seekers, HR professionals, recruiters, and even some university research.
Hi, thanks so much for that useful information. I don’t have kagi or any paid additional service. I’ll see what I can find, I do appreciate your letting me know!
You don’t need to lie on your resume for it to stand out and be impressive.
First, stop listing “duties” and generalized things for the role. As somebody that’s done a few hundred interviews, I quickly bin those resumes. I have a good understanding of what a related role’s duties are that would make you qualified for a role I’m interviewing for.
Your goal in a resume is to show the hiring team of what you can provide to the team/company if you are brought on board.
What you should do is keep track of you work successes and KPIs and periodically update your resume with those successes and metrics for that role. Got a top performer review status, log it. Increased sales for the department by some % for the year, log it. Delivered a highly complex & valuable project, log it.
If you do the above, I can have a good understanding of what you’re actually capable of and how you utilize the skills you have within a role.
Are you sure not including duties and what you actually did is recommended?
Like, “Software Engineer” could mean bloody anything if you don’t specify what you actually did. You could have been mindlessly doing minor Jira tickets and running import tools, or you could be architecting entire pieces of enterprise software.
Listing your successes, metrics, and accomplishments will drive home your actual work duties and capabilities.
If you’re listing the following, you’ve failed in writing a solid entry to tell me that you’re a bugfix and data import wizard:
Instead, you could write entries like:
I’m not saying to lie or embellish either. I’m saying that you need to think about how you market your skills for sale as a service. If I’m looking for somebody with those skills, the latter two bullet points are going to stand out a far lot better than the former.
It seems to be the standard requirement in the USA, like having a resumé rather than a CV. I’d rather not, but it is standard, here.
I live in the USA. I use the process I’ve described on my resume. I’ve also just landed a new job and started within the last month. When sending out resumes on my latest job search I had a 90% response rate, all for jobs I’d actually like to work at. The job I accepted was after the recruiter that reviewed my resume reached out to me to tell me the role I applied for had been filled but that they had another role that I’d be a fit for in the process of being written and wanted to get the ball rolling so I could be at the front of the interview process for it.
I’d say it’s “standard” because people were poorly trained on what to put on their resumes starting in high school and even college. I even used the “standard” before and struggled to land interviews early in my career. It wasn’t until about 15 years ago that I did a deep dive into resume writing and job searching techniques that I completely overhauled my resume and started actually getting call-backs/emails and interviews that would eventually wind up in landing jobs that I actually wanted.
Just because something is “standard” doesn’t mean it’s what we should be doing, or is the right way. The job market has changed over the years and ATSs reviewing resumes meant that people had to figure out how to get past those systems 20 years ago. As LLMs have been added to ATSs it’s only gotten harder to get past the initial gate with a resume drop.
A Kagi search for “resume accomplishments vs duties” will give you a plethora of sources discussing this from job seekers, HR professionals, recruiters, and even some university research.
Hi, thanks so much for that useful information. I don’t have kagi or any paid additional service. I’ll see what I can find, I do appreciate your letting me know!
So, what you’re saying is people should lie about work successes instead of degrees? Got it. Will do.