Role

Description These are roles which people (and other legal entities) hold at U.S. businesses.

type Role implements NodeFunctions {
  externalId: JSON
  externalUrl: String
  id: UUID!
  firstObservedDate: String
  lastObservedDate: String
  jobTitle: String
  jobFunction: String
  managementLevel: String
  startDate: Date
  startDatePrecision: String
  endDate: Date
  endDatePrecision: String
  internalId: String
  internalRoleId: String
  operatingLocations(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RoleOperatingLocationConnection
  phoneNumbers(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RolePhoneNumberConnection
  emailAddresses(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RoleEmailAddressConnection
  legalEntities(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RoleLegalEntityConnection
  registrations(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RoleRegistrationConnection
  brands(
    first: Int = 100
    last: Int
    after: String
    before: String
    conditions: ConnectionConditions
  ): RoleBrandConnection
  count(
    field: String!
    conditions: Conditions
  ): Int
  countDistinct(
    field: String!
    conditions: Conditions
  ): Int
  has(
    field: String!
    conditions: Conditions
  ): Boolean
  sum(
    field: String!
    conditions: Conditions
  ): Int
  min(
    field: String!
    conditions: Conditions
  ): Int
  max(
    field: String!
    conditions: Conditions
  ): Int
  avg(
    field: String!
    conditions: Conditions
  ): Float
  collect(
    field: String!
    separator: String
    conditions: Conditions
  ): String
  minDateTime(
    field: String!
    conditions: Conditions
  ): DateTime
  maxDateTime(
    field: String!
    conditions: Conditions
  ): DateTime
  _fn: JSON
}

Fields

`Role.externalId` ● `JSON` scalar

`Role.externalUrl` ● `String` scalar

`Role.id` ● `UUID!` non-null scalar

`Role.firstObservedDate` ● `String` scalar

`Role.lastObservedDate` ● `String` scalar

`Role.jobTitle` ● `String` scalar

Description

The standardized job title observed in our datasets of roles and employee contact details.
We take observed job titles and apply the following standardizations:

All separation characters are replaced with "and". (e.g., "|", "&", "/")
Replace '(' with comma. (e.g., John Smith (CEO) -> John Smith, CEO)
Convert accented characters into non-accented characters. (e.g., "é" -> "e")
Remove any non-alphanumeric characters (excluding commas)
Lowercase all characters. (e.g., "CEO" -> "ceo")
Expand abbreviations. (e.g., "ceo" -> "chief executive officer")

Full example: "John Smith (Founder/CEO) -> "john smith, founder and chief executive officer"

`Role.jobFunction` ● `String` scalar

Description

The standardized job description for this role, e.g. "Accounting", "Contracts", etc. We take observed job function descriptions and do minor string trimming.
The output is lowercase (e.g., " Product Marketing " -> "product marketing")

`Role.managementLevel` ● `String` scalar

Description

The standardized management level for this role. We use our standardized job title then given the data source, we apply an expected management level. We split management levels into governance roles and functional roles. Governance roles are typically filed on business registrations, or are clear examples of corporate governance. Functional roles are
those roles involved in the day-to-day company activities.

Management levels for functional roles: head, c-suite, director-level, vp-level, manager, non-manager
Management levels for governance roles: owner, founder, board of directors, corporate governance

We assign Null management level to those standardized job titles without sufficient information.

`Role.startDate` ● `Date` scalar

Description

The date the person started this role. Use start_date_precision (day, month, or year) to interpret the granularity. Null if no source reports a start date.

`Role.startDatePrecision` ● `String` scalar

Description

Indicates how to interpret the corresponding start_date value.

day — start_date is the exact day (e.g. 2024-03-15).
month — when year and month are known. start_date is set to the first of that month (2024-03-01 and precision="month" means the role started sometime in March 2024).
year — only the year is known. start_date is set to January 1 of that year (e.g. 2024-01-01 and precision="year" means the role started sometime in 2024).

Null when start_date is null.

`Role.endDate` ● `Date` scalar

Description

The date the person ended this role. Null if the role is currently active or no source reports an end date. Use end_date_precision (day, month, or year) to interpret the granularity.

`Role.endDatePrecision` ● `String` scalar

Description

Indicates how to interpret the corresponding end_date value.

day — end_date is the exact day (e.g. 2024-03-15).
month — when year and month are known. end_date is set to the first of that month (e.g. 2024-03-01 and precision="month" means the role ended sometime in March 2024).
year — only the year is known. end_date is set to January 1 of that year (e.g. 2024-01-01 and precision="year" means the role ended sometime in 2024).