Mapademics DocsGlossary
Definitions for terms used across Mapademics Careers.
Glossary
Terms you will encounter in the Careers app and throughout these docs.
Activity tab
The tab on the applicant profile that records what happened to an applicant: their Skills Report opens, every step of their outcome survey, and every change of tracking status with who made it. See The applicant profile.
Active resume
The resume currently selected as the source of truth for an applicant's skills, sections, and Skills Report. An applicant can have multiple resume versions, but only one is active at a time. Toggle a different version from Resume Versions on the applicant's Overview tab.
Applicant
A person tracked in your Careers workspace. Created by adding them manually, by bulk-importing resumes, or when someone submits through your Resume Upload Widget.
Arlo
The in-app AI assistant. Open it from the sidebar Help… or with ⌘K. See Arlo, your in-app helper.
Background task
A long-running skills-extraction job triggered by an upload. Tracked under Data Import → Background Tasks, split between Resumes and Job Descriptions. Each task reports progress and ends in Completed or Failed.
Caseload
The set of applicants assigned to one coach. An open caseload counts only those not yet in a final-stage status. Surfaced per coach in Coach Analytics.
Coach Analytics
The admin-only page showing caseload, completions, and pipeline health for every coach in the workspace. Open it from Coach Analytics in the sidebar. See Coach Analytics.
Coaching axis
One of seven dimensions Careers scores a resume against in Coaching & Evaluation. See Resume coaching axes.
Communication consent
Whether an applicant has agreed to be contacted about their job search. Recorded when they submit through the Resume Upload Widget, when a coach confirms it, or when a coach makes them eligible for outcome surveys; withdrawn by a coach or by the applicant unsubscribing. Shown as the first switch in the applicant's Outcome Surveys sheet. See Outcome surveys on the applicant.
Custom field
An organization-defined field for tracking data Careers doesn't capture out of the box — for example a Veteran flag or a referral source. Custom fields apply to either applicants or resumes, come in five types (Text, Number, Date, Yes/No, Dropdown), and are configured under Settings → Custom Fields. Applicant custom fields appear on the applicant profile and as sortable, filterable columns on the Applicants list. See Custom fields.
Deactivated user
A teammate whose access has been revoked. They can no longer sign in, but everything they did — assignments, notes, skill edits — stays in the workspace. Deactivated teammates are listed under Settings → Users → Deactivated and can be reactivated at any time. See Inviting your team.
Eligibility (outcome surveys)
Whether an applicant is in the Applicant Outcome Surveys program. An eligible applicant is emailed once they have been in a trigger status long enough. Set per applicant from the Outcome Surveys sheet, at creation with the Eligible for Applicant Outcome Surveys toggle, or automatically by your organization's settings. See Outcome surveys on the applicant.
Job description (JD)
The text that describes a job — usually a PDF or a job-board URL — that Careers extracts skills from. Skills sourced from the JD show JD in the Source column on a job's Required Skills table.
Licence requirement
A credential a job posting asks for, read from the posting text and shown as Licenses Required on the job. Each is either Required or Preferred.
A required credential the applicant doesn't hold removes the job from their matches rather than lowering its score — there is no partial credit for a licence you don't have. A preferred one leaves the job in the list and moves the Match Score a little either way.
What Careers found on the applicant's side lives under Resume & Skills → Resume Sections → Licenses on their profile. See Matching applicants to jobs.
Match Score
A percentage shown next to every matched job on an applicant's Jobs tab. Higher percentages indicate stronger overlap between the applicant's skills and the role's required skills, weighted by skill criticality.
Mapademics Skills Library (MSL)
The standardized skills taxonomy that powers extraction and matching across Careers. Every skill on a resume, on a job, and in a Skills Report references an MSL skill so that comparisons stay consistent across applicants, jobs, and organizations.
Message
A support thread inside Careers, created when you send something through the sidebar Feedback button or downvote a job match. Each carries a reference of the form SUP-1, a type (General, Feature request, Bug, or Job feedback), and a status. Replies from the Mapademics team arrive under My Account → Messages. See Support.
Outcome survey
The short survey an applicant fills in after answering Yes to the question of whether they found a job. Built under Settings → Applicant Outcome Surveys → Surveys; a published survey never changes. Answers are read per applicant in the Outcome Surveys sheet and across the organization on the Outcome Surveys page. See Setting up Applicant Outcome Surveys and Outcome survey reporting.
Public job
A job posting Mapademics has discovered, vetted, and extracted skills from on your organization's behalf. The Public jobs you see depend on your contract with Mapademics. Public jobs live under the Public Jobs sidebar item and are read-only inside Careers. See Public Jobs.
Public employer
An employer record automatically created from one or more Public jobs. Like Public jobs, they are read-only. To override fields on a Public employer, create an Uploaded employer with the same name. See Employers.
Resume Source
The badge shown next to an extracted skill that tells you where it came from — typically Resume for skills inferred from the active resume, or a manual annotation if a coach added the skill by hand.
Resume Upload Widget
A hosted public form your applicants visit to submit themselves into your Careers workspace. Configured under Settings → Resume Upload Widget. See The Resume Upload Widget.
Scope
The Mine / Unassigned / All control on the Home board, deciding whose applicants the board shows. Defaults to Mine. See The Home board.
Sequence
One run of outcome survey emails to one applicant: the first ask and its reminders, on the spacing and count set under Reminders. A sequence starts when a trigger is met, and ends with a Yes or when the last send goes out. See Setting up Applicant Outcome Surveys.
Skill
A capability extracted from a resume or job description. Skills are normalized against the Mapademics Skills Library and carry a proficiency level on the Novice → Expert scale.
Skill domain
A higher-level grouping of skills (for example, customer support, supply-chain operations, professional & workplace). Used by the Strength Finder radar on an applicant and by the Skills Radar on a matched job.
Skills Report
The shareable view of an applicant's resume sections, extracted skills, coaching feedback, and job matches. Generate one with the Share button on an applicant's profile. See Coaching with the Skills Report.
SOC Code
A Standard Occupational Classification code that identifies an occupation. Shown on every job's detail page and used to align matched jobs with labor-market data.
Source
A column appearing on the Jobs list, the Employers list, the per-job Required Skills table, and the Skills Overview table on an applicant. The same word, two contexts:
- On a Jobs or Employers list it distinguishes Public (Mapademics-curated) from Uploaded (your organization added it).
- On a Required Skills or Skills Overview table it tells you where a skill was inferred from (for example, JD, Resume, or a manual edit).
Stage
A coarse grouping assigned to each tracking status — one of Not started, In progress, or Final. The default New status is locked to Not started; you set the stage on every other status under Settings → Applicant Tracking. The stage controls how the status behaves on the Home board: Final columns show only the most recent applicants rather than the full history. See Stages.
Stale
An open applicant whose record hasn't changed in more than fourteen days. Counted per coach as Stale 14d+ in Coach Analytics, and visible per applicant via the Last Activity column on the Applicants list. Automated changes count as activity, so a stale count is a prompt to look, not proof of neglect. It is not the same as In status 14d+, which counts applicants who have not changed tracking status in that time whatever else was edited.
Survey trigger
A tracking status in the In progress stage paired with a number of days. An eligible applicant who has been in that status for that many days starts a sequence. Configured under Settings → Applicant Outcome Surveys. See Survey Triggers.
Tracking status
A label that captures where an applicant is in your pipeline — for example, New, Phone screen, Onsite, Placed, Withdrawn. Each organization defines its own list under Settings → Applicant Tracking, and each status carries a stage. Every applicant starts on New (the one mandatory status) and your team moves them from there. The status pill appears on the Applicants list, on the applicant profile header, as a filter on the applicants list, and as a column on the Home board — where dragging a card between columns changes the status. It is not shown on the Skills Report. See Applicant Tracking and Tracking applicants through your pipeline.
Uploaded job
A job your team adds directly into Careers — by uploading a JD, pasting a posting URL, or entering details manually. Uploaded jobs live under the Uploaded Jobs sidebar item and are fully editable. See Uploaded Jobs.
Uploaded employer
An employer your team adds directly. Editable. Use these to override or supplement records auto-created from Public jobs.