01 / source
Observation comes first
A listing begins as a source observation: a posting retrieved from an employer or applicant-tracking-system page. We preserve the source URL and the observed listing fields used by the public read path.
Methodology / public data boundaries
Read the signal. Keep the caveat.
This is how NextGen Energy Jobs describes source observations, freshness, market figures, and classification uncertainty.
Current implementation noteReviewed 22 September 2026
02 / freshness
Freshness is time-bounded
Public job reads use source status and observed timestamps. An active listing is not a promise that the employer is still hiring, and a missing observation is not by itself proof that a vacancy has closed.
03 / uncertainty
Uncertainty stays visible
When evidence is thin, contradictory, or incomplete, the safe outcome is review or abstention. We do not turn a broad keyword, employer name, or model confidence into a public quality badge.
What the public site means today
A listing is not a market census.
Search results and market pages summarize the listings available to the current public read path. They are useful for discovery, but they are not a complete count of every power-system vacancy, employer, or geography.
Scope
The product focuses on work connected to the modern power system: generation, grid infrastructure, storage, critical facilities, power equipment, markets and controls, and related renewable work. Generic climate, software, corporate, or sustainability work is not automatically in scope.
Source and provenance
Source facts, normalized fields, and derived labels are different things. A title, employer, salary field, location, or application link should be read as information supplied or observed from a source, not as an independent verification by NextGen Energy Jobs.
Classification
The target classification model separates system segment, asset or technology, occupation, discipline, seniority, and work setting. Evidence should come from the job itself. Ambiguous work can be sent to review or left unclassified rather than forced into a category.
Identity and duplicates
A source posting and a real vacancy are not always one-to-one. Reposts, reopened roles, source-ID reuse, and syndication require evidence-backed identity decisions. Until that graph is the public read source, listing counts are posting counts rather than deduplicated vacancy counts.
Freshness and cadence
Observed recently is not the same as guaranteed live.
Scraper runs, employer changes, provider outages, pagination, caching, and revalidation all affect when a change becomes visible. Public pages may therefore lag the source or retain a listing briefly after an employer changes it.
Current listing and salary views use the legacy public data path and its active/status and observed-time fields. A timestamp is evidence of when our system observed a source record; it is not an employer confirmation, an expiry guarantee, or a promise of complete source coverage.
We avoid treating one failed or incomplete crawl as proof that all previously seen jobs disappeared. When you are ready to apply, confirm the role, requirements, and application details on the linked source or employer page.
Classification and review
A label should be earned by evidence.
Classification is intended to separate system segment, asset or technology, occupation, discipline, seniority, and work setting. A role may carry several supported labels while retaining a primary segment and occupation.
Clear evidence can be accepted. Thin or conflicting evidence can be marked for review. If evidence is insufficient, the safe result is abstention; a source posting is not forced into a category simply because a word appears in an employer name or a broad description.
These are quality-control states, not employer endorsements. Classification confidence should not be read as a public claim that a role is better, more verified, or more suitable.
Accepted
The available job evidence supports a controlled concept.
Review or abstain
The evidence is ambiguous, incomplete, or not strong enough to publish as a confident label.
Method changes
Changes remain dated and inspectable.
23 September 2026
Public search language now describes source observations and posting counts instead of claiming a deduplicated live vacancy census. Raw cross-currency salary bands are withheld from search until annual compensation normalization is available.
Canonical graph work
Versioned taxonomy, provenance, identity, classification, and freshness foundations are being built in parallel. They do not become public facts until backfill, shadow comparison, review, and cutover gates pass.
Corrections and questions
See a stale, incorrect, or misleading listing?
Send the listing URL, the field that needs correction, and the source or evidence you are relying on. We can investigate source status, freshness, attribution, or a classification boundary.