CV Mapping Overview

Modified on Thu, 22 May, 2025 at 1:59 PM

FLOW:

ATS → Feed/API → CMS → Job Board / Job Platform

STEP BY STEP MAPPING FLOW

Step	System	Purpose	Example Field: `occupation_type`
1	ATS	Recruiter enters job	`Engineering` (user-selected or coded as `ENG001`)
2	Feed/API	Job data export from ATS	Field may be `jobFunction: "Engineering"`
3	CMS	Parses the feed, maps values	CMS maps `"Engineering"` to its internal taxonomy or tag
4	Careers.Vic	CMS publishes to Careers.Vic or displays it	Job board receives standardized category like `"Engineering & Manufacturing"`

EXAMPLE MAPPING

Example used: occupation_type

Source System	Field Name	Value	Notes
ATS	`job_function_code`	`ENG001`	Internal code in ATS
Feed/API	`jobFunction`	`Engineering`	Human-readable string
CMS	`occupation_type`	`Engineering`	Parsed and may be categorized or tagged
Job Board	`category`	`Engineering & Tech`	Standardized per board taxonomy

VISUAL DIAGRAM:

Recruiter → [ATS]

↓

Job Feed/API

↓

[CMS]

↓

[Job Board / Website]

WHERE FIELD MAPPING HAPPENS

Feed Layer:
- Translates ATS field names to CMS field names.
- May also map code → string (e.g., ENG001 → Engineering).
CMS Layer:
- Maps incoming feed values to match job board-friendly terms.
- Controls display, tagging, categorization, and publishing logic.

KEY CONSIDERATIONS:

Your CMS becomes the last point of control before the job hits the public.
If job board taxonomy changes, you'd likely update mappings in the CMS.
If your CMS handles multiple job boards, it might have conditional logic to map one ATS value to different job board-specific categories.

FRESHDESK TICKETS WITH MAPPING SCENARIOS

https://vpscsupport.freshdesk.com/a/tickets/27239