Skip to main content

Job Types

Create and manage employment categories to help candidates understand role types and improve Google for Jobs visibility.

Written by Grace
Updated over 2 months ago

Overview

This article helps you create and manage job types in Access Volcanic. Job types describe the nature of employment for a role and help candidates quickly understand what kind of opportunity is being offered. They also support Google for Jobs optimisation through structured data mapping.


Key benefits

Job types provide several advantages for both candidates and administrators:

  • Help candidates quickly identify relevant employment opportunities.

  • Improve Google for Jobs visibility through structured data mapping.

  • Create consistent employment categorisation across your website.

  • Support ATS integrations with external reference codes.

  • Enable filtering and organisation of job listings by employment type.

  • Maintain clear employment taxonomy for administrative purposes.


Before you start

Before creating job types, ensure you have the necessary access and planning in place:

  • Admin access to your organisation's Access Volcanic platform account.

  • Permission to access Settings and Reference Data in the Admin Area.

  • A clear understanding of the employment categories your organisation uses:

    • Verify the completeness of job data, especially ensuring that job type selections are correctly populated in the ATS or other integrated systems like Broadbean before transmission.

  • Knowledge of any ATS integration requirements for specific identifiers.

πŸ“Œ Note: Job types are used across your site wherever a role requires an employment category, so plan your taxonomy carefully before creating multiple types.


Accessing job types

You can access job type management through your Admin Area.

  1. Log in to the Admin Area.

  2. Click Settings in the top navigation.

  3. Under Reference Data, select Job Types.

This opens the list of existing job types and provides access to create new ones.


Creating a job type

Follow these steps to add a new job type to your system.

  1. Click the + New button.

  2. Enter the job type Name (required).

  3. Complete any optional fields as needed:

    • Reference for external system identifiers.

    • Cached slug for URL-friendly versions.

    • Google for Jobs employment types for search optimisation.

  4. Click Submit to save the job type.

πŸ€“ Tip: Configure all required job types before creating jobs to maintain consistent taxonomy across your site.


Edit a job type

Follow these steps to modify an existing job type.

  1. Locate and select the job type you want to modify.

  2. Update any fields as needed.

  3. Click Submit to save your changes.

⚠️ Important: Editing a job type updates it everywhere it's used, including existing job adverts and structured data.


View job types

Use these steps to review your existing job types.

  1. Review the complete list of existing job types.

  2. Use this view to assess your current taxonomy and identify any gaps or duplicates.

πŸ“Œ Note: Job types appear throughout your site wherever roles require employment categorisation.


Linking job types to jobs

Once created, job types can be assigned to individual job listings.

  1. Open any job record in the Admin Area.

  2. Locate the Job Type field.

  3. Select the appropriate job type from the dropdown.

  4. Save the job to apply the assignment.

The selected job type will appear on the job advert and contribute to structured data used for Google for Jobs optimisation.


Understanding job type fields

Each job type includes several configurable fields that serve different purposes.

Name (required)

The Name is the visible label that users and administrators see throughout the system. This should be clear, recognisable, and consistent with your organisation's terminology. Examples include Full-time, Part-time, or Temporary.

Reference (optional)

The Reference field stores internal or external reference codes. This is useful when syncing job types with external systems such as an ATS. These systems expect specific identifiers for proper integration.

Cached slug (optional)

The Cached slug creates a URL-friendly version of the job type name. This supports cleaner URLs and internal referencing. Leave this field unchanged unless your implementation team or Access support specifically advises modification.

Google for Jobs employment types (optional)

This field maps your job type to Google-recognised employment categories for structured data optimisation. These values are used by Google for Jobs' structured data. Available options include:

  • FULL_TIME for standard full-time positions.

  • PART_TIME for part-time roles.

  • CONTRACTOR for contract positions.

  • TEMPORARY for temporary assignments.

  • INTERN for internship opportunities.

  • VOLUNTEER for volunteer positions.

  • PER_DIEM for daily-rate roles.

  • OTHER for positions not covered by standard categories.

πŸ“Œ Note: Mapping job types to Google categories improves structured data and search visibility for your job listings.


Best practices

Following these guidelines will help you maintain effective job type management:

  • Keep your job type list concise and focused on meaningful employment distinctions.

  • Map each job type to relevant Google for Jobs categories to improve search visibility.

  • Establish consistent naming standards to prevent duplicate job types with similar meanings.

  • Review job types periodically to ensure they reflect current hiring practices and organisational needs.

  • Use clear, recognisable names that candidates will easily understand.

  • Configure all required job types before creating job listings to maintain taxonomy consistency.- Regularly audit integration data, such as ATS or Broadbean job type fields, to ensure alignment with Volcanic configurations.

  • Consider ATS integration requirements when setting up reference codes for external system compatibility.

πŸ“Œ Note: Consistent job type usage across your platform improves both user experience and search engine optimisation.


FAQs

Q1: Can I delete a job type that's no longer needed?

  • Answer: You can delete a job type that's no longer needed only if it isn't currently linked to any jobs. Remove or update dependent job listings first, then delete the unused job type through the Admin Area.

Q2: What happens when I change a job type name?

  • Answer: When you change a job type name, the updated name appears everywhere the job type is used throughout your site, including existing job adverts and administrative interfaces. Changes take effect immediately.

Q3: Do Google for Jobs employment types affect how jobs appear on my website?

  • Answer: Google for Jobs employment types do not affect how jobs appear on your website. These mappings only affect the structured data sent to search engines. The display on your website uses the job type name you've configured.

Q4: How many job types should I create?

  • Answer: When deciding how many job types to create, focus on meaningful distinctions that help candidates understand employment expectations. Typically, 4-8 job types cover most organisational needs without creating unnecessary complexity.

Q5: Can I use the same job type name with different Google mappings?

  • Answer: You cannot use the same job type name with different Google mappings because each job type must have a unique name within your system. If you need different Google mappings, create separate job types with distinct names that reflect the differences.

Q6: What happens if I don't map job types to Google categories?

  • Answer: If you don't map job types to Google categories, your jobs will still function normally, but you'll miss opportunities for improved Google for Jobs visibility and structured data optimisation.

Q7: Can job types be used for reporting and analytics?

  • Answer: Yes, job types can be used for reporting and analytics as they provide valuable categorisation for analysing application patterns, posting performance, and employment trends across your recruitment activities.

Q8: How do ATS integrations use job type reference codes?

  • Answer: ATS integrations use job type reference codes to match job types between systems, ensuring consistent categorisation when syncing job data across platforms.

Q9: Why does a job posted via Broadbean show the wrong job type on my website?

  • Answer: If no job type is provided by Broadbean, the Access Volcanic platform automatically assigns the first option in the pre-configured list of job types. To prevent this, ensure all jobs sent from your ATS or integration services include a valid job type selection before posting.

Q10: How can I prevent jobs from being assigned incorrect job types?

  • Answer: Verify that all jobs sent from your ATS include a valid job type selection before they reach your website. Review the order of job types in your website's configuration to ensure the default aligns with your expectations, as this default is applied when no job type is provided.

Q11: What should I do if a job already has the wrong job type assigned?

  • Answer: Manually adjust the job type directly on the platform by editing the job record. Navigate to the job in your Admin Area and update the job type field to the correct value.

Q12: Why is my job appearing in the wrong category even though it's featured?

  • Answer: Jobs appear in categories based on discipline-to-category assignments, and the featured status does not override this logic. Review and adjust the discipline assignments for the job to ensure it displays in the correct category.

Q13: How do I fix jobs that are appearing in incorrect categories?

  • Answer: Verify the discipline assignments for the affected jobs and correct any misaligned assignments directly in the platform. Once the discipline assignment matches the intended category, the job will display in the correct location on your site.

Did this answer your question?