layiq
worthy; deserving; fitting; suitable.
A role, opportunity, or path that merits attention, time, and pursuit.
Loading LAYIQ…A Greenhouse job is still published when Greenhouse’s public job data lists it. Paste the Apply link from a boards.greenhouse.io or job-boards.greenhouse.io address to see whether the posting is listed and which date Greenhouse gives. The checker asks Greenhouse itself and does not read LinkedIn or Indeed.
When Greenhouse hosts an employer’s job board, the address has two parts. Greenhouse’s support page names them the root, given there as boards.greenhouse.io, and the job board token, “The customizable end part of the URL,” as in https://boards.greenhouse.io/omnivacorp.1 A job post under that board adds the job’s ID, and Greenhouse’s own example links read boards.greenhouse.io/vaulttec/jobs/127817.4 When we read the public job data for Greenhouse’s own job board on October 7, 2026, all 19 of its jobs were linked on job-boards.greenhouse.io, so you will see both hosts.7
| Link shape | What it is | Checker |
|---|---|---|
| boards.greenhouse.io/{board}/jobs/{id} | A job post on a Greenhouse-hosted board.14 | Reads it |
| job-boards.greenhouse.io/{board}/jobs/{id} | The same kind of post on the host Greenhouse’s own jobs use.7 | Reads it |
| …/embed/job_app?for={board}&token={id} | An embedded application address, with the board and job ID in the query. | Reads it |
| boards.eu.greenhouse.io or job-boards.eu.greenhouse.io | The hosts the checker treats as Greenhouse’s EU region. | Recognizes the link and says it cannot check it yet |
| company.com/careers?gh_jid={id} | A careers page on the employer’s own domain showing a Greenhouse job. Greenhouse says it adds the gh_jid parameter “between your root URL and job ID.”2 | Does not read it. Follow the page’s Apply button and paste that address. |
Jobs can also sit on the employer’s own domain, because Greenhouse offers “five integration options.” Some host the whole board, and others embed it or build it from Greenhouse’s data on the employer’s site.3 A gh_src parameter only tags where a click came from. Greenhouse says it tracks “a candidate’s sources through the source token parameter gh_src=.”2 Paste the whole address; the checker ignores tracking tags.
Greenhouse’s Job Board API gives “easy access to a simple JSON representation of your company’s offices, departments, and published jobs,” and “Job Board data is publicly available, so authentication is not required for any GET endpoints.”4 The checker asks for one job at a time at boards-api.greenhouse.io, using the board and job ID from your link.
| Field | What the documentation shows | How the checker uses it |
|---|---|---|
| id | “The id field contains the unique identifier for the job post, while internal_job_id contains the unique identifier for the job itself.”4 | Matches it to the number in your link. |
| first_published | A date in the job’s data.4 | The posting date it shows, and the basis for the age signal. |
| updated_at | A second, separate date field in the same data.4 | Not used as a posting date, because it is a different field. |
| requisition_id | A requisition number, in the example data.4 | Not shown. If a job page prints one, use it to search the careers page. |
| application_deadline | A deadline date, in the example data.4 | Not shown today. Read the job page for a closing date. |
Greenhouse separates a job from its post. Its support pages say “There are two job post statuses: Live and Offline,” and that a job status and a job post status “are different statuses.”5 Closing a job “un-publishes the job’s job posts from all of your organization’s job boards.”6 An Offline post is “not visible on any job boards, even though the job itself may be open and the hiring team may be actively interviewing candidates to fill it.”5
That is what lies behind the checker’s answer “The employer’s system no longer lists this job.” Greenhouse’s job data for the employer was reachable, but this posting was not in it. The answer does not say whether the role was filled, put on hold or has only had its post turned off. Greenhouse names one more reason for turning a post off, that the hiring team “doesn’t want to receive additional applications,”5 so a missing job is a question to ask the employer.
A job on the board is not proof of hiring either
The checker confirms that a post is published in Greenhouse’s data. It cannot see whether the team is reviewing applications. Our guide on how to tell if a posting is still open covers the steps after the check.
The checker shows the first_published date as the posting date and works out the age from it. The age signal follows the rule on the main checker page: “Under six months, age alone does not change the result. Past six months it is marked worth a second look.”9 A Greenhouse job first published eight months ago would read “Posted over six months ago,” with a prompt to ask the employer.
Greenhouse’s data keeps first_published and updated_at as two dates,4 and so does the checker. It does not use updated_at as the posting date, so an edited job does not look newly posted. If a job page shows a different date, compare the two and ask the employer which one it means.
Open the board’s own address, the root plus the token, such as boards.greenhouse.io/omnivacorp.1 The board is the employer’s list of published jobs.4 Search the list for the title. A job that is on the board is published, and a job that is not there is not, whatever a job site still shows. Then search the employer’s careers page for the same title, using the requisition number if the posting prints one.
It is a parameter Greenhouse adds to a job post’s address on an employer’s own careers page. Greenhouse says it adds gh_jid “between your root URL and job ID.”2 The number after it is the job post’s ID, which is also the number in a boards.greenhouse.io link.
Greenhouse separates the post from the job. A post set to Offline stops showing on job boards “even though the job itself may be open,” and “any links to the post stop working.”5 Ask the recruiter whether the role is still being filled.
It dates the post in Greenhouse’s data, which is not the same as the whole hiring effort. The data has a separate updated_at field.4 Use the date to judge the post’s age and ask the employer about the role.
Only the page itself, and only if the site allows it. For an address on the employer’s domain, the checker first reads the site’s robots.txt and, if it may, reads the page’s own job details, which are weaker evidence than Greenhouse’s data. For Greenhouse’s own answer, paste the boards.greenhouse.io or job-boards.greenhouse.io address the page’s Apply button leads to. Either way it also looks for the job among the openings LAYIQ lists.
Not yet. It recognizes boards.eu.greenhouse.io and job-boards.eu.greenhouse.io links and says it cannot check them. The result never counts against the job.