Job board jobs
Parameters, response schema, and authenticated examples for /v1/active-jb.
Retrieves active job board listings with support for filtering, full-text search, date ranges, pagination, and field selection. Use the time_frame parameter to select the time window.
Supported sources: linkedin, wellfound, ycombinator (filter via source / exclude_source). Only linkedin listings are checked for expiration at the moment.
Note: Description search (description, description_advanced) is not available for time_frame=6m.
bearerAuthAuthorizationBearer <token>Authenticate requests with Authorization: Bearer YOUR_API_KEY. Find and manage your API key in the dashboard at https://dashboard.fantastic.jobs/dashboard. Store the key in an environment variable and never expose it in client-side code.
time_frame*stringTime window for job listings. Smaller windows return fresher jobs in smaller batches; larger windows are best for backfills.
1h- firehose of just-discovered jobs (best for hourly polling).24h- most common choice for daily syncs.7d- weekly batch jobs.6m- full backfill (large; description search (description,description_advanced) is not available on6mfor/active-jb).
"24h""1h""24h""7d""6m"limit?integerNumber of results to return. Default: 100, min: 1, max: 1000.
Use with offset to paginate, e.g. limit=100&offset=0, then limit=100&offset=100, then limit=100&offset=200. For very large feeds prefer cursor over offset.
1 <= value <= 1000100offset?integerNumber of results to skip for pagination. e.g. limit=100&offset=200 returns the third page (results 201–300). Use cursor instead for very large feeds - offset becomes inefficient at deep pages.
0 <= valuecursor?integerCursor-based pagination. Pass the last job's id to get the next page. Note: When cursor is set, results are ordered by id ascending - this overrides the default ordering (date_posted desc, or date_modified desc on /modified-ats). Cursor and offset pagination therefore traverse the feed in different orders.
Interaction with offset: cursor overrides offset. If both are passed, offset is ignored. Pick one pagination strategy and stick with it.
int64organization_agency?stringFilter listings by recruitment-agency status of the organization. Omit to include both.
only- return only listings whose organization is a recruitment/staffing agency.exclude- exclude listings from recruitment/staffing agencies.
The agency flag itself is exposed in the response as org_linkedin_recruitment_agency_derived.
"only""exclude"description_format?stringFormat the job description should be returned in. Choose text for plain text or html for raw HTML. Omit the parameter entirely to exclude the description field from the response - descriptions are not included by default because they significantly increase payload size.
Caution: html returns the description as it was scraped from the source - sanitize before rendering on a web page.
"text""html"exclude_recruiter_fields?booleanSet to true to exclude recruiter fields (recruiter_name, recruiter_title, recruiter_url) from the response. Default: included.
include_beta?booleanOff by default. Set to true to include beta output fields inline with each job. On the job board feed this adds the structured location breakdown (locations_derived_structured) - the classification_* fields are ATS-only and are not returned here.
These fields are in beta - their shape and availability may change without notice, and they are excluded from the response entirely unless this flag is set. See Beta Output Fields for the full field reference.
title?stringText search on job title. Searches like a Google query:
software engineer- jobs with both words in the title."software engineer"- exact phrase.software OR engineer- either word.-engineer- exclude jobs withengineerin the title.
For Boolean operators, parentheses, or prefix matching, use title_advanced instead.
description?stringText search on job title and description combined. Searches a single index covering both fields, so a hit in either the title or the description matches - use title instead if you want to restrict matches to the job title only. Same syntax as title. e.g. python OR javascript OR js returns jobs whose title or description mentions any of those keywords. Not available for time_frame=6m. Heavy queries (long phrases, many ORs) on long time windows can time out - keep it tight.
location?stringText search on location fields. Search using full names, abbreviations are not supported.
- Use
United States, notUS. - Use
United Kingdom, notUK. - US states need their full name and country:
New York, United States,California, United States. - UK cities need the constituent country:
Birmingham, England, United Kingdom,Glasgow, Scotland, United Kingdom.
Multi-location with OR: "United States" OR "United Kingdom" or "San Francisco" OR "New York". For Boolean operators (parentheses, AND, NOT), use location_advanced.
See Nuances of Location Search for more.
organization?array<string>Filter by organization name(s). Exact, case-sensitive match - nvidia will not match NVIDIA. For fuzzy or Boolean matching, use organization_advanced.
Fetch the full list of organizations we currently track via /ats-organizations.
Escaping. Percent-encode the value as you would any URL parameter (& becomes %26, spaces become %20) - every HTTP client and SDK does this for you. Separately, wrap any individual value containing a comma or parentheses in double quotes, otherwise the comma is read as a list separator: organization="4imprint, Inc.". Quote each value on its own, never the whole list.
Input a comma-separated list.
exclude_organization?array<string>Exclude organization name(s). Same matching rules as organization (exact, case-sensitive), including the escaping rules - percent-encode the value, and double-quote any individual value containing a comma or parentheses (exclude_organization="4imprint, Inc."). For fuzzy/Boolean exclusion, use organization_advanced with !.
Input a comma-separated list.
title_advanced?stringBoolean full-text search on title. Operators: & (AND), | (OR), ! (NOT), <-> (followed-by), parentheses for grouping, :* for prefix matching.
Multi-word phrases must be single-quoted ('machine learning') or chained with <-> (machine <-> learning). If title is also passed, title_advanced takes precedence and title is ignored.
Examples:
(AI | 'machine learning' | robotics) & !marketing- AI/ML/robotics roles, no marketing titles.senior & (python | rust) & !staff- senior IC roles in either stack, excluding staff-engineer.project <-> manag:*- matchesproject manager,project management,project managing, ...
See Advanced Searching Guide for more.
description_advanced?stringBoolean full-text search on title and description combined (same index as description, so matches in either field count - pair with title_advanced if you also want to require a term in the title specifically). Same operator syntax as title_advanced. If description is also passed, description_advanced takes precedence and description is ignored. Not available for time_frame=6m. Description searches are expensive, if a query times out, simplify it, lower limit, or shrink the time window.
location_advanced?stringBoolean full-text search on location. Same operator syntax as title_advanced. If location is also passed, location_advanced takes precedence and location is ignored. The same naming rules as location apply (full names, no abbreviations).
Examples:
'United States' & !California- US minus California.Germany & !(Berlin | Munich)- Germany excluding two cities.'New York' | 'San Francisco' | Boston- multi-city.
organization_advanced?stringBoolean full-text search on organization name. Same operator syntax as title_advanced. If organization is also passed, organization_advanced takes precedence and organization is ignored.
Examples:
University & !Harvard- every "University" employer except Harvard.(Microsoft | Google | Apple)- match any of the three.Open <-> AI:*- matchesOpenAI,Open AI,Open-AI, etc.
date_posted_gte?stringFilter jobs posted on or after this date (ISO 8601). e.g. 2026-04-20T00:00:00. Posted-date timestamps are UTC, with a 1-2 hour ingestion delay between the source publishing the job and it appearing in this API.
See Time Fields for the difference between date_posted, date_created, and date_modified.
date-timedate_posted_lt?stringFilter jobs posted before this date (ISO 8601).
date-timedate_created_gte?stringFilter jobs indexed on or after this date (ISO 8601). date_created reflects when our system first indexed the job.
date-timedate_created_lt?stringFilter jobs indexed before this date (ISO 8601).
date-timesource?array<>Filter by source job board(s). Input a comma-separated list.
Note on expiry tracking: only linkedin listings are re-checked for expiration and surfaced via /expired-jb. wellfound and ycombinator listings stay in the active feed until naturally aged out, so plan your freshness logic accordingly if you ingest them.
exclude_source?array<>Exclude source job board(s). Input a comma-separated list.
seniority?array<string>Filter by LinkedIn-posted seniority level. English values: Internship, Entry level, Associate, Mid-Senior level, Director, Executive, Not Applicable. Case-sensitive.
Heads-up: many employers default to Not Applicable. If you filter to a specific level, you'll miss those, consider whether that's acceptable. Non-English postings may use localized seniority strings; if you target multiple markets, include both the English and local-language values.
Alternative: for a normalized, market-independent signal, use ai_experience_level instead.
Input a comma-separated list.
organization_industry?array<string>Filter by LinkedIn industry. Use the exact LinkedIn industry name (case-sensitive). Common values: Software Development, Information Technology and Services, Financial Services, Hospital & Health Care, Staffing and Recruiting, Marketing and Advertising. The full taxonomy of ~400 industries lives at LinkedIn Industries.
Escaping. Percent-encode the value as you would any URL parameter (& becomes %26, spaces become %20) - every HTTP client and SDK does this for you. Separately, wrap any individual value containing a comma in double quotes, otherwise the comma is read as a list separator. Several LinkedIn industries contain commas, so this matters: organization_industry="Health, Wellness & Fitness". Quote each value on its own, never the whole list.
Input a comma-separated list.
exclude_organization_industry?array<string>Exclude LinkedIn industry/industries. Same matching rules as organization_industry (exact, case-sensitive), including the escaping rules - percent-encode the value, and double-quote any individual industry containing a comma (exclude_organization_industry="Health, Wellness & Fitness"). See LinkedIn Industries for the full taxonomy.
Input a comma-separated list.
organization_slug?array<string>Filter by LinkedIn organization slug(s), the company-specific portion of a LinkedIn URL.
For https://www.linkedin.com/company/walmart/, the slug is walmart.
For https://www.linkedin.com/company/tesla-motors/, it's tesla-motors.
Exact match only. Generally more reliable than organization (no spelling/casing variation) and the only way to filter on names containing parentheses.
Fetch the full list of organizations (with their slugs) via /ats-organizations.
Input a comma-separated list.
exclude_organization_slug?array<string>Exclude LinkedIn organization slug(s). Same rules as organization_slug (exact match). Fetch slugs via /ats-organizations.
Input a comma-separated list.
organization_headcount_gte?integerFilter companies with at least this many LinkedIn employees (inclusive lower bound). Source: LinkedIn company profile (org_linkedin_headcount).
Combine with organization_headcount_lt for a range, e.g. organization_headcount_gte=50&organization_headcount_lt=500 for 50–499-employee companies.
organization_headcount_lt?integerFilter companies with fewer than this many LinkedIn employees (exclusive upper bound). Source: LinkedIn company profile (org_linkedin_headcount).
Combine with organization_headcount_gte for a range.
organization_size?array<>Filter by LinkedIn company-size bucket. Matches the org_linkedin_size response field. Input a comma-separated list.
employment_type?array<string>DeprecatedDeprecated — will be removed in a future version. Use ai_employment_type instead, which provides normalized, market-independent values now that every job is AI-analysed.
Filter by raw employment type(s) (overlap match, a job tagged with multiple types matches if any are in your list). Values are country-specific and vary by job board.
Input a comma-separated list.
ai_employment_type?array<>Filter by AI-derived employment type(s) (overlap match, a job tagged with multiple types matches if any are in your list).
FULL_TIME,PART_TIMECONTRACTOR,TEMPORARY,PER_DIEMINTERN,VOLUNTEER,OTHER
For raw, country-specific values use employment_type.
Input a comma-separated list.
ai_experience_level?array<>Filter by AI-derived experience level (years of experience required, inferred from the job description and other elements from the job page).
0-22-55-1010+
Pass multiple to broaden the match (e.g. 0-2,2-5). Input a comma-separated list.
ai_work_arrangement?array<>Filter by AI-derived work arrangement.
On-site- no remote at all.Hybrid- split between office and remote.Remote OK- fully remote, but an office is available.Remote Solely- fully remote, no office.
Pass multiple to broaden, e.g. Hybrid,Remote OK,Remote Solely for any-remote-flexibility roles. Input a comma-separated list.
ai_education?array<>Filter by AI-derived education requirements. The LLM is instructured to flag education that's required, preferred, or desired (overlap match, jobs are tagged with one or more requirements).
high schoolassociate degreebachelor degreeprofessional certificatepostgraduate degree
Note: Overlap match means bachelor degree matches jobs that explicitly require a bachelor's, it doesn't broaden to also match jobs that only require high school.
Input a comma-separated list.
ai_language?array<>Filter by the AI-detected language of the job description. Matches the ai_job_language response field. Input a comma-separated list.
ai_taxonomies_a_primary?array<>Filter by AI taxonomy/taxonomies. Similar to ai_taxonomies_a, but only matches the first (most relevant) taxonomy assigned to a job. Use when you want a tight category match, e.g. jobs that are primarily about Technology, not just adjacent to it.
Input a comma-separated list.
ai_taxonomies_a?array<>Filter by AI taxonomy/taxonomies (overlap match, jobs are tagged with one or more, ordered by relevance). The first taxonomy in the array is the primary taxonomy.
Matches a job if any of its assigned taxonomies are in your list (broad). For tighter matches use ai_taxonomies_a_primary (matches only the primary). To exclude taxonomies use exclude_ai_taxonomies_a.
Escaping. Percent-encode the value as you would any URL parameter - Management & Leadership becomes Management%20%26%20Leadership. Every HTTP client and SDK does this for you; only hand-written URLs need care, and an unencoded & will end the parameter early and return a 400.
Input a comma-separated list.
exclude_ai_taxonomies_a?array<>Exclude AI taxonomy/taxonomies - excludes a job if any of its assigned taxonomies are in this list. See ai_taxonomies_a for the value list and overlap-match semantics.
Input a comma-separated list.
ai_visa_sponsorship?stringFilter listings by AI-derived visa-sponsorship availability. Omit to include both.
only- return only listings that offer visa sponsorship.exclude- exclude listings that offer visa sponsorship (return only those that don't).
Note: Detection is based on language in the job description, not all companies are very clear about their requirements in the job description.
"only""exclude"has_salary?booleanSet to true to only return jobs that have salary information (raw or AI-enriched). Omit (or pass false) to include both.
has_no_location?booleanSet to true to return only listings with no normalized location set (i.e. locations_derived is null). Useful for surfacing jobs whose source feed didn't include structured location data, which would otherwise be missed by location-based searches. Omit (or pass false) to include all listings.
Note: combining has_no_location=true with location / location_advanced will always return zero rows, since the listings selected by has_no_location=true have no location text to match against. Don't combine them.
direct_apply?stringFilter listings by direct-apply availability. "Direct apply" means the candidate can apply within the source job board itself (e.g. LinkedIn's Easy Apply / one-click in-platform application) rather than being redirected to an external site. Omit to include both.
only- return only listings that support direct apply on the source job board.exclude- exclude direct-apply listings (return only those that redirect to an external apply flow).
Direct-apply listings have almost no overlap with the ATS feed (/active-ats), making them complementary rather than duplicates.
"only""exclude"exclude_ats_duplicate?booleanUse this only if you also consume /active-ats - when true it removes the majority of job board jobs we've matched against an existing ATS posting. Omit (or pass false) to include both.
How matching works. For each job board job - on all sources (linkedin, wellfound, ycombinator) - we run two checks against the ATS dataset:
- Job title + organization name + country match.
- Job title + LinkedIn company profile + country match.
If either check hits, the job is flagged ats_duplicate=true. If neither hits, it's ats_duplicate=false. Direct-apply listings (direct_apply=true) are not checked and are flagged ats_duplicate=null (these are also kept when this filter is true, since they're unlikely to be ATS duplicates by construction).
We aim for high precision over recall, so a small number of duplicates can still slip through. For full deduplication, add a fuzzy-match layer client-side.
linkedin_id?array<>Filter by one or more LinkedIn job posting IDs (comma-separated when passed as a raw URL). This is LinkedIn's public job ID - the digits at the end of a linkedin.com/jobs/view/{linkedin_id} URL - surfaced as linkedin_id in each response object. Distinct from id, which is the internal Fantastic.jobs ID.
id?array<>Filter by one or more internal Fantastic.jobs IDs. Matches the id field in each response object, the same identifier surfaced by /expired-jb for expiration tracking. e.g. id=8123456,8123457 returns those two specific jobs (useful for refreshing rows you already store). Distinct from linkedin_id, which is LinkedIn's public posting ID.
Input a comma-separated list.
Response Body
A list of active job board listings
application/jsonThe response is an array. Each item is an object with these fields.
| Field | Type | Description |
|---|---|---|
id* | integer | The job's internal ID. Used for expiration. Format int64 |
title* | string | Job title. |
organization? | string | Name of the hiring organization. |
organization_ | string | URL to the organization's page. Format uri |
organization_ | string | URL to the organization's logo. Format uri |
date_ | string | Date & time of posting. Format date-time |
date_ | string | Date & time of indexing in our database. Format date-time |
date_ | | | Date & time of the future expiry date. Format date-time |
locations? | array<> | Source-supplied location objects per the Google JobPosting schema (e.g. |
locations_ | array<string> | Normalized location strings. Geocoded. This is the field used for location search. |
location_ | | | To identify remote jobs: 'TELECOMMUTE' per the Google JobPosting schema. |
location_ | array<> | | Location requirement to accompany remote (TELECOMMUTE) jobs per the Google JobPosting schema. |
salary? | | | Source-supplied salary object per the Google JobPosting schema. Often partial or missing. For a normalized numeric breakdown use |
employment_ | array<string> | | Types like 'Full Time', 'Contract', 'Internship'. Usually a single value. For better accuracy, use |
url* | string | The URL of the job. Format uri |
source* | string | Source job board. |
source_ | string | For Value in "ats""jobboard" |
source_ | string | Domain of the job board. |
description_ | string | Plain text job description. Returned when |
description_ | string | Raw HTML job description. Returned when |
cities_ | array<string> | | All cities from |
counties_ | array<string> | | All counties from |
regions_ | array<string> | | All regions/states/provinces from |
countries_ | array<string> | All countries from |
timezones_ | array<string> | All timezones from |
lats_ | array<number> | Latitudes derived from |
lngs_ | array<number> | Longitudes derived from |
ai_ | | | Salary currency in ISO 4217 format. |
ai_ | | | Salary value when there is a single salary with no range. |
ai_ | | | Minimum salary in a range. |
ai_ | | | Maximum salary in a range. |
ai_ | | | Salary period: HOUR, DAY, WEEK, MONTH, or YEAR. Value in "HOUR""DAY""WEEK""MONTH""YEAR"null |
ai_ | array<string> | | Non-salary benefits mentioned in the job listing. |
ai_ | string | Years of experience required. Value in "0-2""2-5""5-10""10+" |
ai_ | string | Remote Solely (no office), Remote OK (optional office), Hybrid, or On-site. Value in "Remote Solely""Remote OK""Hybrid""On-site" |
ai_ | | | When Hybrid, the number of days per week in office. |
ai_ | array<string> | | When remote but restricted to a certain location, returns that location. |
ai_ | array<string> | | Derived remote location data matched with a location database (same as |
ai_ | array<string> | Key skills mentioned in the job listing. |
ai_ | | | Hiring manager name, if present. |
ai_ | | | Hiring manager's email address, if present. Format email |
ai_ | string | A 2-sentence summary of the job's core responsibilities. |
ai_ | string | A 2-sentence summary of the job's requirements. |
ai_ | integer | Required working hours. Defaults to 40 if not mentioned. |
ai_ | array<> | Employment type as derived from the job description. |
ai_ | string | Language of the job description. |
ai_ | boolean | True if the job description mentions visa sponsorship opportunities. |
ai_ | array<string> | Up to 5 taxonomies per job ordered by relevancy (e.g., Technology, Healthcare, Finance & Accounting). The first item in the array is the primary taxonomy and is what the |
ai_ | array<string> | Important keywords: technologies, tools, skills, certifications, industry terms, methodologies, programming languages. |
ai_ | array<> | | Explicitly mentioned educational requirements from the job description. |
org_ | string | Company-specific part of the LinkedIn URL (e.g., 'tesla-motors'). Unique per company. Always returned so jobs can be joined to |
org_ | integer | LinkedIn's internal company ID - the numeric identifier behind the company's LinkedIn page. Same value as Format int64 |
org_ | integer | Number of employees according to LinkedIn. |
org_ | | | Company's main website URL (sourced from LinkedIn). Format uri |
org_ | string | Employee count range according to the company. |
org_ | | | Company's slogan. |
org_ | string | Company's industry from LinkedIn's fixed list. |
org_ | | | Number of LinkedIn followers. Not populated for all companies. |
org_ | string | Company's HQ location. |
org_ | string | Company type (e.g., 'Privately Held', 'Public'). |
org_ | string | Company's founded date. |
org_ | array<string> | Company's specialties. |
org_ | array<string> | Full addresses of the company's locations. |
org_ | | | Description from the company's LinkedIn page. |
org_ | boolean | True if the company is a recruitment agency or job board (AI-identified). |
recruiter_ | | | Name of the recruiter who posted the job. Excluded when |
recruiter_ | | | Title of the recruiter. Excluded when |
recruiter_ | | | URL to the recruiter's profile. Excluded when Format uri |
seniority? | string | Seniority level as listed by the job board. |
direct_ | boolean | True if the job supports direct application on the job board (e.g. LinkedIn Easy Apply). |
no_ | | | True if the job board listing has no structured schema data. |
ats_ | | | True if this job is a duplicate of an ATS listing. |
linkedin_ | integer | LinkedIn's public job posting ID - the digits at the end of a Format int64 |
locations_ | array<> | Beta. Structured, geocoded breakdown of each derived location, powered by geocode.earth (Pelias). Returned only when |
curl --fail-with-body --silent --show-error 'https://data.fantastic.jobs/v1/active-jb?time_frame=24h&limit=1' \ --header "Authorization: Bearer ${FANTASTIC_JOBS_API_KEY:?Set FANTASTIC_JOBS_API_KEY}"[ { "id": 2465032259, "date_posted": "2026-11-13T01:49:49.488", "date_created": "2026-11-13T01:49:49.563158", "title": "Compliance Manager", "organization": "Thermo Fisher Scientific", "organization_url": "https://www.linkedin.com/company/thermo-fisher-scientific", "date_valid_through": null, "locations": [ { "@type": "Place", "address": { "@type": "PostalAddress", "addressRegion": "", "addressCountry": "", "addressLocality": "España" } } ], "location_type": null, "location_requirements": null, "salary": null, "employment_type": null, "url": "https://es.linkedin.com/jobs/view/compliance-manager-at-thermo-fisher-scientific-4488580538", "source_type": "jobboard", "source": "linkedin", "source_domain": "es.linkedin.com", "organization_logo": "https://media.licdn.com/dms/image/v2/D560BAQGe2HQP4zwTlA/company-logo_100_100/company-logo_100_100/0/1688649979581/thermo_fisher_scientific_logo?e=2147483647&v=beta&t=iwXfVsVoN3N55AbBLzgcXs3SjpF3H5asLBOKd8LqV3o", "cities_derived": null, "counties_derived": null, "regions_derived": null, "countries_derived": [ "Spain" ], "locations_derived": [ "Spain" ], "timezones_derived": [ "Europe/Madrid" ], "lats_derived": [ 39.3260685 ], "lngs_derived": [ -4.8379791 ], "seniority": "No corresponde", "direct_apply": false, "no_jb_schema": true, "ats_duplicate": true, "linkedin_id": 4488580538, "org_linkedin_slug": "thermo-fisher-scientific", "org_linkedin_id": 3081, "org_linkedin_headcount": 4, "org_linkedin_website": "https://www.thermofisher.com", "org_linkedin_size": "10,001+ employees", "org_linkedin_slogan": null, "org_linkedin_industry": "Biotechnology Research", "org_linkedin_followers": 2529963, "org_linkedin_headquarters": "Waltham, MA", "org_linkedin_type": "Public Company", "org_linkedin_founded_date": "", "org_linkedin_specialties": [ "Analytical Instruments", "Laboratory Supply Chain Programs and eCommerce", "Laboratory Equipment", "Lab Services", "Specialty Diagnostics", "Life Sciences", "Pharma Services", "and CDMO" ], "org_linkedin_locations": [ "168 Third Avenue, Waltham, MA, US" ], "org_linkedin_description": "About Thermo Fisher Scientific\nThermo Fisher Scientific Inc. is the world leader in serving science, with annual revenue of approximately $40 billion. Our Mission is to enable our customers to make the world healthier, cleaner and safer. Whether our customers are accelerating life sciences research, solving complex analytical challenges, increasing productivity in their laboratories, improving patient health through diagnostics or the development and manufacture of life-changing therapies, we are here to support them. Our global team delivers an unrivaled combination of innovative technologies, purchasing convenience and pharmaceutical services through our industry-leading brands, including Thermo Scientific, Applied Biosystems, Invitrogen, Fisher Scientific, Unity Lab Services, Patheon and PPD. \n\nFor more information, please visit www.thermofisher.com.\n", "org_linkedin_recruitment_agency_derived": false, "recruiter_name": null, "recruiter_title": null, "recruiter_url": null, "ai_salary_currency": null, "ai_salary_value": null, "ai_salary_min_value": null, "ai_salary_max_value": null, "ai_salary_unit_text": null, "ai_benefits": null, "ai_experience_level": "5-10", "ai_work_arrangement": "On-site", "ai_work_arrangement_office_days": null, "ai_remote_location": null, "ai_remote_location_derived": null, "ai_key_skills": [ "Clinical Compliance", "Clinical Auditing", "GxP Compliance", "Good Clinical Practice", "ICH E6", "Regulatory Compliance", "Root Cause Analysis", "CAPA Management", "Deviation Management", "Risk Assessment", "Impact Analysis", "Quality Assurance", "Audit Reporting", "Process Improvement", "Mentoring", "Cross-Functional Leadership" ], "ai_hiring_manager_name": null, "ai_hiring_manager_email_address": null, "ai_core_responsibilities": "Conduct and manage internal and external clinical audits, identify quality and compliance issues, determine root causes, and develop strategies to address findings. Report audit results, lead quality improvement initiatives, develop compliance tracking tools, and mentor staff while coordinating quality services across projects.", "ai_requirements_summary": "Requires a bachelor’s degree in life sciences, nursing, pharmacy, or a related field, plus at least five years of clinical research experience, including two years in clinical quality, GCP compliance, or a related role. Candidates should have strong knowledge of GxP regulations and clinical trials, experience with CAPA and deviation management, excellent communication and leadership skills, and familiarity with clinical quality systems; Veeva QMS experience is a plus.", "ai_working_hours": 40, "ai_employment_type": [ "FULL_TIME" ], "ai_job_language": "English", "ai_visa_sponsorship": false, "ai_keywords": [ "Clinical Compliance", "Clinical Research", "Clinical Development", "Quality Assurance", "Clinical Audits", "Internal Audits", "External Audits", "GxP", "Good Clinical Practice", "ICH E6(R2/R3)", "EMA", "MHRA", "FDA", "CAPA", "Root Cause Analysis", "Deviation Management", "Regulatory Guidelines", "Audit Reporting", "Risk Assessment", "Impact Analysis", "Quality Systems", "Veeva Vault", "TrackWise", "Veeva QMS", "Process Improvement", "Clinical Trials", "Technical Document Review", "Laboratory Audits", "Site Audits", "Compliance Management" ], "ai_taxonomies_a": [ "Healthcare", "Management & Leadership", "Science & Research", "Legal" ], "ai_education": [ "bachelor degree" ] }]