Docs Templates Template variables reference Owners and admins Updated 22 Oct 2026
Every field available to a template and the tag that reads it.
These are the variables a template can read. Text variables hold a single value. Variables marked as a list hold several values, so use them in a loop or with a filter such as {{ skills | join(", ") }}. A value Sourcemint does not have is empty text, or an empty list.
Variable Type Description first_nameText Given name last_nameText Family name main_roleText Primary job title total_experienceText Total experience, taken from the dated employment summaryText The profile summary
Variable Type Description emailText Email address mobileText Phone number linkedinText LinkedIn profile URL githubText GitHub profile URL other_urlsList Portfolio and other URLs physical_addressText The full address as one line detailed_address.addressText Street address detailed_address.cityText City detailed_address.postal_codeText Postal code detailed_address.countryText Country name
# Skills and technologiesVariable Type Description skillsList Skills and areas of expertise technologiesList All technologies, as one flat list category_techLists by category Technologies grouped by category, read as category_tech["language"] tech_listList of rows One row for each category that has technologies, with header (the category name) and content (the technologies, comma separated)
# Technology categoriescategory_tech always has these keys, each a list that is empty when nothing belongs to it:
Variable Contains category_tech["language"]Languages category_tech["framework"]Frameworks category_tech["database"]Databases category_tech["cloud_platform"]Cloud platforms category_tech["devtool"]Dev tools category_tech["testing"]Testing tools category_tech["os"]Operating systems category_tech["other"]Everything that fits no other category
If your organization has its own technology categories, their identifiers are keys of category_tech as well.
# Experienceexperience is a list. Loop over it with {% for exp in experience %} and read these fields from each entry. A job with several projects produces one entry per project, and independent projects follow the jobs.
Variable Type Description exp.companyText Employer exp.rolesList Roles held exp.projectText Project name exp.locationText Work location exp.fromText Start date exp.toText End date, or Current exp.responsibilitiesList Responsibilities exp.technologiesList Technologies used
# EducationLoop over education with {% for edu in education %}.
Variable Type Description edu.universityText Institution edu.facultyText Faculty or school edu.degreeText Degree edu.majorText Field of study edu.startText Start date edu.finishText End date
# Languages and certificationsVariable Type Description languagesList Loop with {% for lang in languages %} lang.languageText Language lang.levelText Proficiency certificationsList Loop with {% for cert in certifications %} cert.certificateText Certificate name, with the issuer in brackets when there is one cert.dateText Date obtained
Variable Type Description hobbyList Hobbies additional_informationText Additional information custom_fieldsName to value Your custom fields , read by name
# How dates lookDates are written as YYYY when only the year is known and MM-YYYY otherwise. A job that has a start date but no end date shows Current . If your organization enforces a date format in its conversion settings , dates are exactly as that setting wrote them when the CV was imported.