Choose from a wide range of NEWCV resume templates and customize your NEWCV design with a single click.
Use ATS-optimised Resume and resume templates that pass applicant tracking systems. Our Resume builder helps recruiters read, scan, and shortlist your Resume faster.
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create Resume
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create ResumeYour resume does not get stronger because it lists more responsibilities. It gets stronger when it proves what happened because you were in the role. In the Canadian job market, recruiters and hiring managers are not reading your resume to learn what a project coordinator, accountant, administrative assistant, sales manager, or software developer generally does. We already know the job category. What we need to understand is whether you performed well, solved relevant problems, improved something, handled real complexity, or contributed in a way that makes you worth interviewing.
A responsibility tells me what you were supposed to do. Evidence tells me whether you actually did it well. That difference is often where interviews are won or lost.
Most weak resumes are not weak because the candidate has no experience. They are weak because the resume makes good experience sound ordinary.
I see this constantly. A candidate has handled serious workloads, supported difficult stakeholders, improved processes, trained people, managed competing priorities, cleaned up messy operations, or helped increase revenue. Then their resume says something painfully flat like:
Weak Example
“Responsible for managing client accounts and preparing reports.”
That sentence technically says something. It just does not say anything useful.
The problem is not that responsibilities are wrong. The problem is that responsibilities are only the starting point. They describe the assignment, not the impact. When a recruiter reads a resume full of duties, the mental reaction is usually:
“Fine, but how well?”
That question matters. A hiring manager is not trying to hire a list of duties. They are trying to reduce risk. They want to know whether you can step into their team and handle the real work, not the sanitized job description version of it.
In Canada, where many job postings attract large applicant pools, especially for remote, hybrid, administrative, customer service, HR, marketing, finance, operations, project, and technology roles, a resume that only repeats responsibilities can disappear quickly. Not because the person is unqualified, but because the resume gives the employer no reason to choose that candidate over ten others with similar job titles.
Recruiters scan resumes with a simple but unforgiving question in mind:
“Is there enough here to justify moving this person forward?”
That does not mean every resume gets a deep, careful literary reading. It means your resume needs to make the right evidence easy to find.
When I screen a resume, I am usually looking for several things at once:
Does this candidate match the core requirements of the role?
Have they worked in a similar environment, industry, company size, or function?
Do they show progression, stability, or a clear reason for movement?
Can I understand the level of complexity they handled?
Do their achievements match what this employer actually cares about?
Is there proof, or are they just describing the job title?
This is why responsibility based resumes often feel unfinished. They may include keywords, but they lack judgement. They tell me the candidate was near the work, but they do not prove the candidate drove the work.
That distinction matters more than candidates realize. Hiring is not only about experience. It is about confidence. Evidence gives the reader confidence.
A responsibility describes what you were assigned.
Evidence explains what you did with that assignment.
For example:
Weak Example
“Handled customer inquiries.”
This is a responsibility. It tells me the person interacted with customers. It does not tell me volume, difficulty, quality, speed, tools, outcomes, escalation level, or business impact.
Good Example
“Resolved 60 plus customer inquiries per day across phone, email, and live chat while maintaining quality standards and reducing repeat escalations.”
That is stronger because it gives the recruiter context. It shows workload, communication channels, performance expectations, and a hint of quality.
Another example:
Weak Example
“Managed social media accounts.”
Again, this is not terrible. It is just incomplete.
Good Example
“Managed LinkedIn and Instagram content calendars for a Canadian B2B services brand, increasing monthly engagement by 38 percent through sharper post positioning, stronger calls to action, and improved content timing.”
Now I can see platform, audience, market, impact, and method. That is evidence.
Good resume evidence usually answers at least one of these questions:
How much?
How many?
How often?
How quickly?
Compared to what?
For whom?
With what result?
Under what conditions?
What changed because of your work?
A strong resume does not need every bullet to include a number. That is another piece of advice that gets repeated badly. Numbers help, but only when they mean something. A random metric attached to a vague bullet is not strategy. It is decoration.
Candidates often write resumes as if employers will believe every claim at face value.
They will not.
That does not mean employers think candidates are lying. It means hiring managers have seen enough resumes to know that words like managed, supported, led, coordinated, improved, and assisted can mean wildly different things depending on the person.
One candidate “managed” a project by owning the timeline, budget, stakeholder updates, risk register, vendor communication, and final delivery.
Another candidate “managed” a project by attending meetings and updating a spreadsheet.
Same verb. Completely different value.
This is why evidence matters. It narrows the interpretation gap.
Hiring managers are trying to picture you in their environment. They are asking:
Can this person handle our workload?
Will they need heavy supervision?
Have they dealt with similar pressure?
Do they understand the kind of problems we have?
Are they exaggerating, or does the resume feel grounded?
Do they communicate with enough clarity to be trusted?
Evidence makes your resume feel more credible because it gives the reader something concrete to evaluate. Generic responsibility language forces the reader to guess. And in hiring, guessing usually works against the candidate.
One of the biggest resume mistakes I see is copying language from job descriptions without turning it into candidate specific proof.
Job postings describe what the employer wants. Your resume needs to show where you have already done something similar.
There is a difference.
A job posting might say:
“Manage stakeholder relationships and support cross functional project delivery.”
If your resume says the same thing, it sounds like you copied the requirement. It may help with keyword matching, but it does not help with persuasion.
A stronger version would be:
Good Example
“Coordinated project updates across sales, operations, and finance teams during a CRM migration, helping reduce duplicate data entry and improve handoff accuracy between departments.”
This tells me the candidate understands cross functional work in practice. It gives me the setting, teams involved, project type, and operational result. That is far more useful than repeating “stakeholder management” because the phrase sounds professional.
A lot of candidates think ATS optimization means copying keywords. That is only part of it. Applicant tracking systems may help organize and search applications, but humans still evaluate meaning. A resume packed with keywords but lacking evidence can pass a basic search and still fail the actual screening.
The ATS is not impressed by your buzzwords. The recruiter is not emotionally moved by “results oriented professional.” Everyone claims to be results oriented. Results are more convincing when you actually show the result.
Evidence is any specific information that helps prove the value, scope, difficulty, quality, or outcome of your work.
It can include numbers, but it can also include context. This is important because not every role has clean revenue figures, performance dashboards, or public metrics. Many Canadian job seekers work in roles where impact is operational, administrative, confidential, relationship based, or hard to quantify directly.
Useful resume evidence can include:
Revenue, sales growth, cost savings, budget size, or profitability impact
Volume of work, such as files processed, clients supported, tickets resolved, reports prepared, or accounts managed
Time saved, delays reduced, turnaround improved, or processes shortened
Accuracy improvements, error reduction, compliance results, or quality control outcomes
Team size, stakeholder groups, departments supported, or leadership scope
Tools used, systems implemented, platforms managed, or technical environments supported
Project scale, timelines, budgets, locations, vendors, or business units involved
Customer, client, patient, employee, or user outcomes
Recognition, promotions, internal selection, trusted responsibilities, or expanded ownership
Before and after changes, especially where you improved a messy process
Some of the strongest evidence is not dramatic. It is simply specific.
For example:
Weak Example
“Assisted with onboarding.”
Good Example
“Supported onboarding for 40 plus new hires across three departments by preparing documentation, coordinating orientation schedules, and tracking completion of required training.”
Nothing about that is flashy. But it is useful. It tells me the candidate can coordinate details, support volume, work across departments, and handle structured employee processes.
That is how real hiring decisions often work. Not every employer is looking for a superhero. Many are looking for someone who can do the work properly without creating more chaos. Evidence helps show that.
The easiest way to improve a responsibility based resume is to stop asking, “What was I responsible for?” and start asking, “What did my work change, support, improve, protect, deliver, or make easier?”
That shift matters.
A responsibility based bullet usually follows this pattern:
“Responsible for X.”
An evidence based bullet usually follows this pattern:
“Did X for Y purpose, under Z conditions, resulting in A outcome.”
You do not need to force every bullet into the exact same structure. In fact, please do not. Resumes that repeat the same sentence pattern become boring quickly. But the thinking behind the structure is useful.
Here are practical ways to strengthen a bullet:
Scale helps the recruiter understand size and workload.
Weak Example
“Managed invoices.”
Good Example
“Processed 250 plus vendor invoices monthly using QuickBooks and Excel, maintaining accurate records and supporting timely payment cycles.”
Context helps the reader understand the environment.
Weak Example
“Created reports for management.”
Good Example
“Prepared weekly sales performance reports for regional leadership, highlighting pipeline movement, conversion trends, and account risks.”
Outcome shows why the work mattered.
Weak Example
“Updated internal procedures.”
Good Example
“Rewrote internal scheduling procedures to reduce missed shift updates and improve communication between supervisors and front line staff.”
Complexity shows judgement and maturity.
Weak Example
“Handled employee questions.”
Good Example
“Responded to employee questions on payroll, benefits, scheduling, and policy updates, escalating sensitive issues while maintaining confidentiality.”
Tools show practical capability, especially in roles where systems matter.
Weak Example
“Tracked project progress.”
Good Example
“Tracked project milestones in Asana and Excel, keeping timelines visible for operations, sales, and client service teams.”
This is where good resume writing becomes less about fancy wording and more about honest precision. You are not trying to make small work sound inflated. You are trying to make real work understandable.
Not all evidence carries the same weight. The best evidence is tied to the employer’s actual hiring problem.
This is where many candidates miss the point. They include achievements they are proud of, but not always achievements that matter for the role they want next.
A hiring manager does not evaluate your resume in isolation. They evaluate it against a business need.
For example, if the role requires process improvement, evidence about reducing manual work, improving accuracy, or creating better workflows matters.
If the role requires client management, evidence about retention, satisfaction, account growth, conflict resolution, or executive communication matters.
If the role requires leadership, evidence about coaching, team performance, delegation, hiring, scheduling, conflict management, or improving team consistency matters.
If the role requires operations, evidence about volume, timelines, compliance, coordination, cost control, vendor management, or service delivery matters.
If the role requires administration, evidence about organization, accuracy, calendars, documentation, stakeholder support, systems, and follow through matters.
This is why the same experience may need to be framed differently for different roles. You are not inventing a new career. You are choosing the evidence that best matches the job.
A good resume is not a storage unit for everything you have ever done. It is a business case for why you should be interviewed.
Employers often use vague language in job postings. Candidates then repeat the vague language back in resumes. That creates a loop of professional sounding emptiness.
Here is what some common employer phrases often mean in practice.
When an employer says fast paced environment, they may mean the team is under resourced, priorities change quickly, and they need someone who can stay organized without constant direction.
Your resume evidence should show workload, prioritization, deadlines, and calm execution.
When an employer says strong communication skills, they may mean the role involves explaining things clearly to people who are busy, frustrated, senior, technical, non technical, or not paying attention.
Your resume evidence should show audience, message type, communication channel, and outcome.
When an employer says attention to detail, they may mean mistakes are expensive, visible, embarrassing, regulated, or annoying enough that the manager is tired of fixing them.
Your resume evidence should show accuracy, quality checks, documentation, compliance, or error reduction.
When an employer says team player, they may mean they want someone who can collaborate without creating drama, withholding information, or treating every minor disagreement like a courtroom event.
Your resume evidence should show cross functional work, handoffs, support, shared goals, and stakeholder trust.
When an employer says self starter, they may mean they do not have time to babysit the role.
Your resume evidence should show ownership, initiative, problem solving, and work completed without excessive prompting.
This is why evidence based resumes feel more mature. They do not just say “excellent communication skills.” They show what communication looked like in a real workplace.
Evidence helps only when it is clear, relevant, and believable. Poor evidence can make a resume feel inflated or confusing.
A bullet like “Increased productivity by 75 percent” sounds impressive, but it raises questions if there is no explanation. Productivity of what? Measured how? Over what period? Compared to what baseline?
Numbers need context to feel credible.
Better
“Reduced weekly reporting time from four hours to one hour by rebuilding the tracking spreadsheet and automating recurring calculations.”
That is believable because the mechanism is clear.
Not every responsibility deserves resume space. Candidates often give equal weight to minor tasks and major contributions. That makes the resume feel unfocused.
A recruiter should not have to dig through routine duties to find the strongest evidence.
There is nothing wrong with normal work. Most companies run on normal work done well. The problem is when candidates try to make everything sound revolutionary.
“Transformed organizational excellence through strategic document handling” is not better than “Maintained accurate client documentation and reduced missing file issues through weekly audits.”
The second one is clearer, more credible, and much less exhausting.
Your resume is not being read by someone who knows your internal company structure. Avoid internal acronyms, project names, and vague department references unless you explain them.
A bullet that makes sense only to your former employer is not strong evidence. It is workplace archaeology.
Sometimes the evidence is there, but the wording buries it.
Weak Example
“Helped with improving reporting process.”
Good Example
“Rebuilt the monthly reporting tracker to remove duplicate entries, improve data visibility, and give managers faster access to performance updates.”
The second version does not exaggerate. It simply explains the work properly.
A strong resume bullet should usually include enough detail to prove value without turning into a paragraph.
Most effective resume bullets include two or three of the following:
Action
Scope
Tool
Context
Stakeholder
Outcome
Metric
Business reason
For example:
“Coordinated interview scheduling for high volume retail hiring across Ontario, managing candidate communication, hiring manager calendars, and weekly status updates.”
This bullet includes action, context, geography, volume implication, stakeholders, and tasks. It does not include a hard metric, but it still gives useful evidence.
Another example:
“Improved monthly reconciliation accuracy by introducing a checklist process that helped identify missing entries before finance review.”
This bullet includes action, method, outcome, and business function.
Do not overload every bullet. If every sentence is packed with metrics, tools, stakeholders, and outcomes, the resume becomes hard to read. Evidence should create clarity, not clutter.
A good rule is this: after reading each bullet, the recruiter should understand something specific about your capability that was not obvious from your job title alone.
This is one of the most common concerns candidates have, and it is a fair one.
Not every job gives you clean performance data. Some companies do not measure properly. Some managers never share results. Some roles are confidential. Some work is supportive and indirect. Some achievements are obvious internally but hard to prove externally.
That does not mean your resume has to be vague.
If you do not have metrics, use evidence from scope, complexity, frequency, stakeholders, tools, or before and after context.
Instead of saying:
Weak Example
“Supported office administration.”
Say:
Good Example
“Supported daily office administration for a 35 person team, including calendar coordination, vendor communication, supply tracking, document preparation, and front desk coverage.”
No dramatic metric. Still much stronger.
Instead of saying:
Weak Example
“Worked on process improvements.”
Say:
Good Example
“Identified recurring delays in approval handoffs and created a shared tracking sheet that helped managers see pending items more clearly.”
Again, no percentage needed. The evidence is in the problem, action, and improvement.
For many Canadian job seekers, especially newcomers, early career professionals, career changers, administrative professionals, and support roles, this matters. You may not have direct ownership of revenue or strategy. But you still have evidence. You need to describe the real shape of your work.
Evidence is not only numbers. Evidence is specificity.
A resume needs to work for both applicant tracking systems and human readers.
The ATS may parse your job titles, dates, skills, employers, and keywords. Recruiters may search within the system for specific terms. But after that, a human still needs to decide whether the resume is worth attention.
This is where evidence based writing is powerful. It naturally includes relevant keywords while also explaining how you used them.
For example, instead of listing Salesforce in a skills section and hoping someone cares, a stronger bullet might say:
Good Example
“Updated Salesforce opportunity records, tracked pipeline changes, and prepared weekly account activity summaries for the sales leadership team.”
That sentence includes the tool, the task, the business context, and the stakeholder. It works better than keyword dumping because it gives the keyword meaning.
The same applies to terms like project coordination, stakeholder management, reconciliation, onboarding, compliance, reporting, vendor management, payroll, customer service, data analysis, scheduling, CRM, ERP, or inventory control.
Keywords help you get found. Evidence helps you get chosen.
A resume that is optimized only for systems can still fail with people. A resume written only for people can miss important keyword alignment. The best resumes do both without sounding like a robot swallowed a job posting.
Before sending your resume, read each bullet and ask:
Does this prove something, or only describe a duty?
Would another candidate with the same job title be able to copy this sentence easily?
Does this show scale, outcome, complexity, or context?
Is the most impressive information buried too late in the sentence?
Is this relevant to the job I want next?
Does the bullet sound believable?
Does this help the hiring manager picture me doing the work?
If a bullet could be copied into almost anyone’s resume, it is probably too generic.
For example:
“Worked with team members to complete tasks.”
This says almost nothing. It is technically workplace activity, but so is opening Outlook with a sigh.
A stronger version depends on the role:
Good Example
“Coordinated daily task updates between warehouse, customer service, and delivery teams to reduce missed order handoffs.”
Now the reader understands the teams, coordination need, and operational value.
That is the level of clarity you want.
When candidates feel stuck, I usually suggest building bullets from four ingredients:
Work performed
What did you actually do?
Context
Where, for whom, with what tools, or under what conditions?
Value
Why did it matter?
Proof
What changed, improved, increased, decreased, moved faster, became clearer, became more accurate, or became easier?
Here are a few examples across different roles.
Administrative Assistant
Weak Example
“Responsible for scheduling meetings and preparing documents.”
Good Example
“Managed calendar coordination, meeting materials, and document preparation for three senior leaders, helping keep internal deadlines and client follow ups organized.”
Customer Service Representative
Weak Example
“Answered customer calls and emails.”
Good Example
“Handled high volume customer inquiries by phone and email, resolving billing, delivery, and account questions while documenting issues accurately in the CRM.”
Project Coordinator
Weak Example
“Assisted with project management tasks.”
Good Example
“Maintained project trackers, meeting notes, risk logs, and stakeholder updates for multiple client implementation projects, improving visibility on deadlines and pending decisions.”
HR Coordinator
Weak Example
“Supported recruitment and onboarding.”
Good Example
“Coordinated interview scheduling, candidate communication, reference checks, and onboarding documents for hourly and corporate roles across multiple Canadian locations.”
Sales Representative
Weak Example
“Responsible for generating leads and managing accounts.”
Good Example
“Prospected new business accounts, maintained CRM follow up activity, and grew repeat opportunities by building stronger relationships with small business clients.”
Notice that none of these examples are trying too hard. They are not stuffed with buzzwords. They simply make the work more visible.
That is what a resume should do.
A strong resume does not just help you get interviews. It also shapes the interview.
When your resume includes evidence, the interviewer has better material to ask about. Instead of vague questions like “Tell me about your responsibilities,” they can ask:
“How did you improve that process?”
“What made that project difficult?”
“How did you manage that volume?”
“What tools did you use?”
“What was the impact on the team?”
That gives you a better chance to speak about real examples instead of scrambling for a story on the spot.
Evidence also makes your answers more believable because the resume has already introduced the context. You are not suddenly claiming impact in the interview with no setup. The resume and interview support each other.
This is especially useful in Canadian hiring processes, where interviews often involve behavioural questions, practical examples, team fit discussions, and hiring manager concerns about whether the candidate can adapt to the company’s environment.
If your resume only lists responsibilities, the interview starts from a weaker place. You have to build credibility from scratch. If your resume already shows evidence, the interview can go deeper faster.
Responsibilities are not useless. They belong on a resume when they clarify your role, match the target job, or explain necessary experience.
The mistake is relying on them alone.
Some responsibilities are important because they show required exposure. For example, if a job requires payroll processing, vendor coordination, financial reporting, case management, client onboarding, inventory control, or technical support, your resume should clearly show that you have done those things.
But whenever possible, attach evidence.
Instead of:
“Responsible for payroll processing.”
Use:
“Processed biweekly payroll inputs for hourly employees, reviewing timesheets, resolving discrepancies, and coordinating corrections before submission deadlines.”
This still communicates the responsibility, but it adds process, accuracy, and time sensitivity.
A good resume balances responsibilities and evidence. Responsibilities tell the reader what lane you were in. Evidence shows how well you drove in that lane.
Evidence based resumes stand out because they respect how hiring actually works.
Recruiters are busy. Hiring managers are cautious. Employers are imperfect. Job postings are often vague. Applicant pools are noisy. Many candidates look similar on paper. Internal priorities shift. Screening is not always as organized as candidates imagine.
In that reality, clarity wins.
A resume with evidence makes the decision easier. It reduces doubt. It shows the candidate understands their own value. It gives the recruiter stronger reasons to shortlist them. It gives the hiring manager more confidence that the person can do the work.
The strongest resumes do not scream. They prove.
They show the reader:
I understand the work
I have done relevant things
I can explain my contribution clearly
I know what mattered in my role
I can connect my experience to your hiring need
That is the point. Your resume is not a biography. It is not a job description. It is not a list of everything you were paid to touch.
It is evidence for an interview decision.
Written by Simar Malhi, a recruiter and headhunter with international recruitment experience. I write about CVs, job applications, hiring decisions, and the reality behind recruitment processes. My goal is to help candidates understand more honestly how employers, recruiters, and hiring managers actually select candidates.
Upload Resume
Import from Linkedin