# New in a role

People who just started a job you sell to.

In the API this is the signal type `new_in_role` (People who just took a role). You run it with the same route as every signal: a search.

## What it finds

People who started a role with one of your titles in the last 3 months, optionally only external hires, each with their new role. The search itself can filter on the sector and size of the company.

## Rows and price

- One row per person, as the source shows it, with no AI judging it: you decide which rows fit.
- At most 25 rows per search, 25 unless you send `limit`; more with `cursor`. **1 credit** per row.
- A search that delivers nothing is free.

## The signal object

Send it as `signal` in the body of POST /searches. The other fields of the body are on [Start a search](/docs/api-reference/start-search).

- **`type`** `string` · **required** — Always `new_in_role`.
- **`titles`** `string[]` · **required** — Job titles of the new role; a title is a condition, not a hint. 1 to 10 items.
- **`locations`** `string[]` · **required** — Countries (ISO 3166-1 alpha-2 or English name) where the person lives. 1 to 5 items.
- **`external_only`** `boolean` — Only people who came from another company (no internal promotions). Defaults to `false`.
- **`sectors`** `string[]` — Exact LinkedIn industry names of the company, e.g. "Software Development". Up to 5 items.
- **`company_sizes`** `string[]` — Headcount ranges of the company. One of: `self-employed`, `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+`.

## Limits

- Depends on people updating their profile: a change that is not on the profile yet is not seen.
- "New" means the role started at most 3 months ago, and started_on has month precision.

## Run it

- **Once**: [Start a search](/docs/api-reference/start-search) (`POST /searches`). [Preview a search](/docs/api-reference/preview-search) shows the most it can cost first. The rows are in [List search results](/docs/api-reference/search-results).
- **To follow it**: run the search again, for example every week. There are no watches.
- **From your assistant**: `search_signals` runs it ([MCP](/docs/api-reference/mcp)), on the mySDR connection the assistant signed in to, or on the Signals MCP server with a key.

## Example

A search, `POST /searches`:

```json
{
  "signal": {
    "type": "new_in_role",
    "titles": [
      "Chief Financial Officer",
      "CFO"
    ],
    "locations": [
      "BE"
    ],
    "external_only": true
  },
  "limit": 25
}
```