Faculty rank
- Regents Professor of ChemistryDistinguished Professortenure-track
- Smith Family Endowed ChairProfessortenure-track
- Research Assistant Professornon-tenure-track
The engine behind every Cevian Labs product, connected to your own system through a secure API. Each CV comes back as one structured record, classified on academic vocabularies and checked against the public record.
Give recruiters and search committees a comparable record for every academic applicant, instead of a stack of CVs in different formats.
Populate faculty profiles with publications, grants, and honors drawn from the CVs faculty already keep, each entry checked against its source.
Connect the engine to your faculty-reporting system: faculty upload their current CV, and the engine identifies their recent activities automatically, with consistent records across departments and campuses.
The engine reads an academic CV in any layout and discipline, from any country, and returns one structured record of that person's scholarly career. We tailor which CV data it extracts, and which of that data it checks against the public record, to what your platform needs.
What one partner might choose to extract and verify
| Data class | Extract | Verify |
|---|
The engine doesn't simply lift strings off the page. It classifies every entry onto closed academic vocabularies, so your platform can filter, count, and compare records across institutions, fields, and countries without hand-coding.
A few examples of what it standardizes and classifies.
Publications are matched against Crossref and other authoritative bibliographic and library databases; grants against NSF, NIH, USASpending, UKRI, and the EU's CORDIS; and honors against the Cevian Labs Academic Honors Registry of more than 9,000 honors from more than 4,000 organizations.
Peter Liebman, from our sample pool, pseudonymised
Because every entry says which authority confirmed it, or that none did, your platform can show what an independent source corroborates, compute that share for each CV, and filter, weight, or audit on it. Checks are tuned for precision: an entry no source confirms keeps the CV's own content, is labeled unconfirmed, and is never matched to a guess.
Classification fields draw on closed vocabularies, so they filter and aggregate directly. Institutions, publications, grants, and people carry persistent public identifiers (ROR IDs, DOIs, funders' award numbers, and ORCID iDs), so records join cleanly to the institutional, bibliometric, funding, and researcher-profile systems you already run.
A few of the fields you can filter on directly
Peter Liebman, from our sample pool, pseudonymised
Tell us about your platform, your users, and the academic data they need.
We agree which CV data the engine extracts and verifies for you, and how records reach your system.
Your platform connects to the engine through a secure API, under a license that fits your product.
Click the slides or use the arrow keys to step through at your own pace. Open full screen · Full walkthrough
| Task | General-purpose chatbot (ChatGPT, Claude) | CVParsa |
|---|---|---|
| Read one CV and summarize it | Does this well | Does this well |
| Apply the same fields and vocabulary to every CV in a pool of hundreds | Output varies between runs | One schema, fixed academic vocabularies |
| Know that a fellowship title can be a postdoc, and that a CAREER award is both an honor and a grant | Inconsistently | Applied the same way to every CV |
| Count publications | Depends on how the question is asked | Publications counted by type; preprints and patents kept separate |
| Confirm each record against Crossref, NSF, NIH, and Cevian Labs databases | Not systematically, and prone to inventing citations it cannot find | Every record states which authority confirmed it, or that none did |
| Handle confidential applicant files | Consumer accounts raise data-governance questions | Encrypted, never used to train AI models, originals deleted within 30 days |
Yes. Licensed partners connect to the CVParsa engine through a secure API. Access and delivery are agreed as part of each license; there is no public, self-serve API.
For your engineers. A REST API over HTTPS. Your system authenticates with credentials issued for your license, submits CVs as PDF files, and is notified when each structured record is ready to collect as JSON. No CV data travels unencrypted, and nothing is retained beyond the terms of your license.
Yes. We tailor which CV data the engine extracts, and which of that data is checked against the public record, to what your platform needs.
Up to nine data classes: person and standing, education and training, employment, advising, publications, research funding, honors, research interests, and institutional identity. Classification fields use closed vocabularies, and institutions, publications, and people carry persistent public identifiers.
Academic CVs in any layout and discipline, from any country. The engine understands CVs in most major languages and recognizes international institutions and venues; records are returned in English.
That no independent source confirmed the entry. The CV's own content is kept and plainly labeled. Unconfirmed is not the same as false: many genuine achievements are not in any public database.
No. Verification is a data-quality check: it shows which entries an independent source corroborates. It is not a finding that anything on a CV is wrong, and it should not be used as one.
Yes. CVParsa for Search Committees and CVPaaS are built on the same engine. Integrations make it available inside your own platform.
Files are encrypted with AES-256 at rest and TLS in transit, and are never used to train third-party AI models. Retention and data handling are agreed in each license.
Licensing is scoped to each partner. Write to licenses@cevianlabs.io.