The group is hiring a research assistant. More than a dozen résumés came in—nicely formatted, well worded, and all seemingly right. But “seemingly right” and “actually right” are two different things: whether a school name is written in full or abbreviated, whether an employer is the headquarters or a research group, whether project experience says “participated” or “led”—the differences behind these words cannot be gleaned just by reading a résumé. Discovering only before sending an offer that some experience does not match costs far more in back-and-forth than the verification itself.
This article breaks down how to use the MuchSci talent profile for résumé verification: compare the schools, majors, and employment experience written on the résumé item by item against public information, turning “seemingly right” into “verifiable.” Let’s put the conclusion up front: what can be verified are factual fields; what cannot be verified are competence and fit—the latter can only be assessed through interviews and probation, and the profile does not make, nor should it make, hiring recommendations.
01 Verification in Four Steps
▲ Figure 1 | From breaking out fields to handing off to the interview, four steps establish the verification process
Step 1: Break out fields. Take the schools, majors, employers, and project names on the résumé and pull them out separately; do not let them stay buried in narrative text. Step 2: Compare item by item. Check each item against public information separately, rather than relying on an overall impression that “it reads as if it’s true”—overall impressions are exactly what a polished résumé is best at creating. Step 3: Flag items that cannot be found. If a period of employment has no corresponding record in public information, mark it and leave it blank; do not fill it in with a similar record, and do not rush to conclude that “there is a problem”: it may be that the data source does not cover it, or you may need to ask the person for additional supporting documents.
The fourth step is to hand the rest to the interview.The first three steps address whether experience is factual, while competence, ability to work with others, and whether someone can fit into the group’s way of working are questions public information simply does not answer; forcing verification there will only produce a pile of false conclusions.
02 What Can Be Verified and What Cannot
▲ Figure 2 | The left column is facts that can be checked item by item; the right column is what verification does not cover
Three types can be verified: education history, employer, and public projects. Schools and majors can be checked against public records; employers and job titles can be verified; public projects someone participated in have evidence to support them. Three types cannot be verified: performance in school, the work actually undertaken, and the share of individual contribution. On the same project, the gap between “participated” and “core contributor” cannot be seen from the résumé, nor from public records.
Writing this “cannot verify” column down plainly is an easily skipped but important step in the verification process. It reminds those conducting interviews that what this interview needs to fill in is precisely the part the profile cannot manage. Passing verification does not mean the candidate is suitable, and a verification doubt does not necessarily mean dishonesty—it may simply be that public information does not cover it. Do not overinterpret in either direction.
03 Which Types of Profile Records Do Résumé Fields Map To?
▲ Figure 3 | When résumé fields are broken into four types of profile structures, gaps surface on their own
Identity and current position correspond to basic information: name format, current employer, and research field. Education history corresponds to education: time, school, major, and result, with the four columns matching one to one. Employment and achievements correspond to employment history and research outputs: employer and title, project experience, and authorship records. After breaking them out, every sentence on the résumé falls into a specific box, and which box is empty or does not match is visible at a glance.
This field structure is exactly the skeleton of the MuchSci talent profile: it includes only records related to national-level projects and requires an exact match of name, institution, and history with public information before inclusion; anything that does not match is marked “pending verification.” The advantage of using it for verification is that the reference system itself comes with a validation mechanism—what you are comparing against is not another unverified document, but a profile that has already been screened.
04 Feature Interface: Check Side by Side
▲ Figure 4 | What can be checked and what can only be tested are listed on two sides; write the interview outline according to the right column
The three questions in the left column—whether the experience holds up, whether the timeline is continuous, and whether the project is real—are handed to the profile for checking; the three questions in the right column—competence and proficiency, teamwork, and long-term commitment—are written into the interview outline. The two lists are not mixed, so verification and interviews each have their own brief.
The profile in the interface looks like this:
▲ Figure 5 | Employment history lists institution and title by date; research outputs are divided into academic contributions and led projects
Employment history is presented in a table, with time, institution, and title listed item by item, which is ideal for side-by-side comparison with the corresponding section of the résumé; where the years do not connect, that is exactly where you need to follow up with the candidate. The research section is divided into academic contributions and led projects, making it possible to check whether the projects listed on the résumé are consistent with public records.
05 Boundaries
① This article discusses feature mechanisms and ways to use them; it does not constitute a guarantee of results. Verification results depend on the availability of public information; not finding something does not mean there is a problem.
② The profile does not produce hiring recommendations. Verification covers only factual fields; competence, fit, and actual work performance can only be judged through interviews and probation; hiring decisions are the responsibility of the user. ③ Only public information is used. No personal privacy data is involved, and no evaluation is made of any individual; when used for formal purposes such as recruitment, the current regulations and procedures of the relevant institution shall prevail.