Jadiroon is built for the Saudi context out of the box. This page summarises the country-specific fields that surface across forms, lists, and profiles.
Nationality
Optional field on the Person record. Stored as an ISO-2 country code: SA for Saudi, EG for Egyptian, PK for Pakistani, PH for Filipino, IN for Indian, and so on.
In the UI:
- The /people list shows a 2-letter chip beside each name. Saudis carry an emerald tone; everyone else a neutral tone.
- The person profile displays the full nationality name beside the status badge.
- /grow/succession and /grow/mobility offer a "Saudi only" toggle that filters the list to Saudi nationals. The filter is purely visual — it does not change the underlying match score or ranking.
National ID / Iqama
Optional field on the Person record. Stored as a single 10-digit number with no discriminator between citizen ID and residency permit:
- Numbers starting with
1are typically Saudi National IDs. - Numbers starting with
2are typically Iqama (residency) numbers.
The value is captured through the public apply form on a job role. It saves directly to the Person record so it migrates with the candidate to the employee stage automatically.
The platform does not validate the number technically. Validation is left to your HR governance.
Role grade level (gradeLevel)
Optional field on the Role record. Free-form text that accepts either ladder:
- Saudi government grade ladder: "الأولى" through "العاشرة", "مرتبة ممتازة", "مستشار", "مدير عام", "وكيل".
- Private-sector ladder: Junior, Mid, Senior, Lead, Manager, Director, VP, C-level.
The role wizard offers a unified datalist combining both ladders, ordered with the more relevant ladder first depending on the workspace's sector (gov sectors lead with the gov ladder).
Grade appears as a chip on the role card and the role detail header, and is passed into the JD generator and career-path narrative prompt so the LLM can reference any grade-level jump explicitly when describing the path between current and target roles.
Saudization preference (saudizationPreference)
Boolean flag on the Role record (default false). When enabled:
- A "السعوديون أولاً / Saudis preferred" chip appears prominently on the public job posting and on the role detail header.
- A "Saudi-preferred only" toggle is offered at the top of the public /jobs page to filter the listing.
- The JD generator switches in the formal phrasing "تعطى الأولوية للمواطنين السعوديين" — never exclusionary "Saudis only" language.
In v1.0 the filter is display-only; the match scoring engine does not auto-weight Saudi candidates. Nitaqat-aware scoring is on the roadmap.
Saudi 4-part name
The formal Saudi name is composed of four parts: first name, father's name, grandfather's name, family name. The platform stores them as four optional fields on the Person record alongside the legacy firstName / lastName columns, which remain required for backwards compatibility.
The four parts are captured in:
- The invite-acceptance screen (
/invite/[token]) — four separate fields; first and family name are required, the middle two are optional.
The four parts render formally through displayName(person, "ar"):
- All four parts present: "محمد بن أحمد بن عبدالله الشمري".
- First + father + family: "محمد بن أحمد الشمري".
- First + family only: "محمد الشمري".
- Falls back to firstName + lastName when the four parts are absent.
For English text the helper collapses to first + family (e.g. "Mohammed Al-Shamri") since the English form of Saudi names is almost universally truncated.
Where these fields show up downstream
- AI-generated narratives (career path, JD, interview rationale) take nationality, grade level, and the Saudization flag into account when drafting prose.
- JD generation references Vision 2030 and نظام العمل السعودي where relevant, and switches in the formal Saudization phrasing when the role flag is on.
- Career path and succession filtering use the "Saudi only" toggle without affecting the match score itself.