Technology

Canadian Resume Example for Software Developers

Recruiters spend seconds on a developer resume. Give them your stack, what you shipped and the difference it made, in a clean layout an applicant tracking system can read.

Build my resume free or browse all resume examples.

Updated

What does a software developer resume need in Canada?

A software developer resume for a Canadian employer should fit on 1 to 2 pages. Open with a short summary, then put your core stack near the top, along with a GitHub or portfolio link. Follow with your work experience, newest first, with numbers wherever you have them. Use the job posting's own words for your skills, and list the ones it asks for first. Leave out your photo, date of birth, marital status and SIN.

A sample software developer resume

A sample software developer resume in Canadian format. The person and employers are made up.

Emily Tran
Toronto, ON · (416) 555-0182 · emily.tran@email.com
Go, TypeScript, React, Kafka, AWS

Summary

Software developer with 6 years building web platforms in TypeScript, React and Node.js, most recently at a Toronto fintech serving 400,000 users. Led the move from a monolith to services on AWS, cut deployment time from 2 hours to 12 minutes with CI/CD, and mentors 3 junior developers.

Experience

Senior Software Developer, Fernleaf Financial, Toronto, ON, Mar 2023 to Present

Software Developer, Northpoint Logistics, Waterloo, ON, Jun 2020 to Feb 2023

Certifications

Education

Bachelor of Computer Science, 2020

How to write a software developer resume in Canada

The Canadian tech market is competitive, from Toronto and Waterloo to Vancouver, Montreal and Calgary, and a developer resume is often screened twice: first by an applicant tracking system, then by a recruiter or engineering manager in under a minute. Both are looking for the same thing. Does your stack match the posting, and have you shipped real work? Put your main languages and frameworks in a short skills section near the top, and match the words in the job posting where they are true for you.

Your bullets should describe what you built and what changed because of it. "Worked on the backend" says little. "Rebuilt the checkout API in Go, cutting p95 latency from 900 ms to 180 ms" says a lot. Give the scale (users, requests, data size), your role in the team and the tools you used. For new graduates, co-op terms, capstone projects, hackathons and open source contributions count, and a GitHub or portfolio link next to your contact details lets people see the code.

A Canadian detail worth knowing: engineer is a protected title in Canadian provinces, tied to a professional licence such as a P.Eng. Many employers still use software engineer as a job title, and you can list the title your employer gave you, but in your own headline or summary, software developer is the safer choice unless you are licensed. Leave out a photo, age and marital status, as Canadian employers expect.

The layout rules that apply to every job are in our Canadian resume format guide. If you would rather start from a blank page that already follows them, use a free Canadian resume template.

Software Developer professional summary examples

Your summary is the first thing a recruiter reads. Pick the one closest to your own background and change every detail so it describes you.

Skills to put on a software developer resume

List the hard skills first, because they are what screening software and hiring managers search for. Keep soft skills to the ones a bullet point further down can back up.

Hard skills

Soft skills

Words to mirror from the job posting

Employers and their screening software look for the words they used in the ad. When one of these appears in a posting and it is true for you, use the same wording on your resume.

Work experience bullet examples

Each one starts with what you did and ends with a result. Keep the shape and put your own numbers in.

  1. Rebuilt the checkout API in Go, cutting p95 latency from 900 ms to 180 ms for 400,000 users
  2. Set up CI/CD with GitHub Actions and Docker, cutting deployment time from 2 hours to 12 minutes
  3. Built a React component library used across 4 products, cutting new feature UI time by about a third
  4. Designed a Kafka event pipeline that handles 2 million shipment events a day with 99.95% uptime
  5. Raised backend test coverage from 45% to 85%, and production incidents fell by half over the next two quarters
  6. Led the move from a monolith to services on AWS ECS without any customer-facing downtime
  7. Mentored 3 junior developers and 2 co-op students through code reviews and pairing

Certifications and licences that help

Write each one out in full with the issuing body and the date. An employer should never have to guess what an acronym means or whether it has expired.

What recruiters wish you knew

Put the stack where the ATS will find it

A short skills section with your languages, frameworks and cloud platforms helps both the applicant tracking system and a recruiter skimming for a match.

Write impact, not tasks

Each bullet should say what you built and what changed: speed, cost, users, reliability. Numbers make it believable, and they give an interviewer something to ask about.

Link to your work

A GitHub, portfolio or live project link next to your contact details lets a hiring manager see real code. Pin your best two or three repositories.

The section order for a software developer resume

Top to bottom, in the order a hiring manager in this field wants to read it.

  1. Contact details. City, phone, email, LinkedIn, and GitHub or a portfolio.
  2. Professional summary. Your focus, years of experience and main stack.
  3. Technical skills. Grouped into languages, frameworks, cloud and databases.
  4. Work experience. What you built, what it changed and the numbers behind it.
  5. Projects. Two or three with links, most useful early in your career.
  6. Education and certifications. Degree, with a WES assessment if earned abroad, plus cloud or security certifications.

What recruiters check first

Your stack, what you built with it, and a link to GitHub or a portfolio. Where to put it: Skills and a projects section.

Common mistakes on software developer resumes

These come up again and again, and each one is quick to fix.

Listing every tool you have touched

Thirty technologies in a row make it hard to see what you are good at. Group them, lead with the stack the posting asks for, and drop anything you could not talk about in an interview.

Hiding your part in team work

"We migrated to AWS" leaves your role unclear. Say what you did: designed the pipeline, led the migration, wrote the tests.

Calling yourself an engineer in your headline

Engineer is a protected title in Canada. Keep the title your employer gave you in your work history, and use developer in your own summary unless you are licensed.

Before you send it

Six quick checks. Each takes less than a minute.

Software Developer resume FAQ

What should a software developer resume include in Canada?

Contact details with a GitHub or portfolio link, a short summary, a skills section with your stack, work experience with impact-focused bullets, projects if you are early in your career, and education. Leave out a photo, age and marital status.

Can I call myself a software engineer in Canada?

Engineer is a protected title tied to a professional licence in Canadian provinces. You can list the job title your employer gave you, but in your own headline or summary, software developer is the safer choice unless you hold a P.Eng or equivalent.

Should a software developer resume be one or two pages?

One page for new graduates and developers with a few years of experience. Two pages is fine for senior developers with a long record of relevant work, as long as every line earns its place.

What skills should a software developer put on a resume?

Your programming languages, frameworks, databases, cloud platforms, CI/CD and testing tools, matched to the posting. For soft skills, choose problem solving, clear written communication, ownership and collaboration, and show them through your bullets.

How do I write a developer resume with no Canadian experience?

Describe your international work with clear numbers and well-known technologies, name the products or clients in general terms if they are not known here, and add a credential assessment for your degree. Canadian projects, open source contributions or a co-op term help close the gap.

Should I include personal projects on my resume?

Yes, especially early in your career or when changing stacks. Give each project a line on what it does, the technologies used and one result, such as users, stars or a hackathon win, with a link to the code.

Related resume examples

Further reading

Keep building your Canadian resume

Turn this example into your own resume.

CVMaple lays out your resume in Canadian format, helps you word your bullet points for the role, and checks it before you download. The builder is free, and so is your first PDF.

Build my resume free or check a resume I already have. No credit card needed to start.