methodology
how tensor hack curates the index
Linked sources, visible freshness and a tiered publishing policy. Automation collects official and platform records; people review public submissions and editorial features.
Every public record needs a usable source. How it reaches the index depends on the source tier; automated ingestion is not described as human review.
Read why the index exists, send a new listing through the submission queue, or report a stale field through the distinct correction form.
Site-wide full audit completed on . The date is advanced manually only after a completed audit. It is not generated at build time and does not imply that every listing had a human review on that date.
source tiers
- 01 · official
- Official APIs and company ATS feeds may auto-ingest after normalization and safety checks.
- 02 · platforms
- Reputable event platforms may auto-ingest with source-health monitoring and duplicate control.
- 03 · public submissions
- A listing sent through the public form stays in the review queue until an operator decides whether to publish it.
- 04 · editorial
- Features, picks and comparison judgments require a human decision. They are not generated from an automatic score.
publication line
what a live listing means
It means the record passed the policy for its source tier and links out to the source used by the index. It does not mean Tensor Hack contacted the organizer, employer or funder.
A “source checked” or “link checked” date should appear only when a stored timestamp supports it. Missing salaries, prizes, dates and verification events stay missing rather than being inferred.
Registration, applications, funding decisions and payouts happen on the external source. Tensor Hack is the index, not the program administrator.
01 · normalization
what automation does
Official and platform records are normalized into comparable fields. Source safety, duplicates and connector health are checked before the result can be treated as current inventory.
Automation supplies breadth and repeatability. It is not evidence of a person reading each record.
02 · freshness
how listings leave
Confidently past deadlines leave live boards unless the direct source shows an extension. An authoritative 404 or 410 can close a dead link; a timeout, DNS failure, bot wall or server error stays unknown rather than becoming proof that the opportunity ended.
Source-health monitoring records whether a connector is healthy, degraded, failed or stale.
03 · corrections
report the exact field
A correction report needs the listing or direct-source URL, the field that looks wrong and a contact email for follow-up. Reports enter a review queue as corrections; they do not publish new listings.
Open the correction form. There is no promised response time; source-backed changes are updated or the listing is removed when the evidence supports that action.
04 · limits
what the index does not promise
Tensor Hack does not guarantee availability, prize payments, hiring outcomes, judging, organizer behavior, eligibility or team fit.
Always read the current source rules before acting, especially payout timing, IP terms, location, eligibility and required technology.
curator
Manav Gupta (tensorboy)
Role: curator. Manav reviews public submissions and corrections, and makes editorial feature and comparison decisions. Official and platform feeds may be auto-ingested under the published source-tier policy.
x.com/tensor___boy · instagram.com/tensor._.boy · linkedin.com/in/--manav-gupta--
Business inquiries: manav.tensorboy@gmail.com