Skip to main content

​
Prerequisites

Before setting up job settings, ensure you have:
  • Admin or RevOps access to your PG:AI organisation
  • At least one territory created
  • Job data enrichment enabled for your accounts

​
Overview

Jobs settings let you define saved job searches - keyword-based searches that find relevant job postings across your territory accounts. Each job setting targets specific roles or functions, revealing hiring signals that tell you what accounts are investing in. Navigate to Territories → Jobs in the left sidebar.
Use job titles or keywords to find relevant job postings that reveal hiring signals and make your territory planning more targeted and informed.

​
Creating a Job Setting

1

Navigate to Jobs

Go to Territories → Jobs in the left sidebar.
2

Add new job setting

Click + New Job Setting (top-right button).
3

Fill in General details

FieldDescriptionExample
NameA descriptive name for this saved job search”Chief Revenue Officer”
DescriptionWhat this job search is tracking”Chief Revenue Officer”
4

Configure Search Keywords

FieldDescriptionExample
Job Title KeywordsKeywords to look for in job titles”CRO”, “Chief Revenue Officer”, “Chief revenue”
Description KeywordsKeywords to look for in job descriptions”Chief revenue”, “Revenue operations”
5

Save

Click Save.

​
Managing Job Settings

The Jobs settings page shows all configured job searches in a table:
ColumnDescription
NameThe name of the job setting
DescriptionWhat this search tracks
Job TitlesTitle keywords configured (shown as tags)
KeywordsDescription keywords configured (shown as tags)
Max JobsMaximum number of job postings to return per account
  • Click any job setting to edit its keywords and configuration.
  • Use the search bar to filter by name.

​
How Job Matching Works

PG:AI searches job postings across your territory accounts, matching against the title and description keywords you’ve defined. When matches are found:
  • The number of matching job postings is tracked per account.
  • Job data appears in territory views and account profiles.
  • Job counts feed into scoring models as rule inputs.
The Max Jobs field limits how many job postings are returned per account for this search (e.g. 10, 20, or 100).

​
Using Jobs in Territory Settings

Job settings appear in your territory’s Enriched Columns (Territory Settings → Enriched Columns) with the type “Jobs”. Toggle them on to include job data in territory views and scoring. For example:
  • “RevOps Job Monitoring” - Jobs - Included: ON
  • “Chief Revenue Officer” - Jobs - Included: ON
  • “Enterprise Account Executive” - Jobs - Included: ON
  • “Job monitoring test” - Jobs - Included: OFF
Only job settings toggled on will contribute to this territory’s views and scoring models.

​
Using Jobs in Scoring Models

Job counts can be used as inputs to scoring model rules. For example, from the scoring model interface:
  • “Baseline rule for RevOps” - Jobs - weight 3
  • “Baseline rule for Chief Revenue Officer” - Jobs - weight 50
  • “Baseline rule for Enterprise Account Executive” - Jobs - weight 16
Higher weights mean that job signal contributes more to the overall account score. See the Scoring Models setup guide for details.

​
Connecting Jobs to Monitoring Agents

Job settings can also be linked to monitoring agents for real-time alerts.
1

Create a new monitoring agent

From the New Agent form, select a Saved Job Search to use as the monitoring source.
2

Configure alert settings

Set up the Alert Configuration:
  • Severity - how important this alert is
  • Alert Title - template for the alert (supports variables like {job_title}, {job_url}, {company_name})
This means you can get alerted whenever a territory account posts a new job matching your keywords. See the Monitoring Agents setup guide for details.

​
Common Configurations

Role-based job monitoring:
NameJob Title KeywordsDescription KeywordsMax Jobs
Chief Revenue OfficerCRO, Chief Revenue OfficerChief revenue20
RevOps Job MonitoringRevenue Operations, Sales OpsRevenue opera…, Sales operations10
Enterprise Account ExecutiveAccount Executive, Enterprise AEAccount execut…, Enterprise100
Function-based job monitoring:
NameJob Title KeywordsDescription KeywordsMax Jobs
Data EngineeringData Engineer, Analytics EngineerData pipeline, ETL20
Cloud InfrastructureCloud Engineer, DevOps, SREAWS, Azure, GCP, Kubernetes20
SecuritySecurity Engineer, CISOCybersecurity, Security operations20
Use a higher Max Jobs value (50–100) for broad searches and a lower value (10–20) for specific role searches.

​
Troubleshooting

IssueLikely CauseFix
Job setting shows no resultsKeywords too specific or job enrichment not runningBroaden keywords or trigger job enrichment
Too many irrelevant matchesDescription keywords too broadUse more specific keywords or rely primarily on title keywords
Jobs not appearing in territory viewsJob setting not toggled on in enriched columnsTerritory Settings → Enriched Columns → toggle Jobs items on
Job counts not feeding into scoring modelJobs not enabled or no scoring rule referencing jobsAdd a scoring rule that uses job data