How jobs qualify for GTM Vibes

Selection rules

Source postings first pass title and duty checks for go-to-market scope and substantive AI work. A model then reads the role duties and returns one of four decisions. Only A and B decisions publish.

A role marked “light” only asks for AI-assisted productivity or general fluency. “No” means the work falls outside the board. Neither decision publishes.

What stays out

• Company or product descriptions that mention AI without AI duties in the role.
• Quota-carrying sales, account management, customer success, and support roles.
• Forward-deployed, solutions, sales engineering, and customer deployment roles.
• Unrelated engineering, research, design, recruiting, finance, legal, and people roles.
• General AI fluency, drafting, or research with no owned AI workflow or system.

The title prefilter can also exclude internships, coordinators, assistants, and roles whose title places them outside the board's go-to-market scope.

How models assist

Deterministic rules create a candidate set. A language model applies the A, B, light, or no rubric to each new candidate. The final A or B decision is stored with a short evidence excerpt in private feed state.

The model also drafts a one-sentence public summary. Automated checks reject long copy, copied passages, hype language, repetitive openings, and list-like summaries. The original employer posting remains the application source.

Model output can be wrong. The published criteria and correction route make those decisions reviewable; a badge is a classification, not an employer endorsement.

Sources, dates and unknowns

The feed reads public postings from supported employer applicant-tracking systems. It keeps the employer posting URL and stable source identity. Public listing text is an editorial summary, not a copy of the complete posting.

Employer publication dates and deadlines are accepted only from source fields with that meaning. Discovery time, last-seen time, and an adapter update timestamp have different meanings. One is never substituted for another in the source-fact record.

Employment type, physical location, remote applicant eligibility, and compensation remain absent when the source does not support them. Missing compensation does not mean the employer withheld it; we label missing pay “Salary not listed.” A display location also does not prove remote eligibility.

“Added to GTM Vibes” is the first date we observed a role, not its employer publication date or proof that it is newly posted. Lists sort by that date, newest first, with a stable job-ID tie-break. Legacy records without it use a separately labeled “Listing date”; unknown dates sort last. “Posted by employer” remains a separate source fact.

Freshness and closure

A successful source check updates the last-confirmed date. The site uses a separate verification cutoff, currently seven days after that check for feed records. At build time, confirmed closure, a passed employer deadline, or a passed verification cutoff removes the role from active pages.

A failed source request does not prove that an employer closed a role. The publication system keeps failure evidence separate from closure evidence. Because the site is static, a delayed publication can leave the live page behind the repository state. Confirm availability on the employer page before applying.

Corrections

Email [email protected] with the GTM Vibes URL, the employer URL, and the specific field that needs review. We compare the report with the employer source and preserve uncertainty when the source does not settle the question.