Nothing is saved until you have read it
CV import turns your résumé into a structured pool of work-experience records in one pass — then makes you approve every single one before a row touches your account.
- Every proposal opens in the same form the manual flow uses
- Fields the parser flagged or left blank are ringed amber
- A re-uploaded CV cannot duplicate roles you already have
Resume.pdf · 3 roles found
Nothing saved yetNothing is saved until you say so — and a re-uploaded CV can't duplicate a role you already have.
The honest version of CV parsing
Most CV parsers optimise for the demo: upload, watch rows appear, move on. That is exactly the wrong behaviour for a regulatory submission, where a quietly wrong employer name or an upgraded job title becomes a problem you signed your name to.
CBA Pro's parse route persists nothing. It reads your CV and proposes records; each proposal opens in the same editable form the manual path uses, with anything the parser was unsure about — a missing end date, an ambiguous employer, an unclear project name — ringed amber. You save it or you skip it. Every saved row has been read by a human.
The prompt behind it is instructed to leave gaps rather than fill them: never merge two employers into one record, never split one role across two, and never upgrade 'Intern' to 'Engineer'. Uploaded files land in a private, owner-scoped bucket.
From résumé to evidence base
- 1
Format it with the template
Download the CBA Pro CV template, lay out one block per role — employer, city, dates and title on one header line, bullets underneath — and save as PDF. A CV in that shape parses with almost no gaps to fill.
- 2
Upload
PDF or plain text. The file goes to a private bucket keyed to your account; nobody else can read it.
- 3
Review every proposed record
One card per role, amber where the parser was unsure. Fix what needs fixing, then save or skip each card individually.
- 4
Top it up by hand
Anything your CV understates — the project you led that got one bullet — you add manually, in your own words. The duties text is what the competency matcher reads.
Why the review step is the feature
The parse route writes nothing
There is no 'import now, clean up later' state. Until you approve a card, it does not exist in your account, which means your evidence base can never quietly contain something you did not check.
Gaps stay gaps
A parser that guesses an end date is more dangerous than one that leaves it blank. Unknown fields come back empty and ringed, so you can see exactly what still needs your input.
Titles are never inflated
The prompt is explicitly barred from promoting a role. What your CV says is what the record says.
Re-uploading is safe
A duplicate guard auto-skips roles you already have, so an updated CV adds the new role rather than doubling your history.
Best practices for documenting engineering experience
The single biggest predictor of a smooth CBA is how well your experience was recorded before you started writing. Regulators want the employer, the location, the dates, the role you held and what you personally did — and they want it consistent across every competency you submit.
Five rules decide whether a CV parses cleanly, and they are worth following even if you never import it: one block per role per employer; keep the header line intact rather than pushing dates into a sidebar; one project name per record; write what you actually did rather than what the team delivered; and expect education and awards to be ignored rather than imported.
The formats that cause trouble are the designed ones — two-column layouts with dates in a margin, tables, graphics-heavy templates. They read beautifully to a recruiter and badly to any parser. That is why the template is a plain, single-column document, and why step four of the guide is 'save as PDF' in bold: the template ships as .docx, and the parser takes PDF or plain text.
Trusted by engineers across Canada
Sadegh Behboudian
“Using CBA Pro by CertNova Software Solutions helped me get my P.Eng. approved on the first attempt without any CBA rejections. What surprised me most was that the challenge wasn't my experience, it was how to present it properly. Having the right structure and guidance made the entire process much more manageable. Definitely saved me time and avoided the usual back-and-forth revisions.”
3 months ago
M. Ibrahim
“This was a wonderful experience. Hossein and Jenny were very helpful and prompt to reply to my emails and questions. Hossein got on a call with me before enrolling just to answer my questions. The review for my CBA questions was detailed, thorough with clear direction on what needs to be done to improve, which made it very easy for me to fix my answers. They gave me a time for looking into my CBA questions. They ended up delivering earlier than promised. Finally, they are very fairly priced. Definitely recommend their service for anyone looking to get someone to assess their CBA answers.”
1 week ago
Nahal Nobahar
“I recently used this service to review and strengthen my competency submissions for my P.Eng. application, and I had a very positive experience. Reza and the team provided detailed and thoughtful feedback on my existing drafts, helping me clearly understand what was missing and what needed improvement to meet the expectations of the P.Eng. assessment process. They didn't just correct wording, they guided me on how to better structure my responses, highlight my individual contributions, and align my examples with the required competencies. What I found especially valuable was their ability to point out gaps in my explanations and suggest exactly what kind of technical details, context, and outcomes should be included. Their feedback made it much easier to refine my responses and present my experience in a clear, concise, and professional way. Overall, this service was extremely helpful for improving both the quality and clarity of my submission. I would recommend it to anyone who is working toward their P.Eng. designation and wants expert guidance to strengthen their application.”
4 months ago
Next in CBA Pro
The right project for each competency
Three candidate experiences per competency, rated honestly for closeness — including the weak one. You choose the evidence; the AI only ranks it.
Learn morePlaceholders, not guesses
The one rule the whole product is built around: every fact the AI does not have becomes a bracket you fill — not a plausible invention you would have to defend.
Learn moreA five-step workspace per competency
Match your experience, close the gaps, draft, review, finalize. The screen always answers “what do I do next?” — and steps 1 and 2 cost nothing.
Learn moreCV import — questions applicants ask
Yes. Uploads go into a private storage bucket where the object key's first path segment is pinned to your user id, so the file is only reachable by your account. Service-role operations re-check ownership before touching anything.
PDF or plain text. The CV template itself is a Word document, so the guide's fourth step is to save it as PDF before uploading.
You fix it in the review card before saving, or skip the card entirely and add the role by hand. Nothing is written to your account until you approve it, so a bad parse costs you nothing but the time to skip past it.
No. Adding work experiences by hand is the primary path and always available. Import is a shortcut for people with a well-structured CV already sitting on their desktop.
In short
CBA Pro's CV import parses a P.Eng applicant's résumé (PDF or plain text) into proposed work-experience records. The parse route persists nothing: every proposal opens in an editable review card with parser-flagged or blank fields ringed amber, and the applicant saves or skips each record individually. The parser is instructed never to guess missing facts, merge employers, or upgrade job titles, and a duplicate guard prevents re-uploads creating duplicate roles. Uploads are stored in a private, owner-scoped bucket.
Run one full competency, free
Every step, on a real competency, with no card. Everything you write carries over the moment you upgrade.