Ntern
Source and Correction Policy
Ntern distinguishes employer-controlled evidence from community reports, preserves attribution, and gives applicants and employers a clear correction path.
What enters the catalog
Ntern covers technical internships, co-ops, apprenticeships, new-grad programs, and roles explicitly described as entry level. A role must lead to an employer-controlled or authorized application destination. The service does not copy full job descriptions into its catalog.
Source labels
- Employer submitted means a currently verified employer supplied the structured catalog facts and official application destination. It does not mean the employer paid for placement or controls ranking.
- Employer posted means a reviewed employer-controlled careers page or applicant-tracking-system board currently supports the listing.
- Source reported means a reviewed public community list reported the role, but Ntern has not established a current direct employer feed for that occurrence.
- Corroborated means more than one qualifying source supports the same application destination.
Provider timestamps remain labeled as employer publication or update times. “Found by Ntern” means the time this service first observed the role and is never presented as an employer publication time.
Source admission and monitoring
Ntern does not use a closed, preferred, or prestige-based employer roster. Any company-controlled Greenhouse, Lever, or Ashby board can be accepted for direct monitoring when it passes the same verification process. Company size, funding, brand recognition, and an existing relationship with Ntern are not admission requirements.
Verification requires evidence connecting the exact board or tenant to an employer-controlled careers surface, a validated official application host, successful complete snapshots, quality review, and a quiet baseline before alerts begin. Admission of a board does not guarantee publication of every posting; individual roles must still fall within the technical early-career scope described above. Community sources must be openly available, attributable, and permitted for the project’s bounded access. Failed or suspicious snapshots do not close roles or publish partial data.
An explicitly configured trusted community source may supply the employer name when Ntern cannot yet resolve a canonical employer, but only after the role leads to a validated posting-specific destination and passes the same metadata and safety checks. This keeps the Source reported label and does not confirm posting identity, merge similar roles, or create an employer alias. Trusted-source alerts remain disabled until a separate reviewed policy activation; identity-unconfirmed roles then require two consecutive complete snapshots with the same occurrence and destination.
A verified employer may propose field-level metadata or submit structured role facts without a full job description. Missing or exactly matching facts may receive employer co-attribution; conflicts with explicit official evidence stay unchanged until a reviewer records why an override is justified. Direct submissions pass the same relevance, destination, duplicate, freshness, and organic ranking rules as other roles. Verification expires after 180 days, and trust failures can suspend publishing or quarantine affected roles.
To suggest a company board, open a GitHub issue with the company name, official careers page, and exact Greenhouse, Lever, or Ashby board URL.
Attribution and reuse
Role details identify their source class and link to the official application destination. Source-review evidence is preserved in repository history so decisions can be audited. Ntern-created catalog metadata may be reused under CC BY 4.0 with attribution to Ntern. Employer-authored text, third-party list content, logos, and trademarks are excluded from that permission.
Request a correction or removal
For a non-sensitive correction, open a GitHub issue with the company, role URL, requested change, and supporting first-party link. For a private, safety-sensitive, or personal-data concern, email [email protected]. Do not place personal information in a public issue.
Ntern targets acknowledgment within two business days and resolution within seven business days. A listing that presents a credible fraud, malware, personal-privacy, impersonation, or applicant-safety concern will be hidden promptly while reviewed. Other disputes may remain visible with corrected labeling when evidence is incomplete.
How corrections are decided
First-party employer evidence is preferred. Ntern checks source ownership, current listing state, destination safety, role identity, and whether the requested edit changes a fact or an opinion. Corrections create new reviewed evidence; prior public evidence remains in Git history unless retaining it would itself create a privacy or safety problem.