Frequently asked questions
What is ats.fyi?
ats.fyi is a startup job feed that pulls open roles directly from company ATS pages and normalizes them into one searchable stream.
Where do the jobs come from?
Listings are scraped from public job boards on Ashby, Lever, Greenhouse, and Workable. We only index roles that are currently visible on those sources.
How often is the feed refreshed?
The scraper runs on a recurring schedule and updates active jobs throughout the day. Stale roles are automatically marked inactive when they disappear upstream.
Do you host applications on ats.fyi?
No. Every role links out to the employer's original application page so candidates always apply at the source.
How do you decide if a role is active?
A role is active when it appears in the latest scrape output for that company. If a posting is no longer returned, it is deactivated in our feed.
Why are some salaries missing?
Many employers do not publish compensation in their ATS listing. We only show compensation when we can extract a reliable range.
How is location labeled?
Location labels come from the source posting and are normalized into remote, hybrid, onsite, and region groupings when possible.
What does the VC backer filter mean?
The VC filter tags companies based on portfolio/backer data in our company dataset, so you can narrow roles to selected investor ecosystems.
Can companies request edits or removal?
Yes. If a job is inaccurate or a company should be excluded, contact us and we can correct the source mapping or suppress the listing.
Do you rank jobs by sponsorship or payment?
No paid placement is used in the core feed ordering. Jobs are sorted by recency and filter relevance.
Do I need an account to browse?
No signup is required for browsing. The site is intentionally lightweight and public.
How can I track newly posted roles?
Use the RSS feed at /feed.xml and weekly drops page to monitor recently active roles without manually checking every company board.
Why might I see duplicate-looking roles?
Some companies publish multiple openings with near-identical titles across teams or locations. We also run dedupe safeguards, but legitimate variants remain separate.
Is historical data kept forever?
We keep core job and company records for analytics and quality checks, while active status reflects the latest observed source state.
How do you handle failures in cron jobs or external APIs?
Cron routes are environment-guarded and return explicit error payloads when secrets or API keys are missing, instead of failing silently.