The new release of our CV parser CVlizer is live. The focus lies on an improved recognition of training and career phases.

When you’ve developed a product like CVlizer and you want to improve the quality further, you can only do one thing: Optimize, optimize, optimize. But how does it work? What does it take? And especially, why does it take so long until a flaw in the extraction of a specific CV is corrected?

Those unfortunate souls who don’t use Microsoft Outlook as a mailclient might know about this: The infamous "winmail.dat"-attachments, which appear from time to time in our inbox and with which you can do nothing most of the time. But what is this really?

Reinhold, who was our Managing Director until 2016, entrusted it to the JoinVision team years ago: The actual trigger for the development of our CVlizer was the trainee of a company, which had advertised jobs on our existing online job portal for IT and technology. In 2008, she got into a conversation with him during a lecture by Reinhold at a university in Vienna.

More often than not application documents are a mingle-mangle of different document types (CV, certificates, cover letters, etc.) and formats. Microsoft Word, Open Office, PDF, scanned documents (PNG, JPG, GIF, etc.) – you name it!

At some point, most of our customers inevitably face an awkward situation: our CV-Parser CVlizer does not extract the information that is actually contained in a CV. The CV in question may look like any other – and yet: the result of its extraction process appears to be a patchwork of letters or it seems at least quite mysterious. How can that happen?