# GitLab Careers Job Listings & Company Profile Extractor (`dataspryva/gitlab-careers-job-listings-and-company-profile`) Actor

Get live GitLab job openings by keyword, department, or job ID/URL with location, publish/update dates, and full descriptions, plus a GitLab company careers profile record.

- **URL**: https://apify.com/dataspryva/gitlab-careers-job-listings-and-company-profile.md
- **Developed by:** [Dataspryva](https://apify.com/dataspryva) (community)
- **Categories:** Jobs, Developer tools, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

## GitLab Careers Job Listings & Company Profile Extractor

Pull live job openings straight from GitLab's own public careers board, or grab a snapshot of GitLab's careers page itself. Search by keyword, filter by department or quota-coverage type, resolve exact job IDs or URLs, or fetch a lightweight company-profile record — all without opening a browser.

### What this actor does

- **Six modes:** keyword search, all open jobs, filter by department, resolve exact job IDs, resolve exact job URLs, or fetch a GitLab company profile
- **Full job detail on request:** title, location, department, requisition ID, publish/update timestamps, and (optionally) the full description text, HTML, section headings, and outbound links
- **Filters:** location substring, minimum publish date, minimum update date, department names, and quota-coverage type
- **Sorting:** by publish date, update date, or title, ascending or descending
- **Empty fields are omitted, and invalid lookups return a typed `error` record instead of failing silently**

### Output per record

The actor emits `job`, `company`, or `error` records, each marked by `recordType`.

#### Job records

- `jobId` — the job's numeric ID
- `url` — direct apply URL for the posting
- `title` — job title
- `companyName` — always `GitLab`
- `location` — office or remote location string
- `language` — posting language code
- `requisitionId` — GitLab's internal requisition number
- `internalJobId` — GitLab's internal job ID, when distinct from `jobId`
- `firstPublishedAt`, `updatedAt` — ISO timestamps for when the posting first went live and was last updated
- `applicationDeadline` — ISO timestamp, when the posting has one
- `metadata` — any additional name/value fields GitLab attaches to the posting
- `quotaCoverageType` — sales quota-coverage classification, for sales roles that carry one
- `departmentNames` — department(s) the role belongs to
- `officeNames` — office(s) associated with the role
- `descriptionHtml`, `descriptionText` — the full job description, as HTML and as plain text, when `fetchFullDescription` is enabled
- `sectionHeadings` — heading text pulled from the description, when available
- `descriptionLinks` — outbound links found in the description
- `complianceTypes` — data-compliance classifications attached to the role, when present
- `scrapedAt` — when the record was fetched

#### Company profile record

- `companyName` — `GitLab`
- `companyUrl` — GitLab's main site
- `careersUrl`, `benefitsUrl`, `valuesUrl`, `handbookUrl` — GitLab's careers, benefits, values, and handbook pages
- `remoteCompany` — `true` when the careers page content indicates GitLab is an all-remote company
- `companySummary` — the first substantial paragraph pulled from the careers page
- `introParagraphs` — up to 6 paragraphs of careers-page intro text
- `sectionHeadings` — up to 12 heading texts from the careers page

#### Error record

- `errorType` — always `invalid_input`
- `message` — what went wrong (e.g. a required field was missing for the chosen mode)
- `mode`, `field` — which mode and input field triggered the error
- `scrapedAt` — when the record was produced

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | string | `searchJobs` | `searchJobs`, `allJobs`, `byDepartment`, `byJobIds`, `byJobUrls`, or `companyProfile` |
| `searchQuery` | string | – | Keyword matched against title, company, location, and requisition ID (mode=`searchJobs`) |
| `departmentNames` | array | `[]` | Exact GitLab department names, required for `byDepartment` and usable as a filter in other list modes |
| `quotaCoverageTypes` | array | `[]` | Exact quota-coverage values to filter by (sales roles only) |
| `jobIds` | array | – | Exact job IDs to resolve (mode=`byJobIds`) |
| `jobUrls` | array | – | Exact job URLs to resolve (mode=`byJobUrls`) |
| `locationContains` | string | – | Case-insensitive location substring filter (e.g. `Remote`, `EMEA`, `US`) |
| `publishedFrom` | string | – | Keep jobs first published on or after this ISO date/time |
| `updatedFrom` | string | – | Keep jobs updated on or after this ISO date/time |
| `sortBy` | string | `firstPublishedDesc` | `firstPublishedDesc`, `firstPublishedAsc`, `updatedDesc`, `updatedAsc`, `titleAsc`, or `titleDesc` |
| `fetchFullDescription` | boolean | `true` | Fetch each job's detail page for description text, departments, offices, and headings |
| `maxItems` | integer | `5` | Maximum number of records to emit (1–5000) |

#### Example: keyword search

```json
{
  "mode": "searchJobs",
  "searchQuery": "engineer",
  "maxItems": 10
}
```

#### Example: all open jobs in one department

```json
{
  "mode": "byDepartment",
  "departmentNames": ["Data Engineering"],
  "sortBy": "firstPublishedDesc",
  "maxItems": 50
}
```

#### Example: resolve specific job URLs

```json
{
  "mode": "byJobUrls",
  "jobUrls": ["https://job-boards.greenhouse.io/gitlab/jobs/8503792002"]
}
```

#### Example: company careers profile

```json
{
  "mode": "companyProfile"
}
```

### Use cases

- **Recruiting research** — track which roles GitLab has open in a specific department or location
- **Talent market monitoring** — watch `firstPublishedAt`/`updatedAt` to see how fast GitLab is hiring in a function
- **Sales intelligence** — filter by `quotaCoverageType` to see GitLab's current sales-role mix
- **Job board aggregation** — feed GitLab's own postings into a broader jobs dataset alongside other companies
- **Employer-brand research** — pull GitLab's careers-page summary and values/handbook links in one call

### FAQ

**Is this affiliated with GitLab?**
No. This is an independent, third-party actor that reads GitLab's own publicly posted job board and careers page; it is not affiliated with or endorsed by GitLab.

**Do I need a login or API key?**
No. GitLab's job board and careers page are public, and the actor reads them without authentication.

**What's the difference between `searchJobs` and `allJobs`?**
`searchJobs` matches a keyword against title, company, location, and requisition ID. `allJobs` returns open postings without requiring a keyword, so you can apply only the other filters (location, department, dates).

**Why would I use `byJobIds` or `byJobUrls` instead of search?**
Use them when you already know the exact job(s) you want — they resolve a specific posting directly rather than searching or listing.

**Why are some job fields like `descriptionHtml` missing?**
`descriptionHtml`, `descriptionText`, `sectionHeadings`, `descriptionLinks`, and `complianceTypes` all come from the job's detail page, so they're only present when `fetchFullDescription` is enabled (or when `departmentNames` filtering forces a detail fetch anyway). `departmentNames`/`officeNames` come from the job listing itself and appear regardless of `fetchFullDescription`, when GitLab's listing publishes them for that job.

**What happens if I pass an invalid job ID or URL?**
The actor returns a typed `error` record for that lookup instead of failing the whole run, so valid lookups in the same input still come back.

**How fresh are the job listings?**
Every run queries GitLab's live job board directly, so results reflect whatever is posted at run time.

**What does the `companyProfile` mode actually return?**
A single summary record built from GitLab's own careers page — its intro paragraphs, section headings, and links to its benefits, values, and handbook pages — rather than individual job postings.

# Actor input Schema

## `mode` (type: `string`):

Choose how to collect GitLab data.

## `searchQuery` (type: `string`):

Keyword used by searchJobs mode. Matches job title, company, location, and requisition ID.

## `departmentNames` (type: `array`):

Exact GitLab department names for byDepartment mode or as an additional filter. Known values: AMER - Commercial, Alliances and Channel, Architecture Engineering, Customer Experience, Customer Success, Data Engineering, DevOps Engineering, EMEA - Commercial, EMEA - Enterprise, Enablement, Enterprise Applications, Platforms, Platforms Engineering, Practice Management, Sales Development, Sec Engineering, Talent Acquisition, Technical Writing.

## `quotaCoverageTypes` (type: `array`):

Exact quota coverage values from GitLab's Greenhouse metadata. Known values: Account Executive, N/A, Overlay, Overlay Quota Rep (OQR).

## `jobIds` (type: `array`):

Exact Greenhouse job IDs for byJobIds mode.

## `jobUrls` (type: `array`):

Exact Greenhouse job URLs for byJobUrls mode.

## `locationContains` (type: `string`):

Optional case-insensitive location substring filter, for example Italy, Remote, EMEA, or US.

## `publishedFrom` (type: `string`):

Optional ISO date/time lower bound for firstPublishedAt.

## `updatedFrom` (type: `string`):

Optional ISO date/time lower bound for updatedAt.

## `sortBy` (type: `string`):

Sort order for job list modes.

## `fetchFullDescription` (type: `boolean`):

When enabled, fetches detail pages to include description text, departments, offices, and section headings.

## `maxItems` (type: `integer`):

Maximum records to emit.

## Actor input object example

```json
{
  "mode": "searchJobs",
  "searchQuery": "engineer",
  "departmentNames": [
    "Architecture Engineering"
  ],
  "quotaCoverageTypes": [],
  "sortBy": "firstPublishedDesc",
  "fetchFullDescription": true,
  "maxItems": 5
}
```

# Actor output Schema

## `items` (type: `string`):

Dataset containing all scraped GitLab job and company profile records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "searchJobs",
    "searchQuery": "engineer",
    "departmentNames": [
        "Architecture Engineering"
    ],
    "sortBy": "firstPublishedDesc",
    "fetchFullDescription": true,
    "maxItems": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("dataspryva/gitlab-careers-job-listings-and-company-profile").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "searchJobs",
    "searchQuery": "engineer",
    "departmentNames": ["Architecture Engineering"],
    "sortBy": "firstPublishedDesc",
    "fetchFullDescription": True,
    "maxItems": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("dataspryva/gitlab-careers-job-listings-and-company-profile").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "searchJobs",
  "searchQuery": "engineer",
  "departmentNames": [
    "Architecture Engineering"
  ],
  "sortBy": "firstPublishedDesc",
  "fetchFullDescription": true,
  "maxItems": 5
}' |
apify call dataspryva/gitlab-careers-job-listings-and-company-profile --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/gitlab-careers-job-listings-and-company-profile"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lGm7YLYFVi4ODDsx0/builds/69oLaxsT5gqomdQ9N/openapi.json
