GitLab Careers Job Listings & Company Profile Extractor
Pricing
from $0.49 / 1,000 results
GitLab Careers Job Listings & Company Profile Extractor
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.
Pricing
from $0.49 / 1,000 results
Rating
0.0
(0)
Developer
Dataspryva
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 hours ago
Last modified
Categories
Features
Share
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
errorrecord 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 IDurlβ direct apply URL for the postingtitleβ job titlecompanyNameβ alwaysGitLablocationβ office or remote location stringlanguageβ posting language coderequisitionIdβ GitLab's internal requisition numberinternalJobIdβ GitLab's internal job ID, when distinct fromjobIdfirstPublishedAt,updatedAtβ ISO timestamps for when the posting first went live and was last updatedapplicationDeadlineβ ISO timestamp, when the posting has onemetadataβ any additional name/value fields GitLab attaches to the postingquotaCoverageTypeβ sales quota-coverage classification, for sales roles that carry onedepartmentNamesβ department(s) the role belongs toofficeNamesβ office(s) associated with the roledescriptionHtml,descriptionTextβ the full job description, as HTML and as plain text, whenfetchFullDescriptionis enabledsectionHeadingsβ heading text pulled from the description, when availabledescriptionLinksβ outbound links found in the descriptioncomplianceTypesβ data-compliance classifications attached to the role, when presentscrapedAtβ when the record was fetched
Company profile record
companyNameβGitLabcompanyUrlβ GitLab's main sitecareersUrl,benefitsUrl,valuesUrl,handbookUrlβ GitLab's careers, benefits, values, and handbook pagesremoteCompanyβtruewhen the careers page content indicates GitLab is an all-remote companycompanySummaryβ the first substantial paragraph pulled from the careers pageintroParagraphsβ up to 6 paragraphs of careers-page intro textsectionHeadingsβ up to 12 heading texts from the careers page
Error record
errorTypeβ alwaysinvalid_inputmessageβ what went wrong (e.g. a required field was missing for the chosen mode)mode,fieldβ which mode and input field triggered the errorscrapedAtβ 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
{"mode": "searchJobs","searchQuery": "engineer","maxItems": 10}
Example: all open jobs in one department
{"mode": "byDepartment","departmentNames": ["Data Engineering"],"sortBy": "firstPublishedDesc","maxItems": 50}
Example: resolve specific job URLs
{"mode": "byJobUrls","jobUrls": ["https://job-boards.greenhouse.io/gitlab/jobs/8503792002"]}
Example: company careers profile
{"mode": "companyProfile"}
Use cases
- Recruiting research β track which roles GitLab has open in a specific department or location
- Talent market monitoring β watch
firstPublishedAt/updatedAtto see how fast GitLab is hiring in a function - Sales intelligence β filter by
quotaCoverageTypeto 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.