Consent-first talent profiles
Students must explicitly activate a profile and control whether they are private, LerenGO-only, visible to verified recruiters, or available through a public link.
Opt-inPrivacyVisibility
HunterGO
Get discovered through skills, projects, and proof.
HunterGO is the verified talent layer of LerenGO. It should help opportunity owners find student builders through evidence from the platform, not through a generic resume database.
Foundation
HunterGO starts with privacy, not job-board volume.
This surface establishes the talent-discovery model without rendering fake candidates, fake companies, or inflated placement claims. Published opportunities are backend-backed.
Proof-first discovery
Candidate cards should lead with SkillGO certificates, ForgeGO projects, CampusGO validation, and approved MentorGO signals where privacy allows.
SkillsProjectsValidation
Verified recruiter workflow
Recruiters need company verification, invite quotas, shortlists, opportunities, and pipeline state before they can reach students at scale.
VerificationShortlistPipeline
Published opportunities
Opportunity discovery without exposing private talent.
These entries come from `hunter_opportunities`. Candidate search remains gated to verified recruiters and opt-in talent profiles.
Backend state
HunterGO schema is not applied yet.
Apply web/supabase/module_expansion_schema.sql before using HunterGO talent, recruiter, opportunity, and admin workflows.
Verified discovery is the product. Spam prevention is not optional.
- Private talent profiles must not appear in search.
- Unverified recruiters must not access broad candidate discovery.
- Candidate contact details stay hidden until the student allows access.
- Recruiter notes remain private to the recruiter/company side.
Pipeline lifecycle
Opportunity progress must be clear to both sides.
Recruiter-facing pipeline notes and candidate-visible status need separate fields. A candidate should never see private recruiter notes.
invitedinterestedappliedscreeninginterviewofferhiredrejectedwithdrawn
Next build step
Build opt-in profiles before recruiter search.
The next slice should add HunterGO schema, private-by-default talent profiles, recruiter onboarding, and admin verification. Search should come after privacy rules are enforced.