Your CV in, with every gap left for you
CV import turns your résumé into a structured set of work-experience records in one go. The parser is told never to guess, so anything your CV leaves unclear comes back blank and ringed amber, and every record stays editable afterwards.
- PDF, Word (.docx) or plain text, including the CBA Pro template as you filled it in
- Fields the parser flagged or left blank are ringed amber
- A re-upload skips roles you already have
Resume.pdf · 3 roles found
Nothing saved yetFrom the work-experience screen, each record waits for you to save or skip it, and a re-upload skips 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 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 parser proposes one record per role and leaves a field blank rather than guess it. During onboarding, records it could fill completely are saved as they are read, and any record with a missing fact, such as an end year or an employer's name, stops for you to complete. Import a CV later from the work-experience screen and every proposed record opens in the same editable form the manual path uses, for you to save or skip.
The prompt behind it is explicit: leave gaps rather than fill them, never merge two employers into one record, never split one role into a record per project, and take the job title exactly as written, so an intern stays an intern. Uploaded files are stored in a private bucket tied to your account.
From résumé to evidence base
- 1
Format it with the template
Download the CBA Pro CV template and lay out one block per role: employer, city, dates and job title on one header line, with bullets underneath for what you did and on which project. A CV in that shape parses with almost no gaps to fill.
- 2
Upload
PDF, Word (.docx) or plain text, up to 10 MB. The filled-in template goes straight back up as a Word file, with no conversion needed, and it is stored in a private bucket tied to your account.
- 3
Check what it found
Anything the parser could not read is ringed amber for you to fill. From the work-experience screen you save or skip each card, and every record stays editable in your list either way.
- 4
Top it up by hand
Anything your CV understates, like the project you led that got one bullet, you add by hand in your own words. The duties text is what the competency matcher reads.
Why careful parsing is the feature
A second read for messy CVs
If a first read comes back thin, CBA Pro rewrites the CV into the template's layout behind the scenes, reads it again, and keeps whichever read found more roles.
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 takes the job title exactly as written on your CV and is barred from promoting a role. What your CV says is what the record says.
Re-uploading is safe
A duplicate guard skips roles you already have, so an updated CV adds the new role rather than doubling your history.
Best practices for documenting engineering experience
A smooth CBA starts with how well your experience was recorded before you began 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 at each employer; keep the header line (employer, city, dates, job title) intact rather than pushing dates into a sidebar; put what you did, and on which project, in bullets underneath; write what you actually did rather than what the team delivered; and expect education and awards to be left out 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 a parser. That is why the template is a plain, single-column Word document, and why CBA Pro, when a first read comes back thin, rewrites the CV into that layout and reads it again.
What applicants say
Farbod Asadi, a civil engineering graduate finishing his P.Eng application, describes writing his CBA competencies with CBA Pro after a colleague referred him to CertNova.
40+ CBAs reviewed since June 2025. No rejection reported back to us.(CertNova's human review service, not CBA Pro)How it's counted
“It made it a lot easier compared to how my wife did it, because I know how hard it could be.”
From CertNova's Google reviews
I had a great experience using CertNova throughout my P.Eng application process. Their software made the competency-based assessment much easier to navigate and helped me organize and present my engineering experience in a clear and structured way. What really stood out, though, was the support from Reza and Hossein. They were knowledgeable, responsive, and genuinely invested in helping me through the process. Their guidance helped me better understand what was expected and gave me much more confidence in preparing my submission. I would highly recommend CertNova to anyone going through the P.Eng licensing process in Canada. The combination of a well-designed platform and excellent personal support made a complicated process feel much more manageable.
CBA Pro helped me organize my experience against each competency, keep track of what I'd covered, and tighten my writing so it focused on my own role and decisions. It saved me a lot of time and stress compared to working from scattered notes of experiences. I'd recommend it to anyone going through the CBA process.
Reviews are quoted as written on CertNova's Google profile. Nobody can promise approval; your regulator decides.
Next in CBA Pro
The right project for each competency
Three candidate experiences per competency, each rated honestly for closeness. 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 use no credits.
Learn moreCV import: questions applicants ask
It is stored in a private bucket: the file's path starts with your user id, storage rules let only your account reach it, and the server checks ownership again before reading it for a parse. To read it, CBA Pro sends the CV to the AI service that parses it. The file stays in your account after the parse.
PDF, Word (.docx) or plain text, up to 10 MB. The CV template is a Word document, so you can fill it in and upload it as it is. Older .doc files are not accepted; save them as .docx first.
Fix it in the record, or delete the record and add the role by hand. Every record stays editable in your work-experience list, and when you import from the work-experience screen you can skip a card before it is ever saved.
No. Adding work experiences by hand is always available, and the CV step in onboarding can be skipped. Import is a shortcut for people with a well-structured CV already on their desktop.
In short
CBA Pro's CV import parses a P.Eng applicant's résumé (PDF, Word .docx or plain text) into proposed work-experience records, one per role. The parser is instructed never to guess missing facts, merge employers or promote job titles, and blank or uncertain fields are ringed amber for the applicant to fill. In onboarding, complete records are saved as they are read and records with a missing fact stop for the applicant; imports from the work-experience screen open every record for the applicant to save or skip. A weak first read triggers a second read of the CV rewritten into the template layout, a duplicate guard stops a re-upload creating duplicate roles, and 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.