Question 1

Can I try the data before licensing it?

Accepted Answer

Yes. The job search, map and analytics dashboard at aylagov.com run on this dataset and are free to use. Delivery as files adds per-posting detail, closing history, and your format.

Question 2

How fresh is the government job data?

Accepted Answer

We sweep every source nightly and retire expired postings automatically. Each job also carries the day we first saw it and the day we last confirmed it, so you can filter on freshness yourself rather than trusting a number on a marketing page. That is a different animal from quarterly survey data.

Question 3

Why license this instead of scraping it ourselves?

Accepted Answer

Because the valuable half is the history, and history cannot be backfilled. Every posting has been re-checked nightly since 2025-12-07 and kept after it closed, so the record knows when a role appeared, when it vanished, why it ended, how long that employer typically leaves a job open, and whether their hiring is rising or falling. A scrape started today begins at zero on all of it. The other half is classification: twenty employer types, occupational series read as series rather than titles, hourly salaries stored as hourly, and non-jobs and scraper artifacts removed before anything reaches you.

Question 4

How do you handle the same job posted in several places?

Accepted Answer

A single role often runs on a state portal, the agency's own site and a contractor's careers page at once. We flag the copies and point them at the original rather than deleting them, so a headcount query returns positions instead of postings — and you can still see everywhere it ran.

Question 5

How is this different from a general labor-market tool?

Accepted Answer

General labor-market tools cover every industry. Ayla covers only government and government-contractor hiring, collected at source level from the official job boards themselves, and keeps the public-sector fields that matter: federal occupational series, pay plan, grade, employer type, and the security-clearance signal. We also keep postings after they close, so the closing history is part of the record rather than something that ages out.

Question 6

Do you sell candidate profiles or resumes?

Accepted Answer

No, and we don't plan to. This is jobs and employers only. Recruiter names and contact details that appear in a posting are stripped before the data reaches you.

Question 7

What does it cost?

Accepted Answer

Not set yet — this is a waitlist, not a product on sale. The waitlist gets a sample slice of the schema above, first access, and founding pricing when delivery opens.

Field	Type	Fill
title	text	100%
employer	text · fk	100%
employer_type	enum(20)	100%
apply_url, source_url	url	100%
posted_date	date	99%
pay_grade, job_series	text	98%
state	text	94%
city	text	55%
description	text	73%
salary_min, salary_max	numeric	35.3%
annualized_pay	numeric	35.3%
pay_period	enum	35.3%
close_date	date	29%
clearance	text	3.6%
job_family, seniority	enum	—
employment_type	enum	—
work_arrangement	enum	—
requirements	text	—
first_seen	date	100%
last_seen	date	100%
expiry_reason	enum	—
is_duplicate, duplicate_of	bool · fk	100%

Field	Type	Fill
name	text	100%
employer_type	enum(20)	100%
headquarters	text	—
sub_agencies	array	—
open_jobs	int	100%
job_families	array	—
median_posted_pay	numeric	—
postings_to_date	int	100%
share_closed	pct	100%
median_days_open	int	—
posting_trend	series	100%

Source	What it covers
Public government data	Federal agencies, all 50 states and the territories, cities, counties, school districts, transit authorities and other public bodies.
Proprietary sources	Government contractors and public-sector employers whose openings never appear on a public government portal.

A daily record of who government is hiring.

Schema

Job

Employer

Sources

Delivery

Waitlist

Questions

Book a call