# Keep different seniority levels separate

**Use case:** 

Strict matching retains separate senior and junior roles while grouping identical exported copies.

## Input

```json
{
  "listings": [
    {
      "title": "Senior Data Engineer",
      "companyName": "Example Labs",
      "companyDomain": "example.com",
      "location": "Remote US",
      "source": "Greenhouse",
      "id": "example-101",
      "url": "https://job-boards.greenhouse.io/example/jobs/example-101",
      "description": "Build reliable data pipelines and financial reporting tools. Design Python services, review database queries, monitor production workloads and document technical decisions. Work with product managers and analysts to clarify requirements. Improve automated testing and deployment workflows. Investigate incidents, explain root causes and support other engineers. This full-time role focuses on data quality and service reliability for the platform team."
    },
    {
      "jobTitle": "Sr. Data Engineer",
      "company": "Example Labs Inc.",
      "companyWebsite": "https://example.com",
      "location": "Remote US",
      "source": "Indeed",
      "id": "mirror-101",
      "url": "https://www.indeed.com/viewjob?jk=example101",
      "description": "Build reliable data pipelines and financial reporting tools. Design Python services, review database queries, monitor production workloads and document technical decisions. Work with product managers and analysts to clarify requirements. Improve automated testing and deployment workflows. Investigate incidents, explain root causes and support other engineers. This full-time role focuses on data quality and service reliability for the platform team."
    },
    {
      "title": "Junior Data Engineer",
      "companyName": "Example Labs",
      "companyDomain": "example.com",
      "location": "Remote US",
      "source": "Greenhouse",
      "id": "example-102",
      "url": "https://job-boards.greenhouse.io/example/jobs/example-102",
      "description": "Build reliable data pipelines and financial reporting tools. Design Python services, review database queries, monitor production workloads and document technical decisions. Work with product managers and analysts to clarify requirements. Improve automated testing and deployment workflows. Investigate incidents, explain root causes and support other engineers. This full-time role focuses on data quality and service reliability for the platform team."
    }
  ],
  "strictness": "strict",
  "maxListings": 1000
}
```

## Output

```json
{
  "verdict": {
    "label": "verdict"
  },
  "bestListing.title": {
    "label": "title"
  },
  "bestListing.employer": {
    "label": "employer"
  },
  "bestListing.location": {
    "label": "location"
  },
  "bestListing.url": {
    "label": "url"
  },
  "bestListing.id": {
    "label": "id"
  },
  "bestListing.source": {
    "label": "source"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Job Listings Deduplicate: Match Roles Across ATS Boards Actor is ready to run with the inputs already set for "Keep different seniority levels separate". [Sign up or log in](https://console.apify.com/create-task-from-example/zcXlQZbXwOn6iIazV) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Keep different seniority levels separate" task

The Job Listings Deduplicate: Match Roles Across ATS Boards Actor will start running based on the input automatically. You can also change all the input fields, like job listings, matching strictness, and more, to match your specific use case.

### 3. Receive the "Keep different seniority levels separate" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as verdict, title, employer, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Keep different seniority levels separate" task via API](https://apify.com/moggedhq/job-listings-deduplicate.md).

## About this Actor

This example demonstrates how to use [Job Listings Deduplicate: Match Roles Across ATS Boards](https://apify.com/moggedhq/job-listings-deduplicate.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/moggedhq/job-listings-deduplicate.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/moggedhq/job-listings-deduplicate.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).