The Engineering CV Rewrite: Getting South African Engineering CVs Read in Canada

Five pages. That’s a fairly ordinary length for a South African engineering CV with a decade of project history on it — and it’s roughly three pages longer than a Canadian recruiter will read before deciding the document, and the candidate, needs too much work.

Canadian résumé convention runs one to two pages, with two considered acceptable only once you’re past ten years’ experience. That’s not a style preference. It changes what you’re forced to cut, and cutting the wrong things is where most South African engineering mistakes in Canada actually happen.

What the two-page limit forces out

The instinct is to shrink the font. Don’t. What actually needs to go is the ID number, photo, date of birth and marital status — standard on an SA CV, never included on a Canadian one, and their presence reads as unfamiliarity with the market rather than thoroughness. Drop the reference list too; Canadian employers ask for one to three references, usually former direct supervisors, near the end of the process rather than upfront on the document.

That alone recovers most of the space. What’s left should be the last decade of relevant project work, described in outcomes rather than duties — Canadian résumés read as achievement statements, not job descriptions.

Framing project metrics so a stranger can use them

A bullet point that says “managed R45 million infrastructure upgrade” asks a Canadian hiring manager to do currency conversion in their head, mid-skim, with no context for what that budget actually represents. Give the CAD-equivalent figure instead, note plainly that it’s an approximate conversion, and let the scale speak for itself — a hiring manager doesn’t need the exact rand number, they need to know whether you’ve run a small project or a large one.

The same logic applies to the employer’s name. If it isn’t a global brand, say what it is in a short descriptor: a JSE-listed company, a member firm of an international engineering network, a municipal or provincial infrastructure authority. Without that line, a senior role at a serious South African firm reads as a junior role at a company nobody’s heard of, because the reader has no way to judge size or standing on the name alone.

The Pr.Eng question

Whether to list Pr.Eng at all is a real question, because it does not function as a Canadian licence. Our research is clear on the underlying reason: Engineers Canada has no mutual recognition agreement with South Africa’s regulator, so your professional registration carries no weight on its own with a provincial body like PEO, APEGA or EGBC — only your academic qualification does, via the Washington Accord, and even that gets assessed rather than waved through.

List it anyway, the same way you’d list your degree: as what it is, bracketed for clarity — “Pr.Eng (South Africa) — registration does not transfer; Canadian P.Eng licensing applied for separately.” It tells a Canadian employer you already met a professional bar somewhere, without implying you’re licensed to practise in their province. Whether to pursue P.Eng licensing itself is a longer process — the 48-month competency assessment and the national practice exam are worth their own read before you start.

Codes, standards and the honest limit here

It helps to be specific: naming codes and standards on a Canadian CV strengthens it, but which ones matter depends heavily on where you specialise, and that’s a level of detail our research doesn’t hold generically. Look up the standards your target employers actually cite in their own postings, rather than porting over SANS references that won’t mean anything to the reader.

None of this is about hiding your experience. It’s about translating fifteen years of South African infrastructure work into a document a stranger in Calgary can evaluate in ninety seconds, because that’s genuinely all the first read gets.

If you’re still assembling the credential side of this, our free guides cover how an ECA fits alongside a rewritten résumé — worth doing both at once rather than in sequence.