Recruiting: one portal for JDs, scorecards, sourcing & scheduling
Get hiring managers and interviewers on the same page. Centralize JDs, rubrics, scorecards, outreach templates, sourcing lists, dashboards, and loops—kept current, searchable, and governed.
TL;DR: Workspace per role/funnel → tags for role, seniority, stage, region, asset, owner, sensitivity, status → import canonical links → publish candidate & internal portals → enforce SSO/SAML & audit.
Common pain points
- JDs, scorecards, rubrics, and loops scattered across docs and ATS notes.
- Inconsistent interviewer prep; outdated take-homes and questions.
- Sourcing boards and outreach templates live in personal systems.
- Scheduling links and pipeline dashboards hard to find quickly.
How Linkinize helps
- Role portals for interviewers & hiring teams (read-only, current).
- Candidate pages with timelines, resources, and FAQs.
- Tag taxonomy for role/stage/region/seniority/asset/status.
- SSO/SAML + audit to protect confidential materials.
How it works (5 steps)
- Create a workspace per role (e.g., role:backend-eng, region:emea, seniority:sr).
- Define tags:
role:eng|design|sales|ops,seniority:jr|mid|sr|lead,stage:sourcing|screen|onsite|offer,region:emea|na|apac,asset:jd|rubric|scorecard|sourcing|sequence|dashboard|policy,owner:recruiting|hm|coord,sensitivity:public|internal|confidential,status:approved|draft|deprecated. - Import canonical links (JDs, scorecards/rubrics, interview loops, scheduling, sourcing lists, outreach templates, pipeline/DEI dashboards, policies).
- Publish candidate-facing and interviewer portals via Public Pages; keep PII and feedback inside your ATS.
- Enforce SSO/SAML, set owners and review cadence, and audit monthly for stale content.
Integrations you’ll likely use
Link to the single source of truth—permissions remain enforced where content lives.
- ATS: Greenhouse, Lever, Ashby, Workable
- Scheduling: Calendly, GoodTime, Google Calendar
- Assessments: CoderPad, HackerRank, Codility, Loom
- Sourcing: LinkedIn, Indeed, Wellfound, Gem, SourceWhale
- Docs & Policies: Notion, Confluence, Drive/SharePoint
- eSign/Offers: DocuSign, Ironclad, Adobe Acrobat Sign
Starter taxonomy (copy & adapt)
Role & Seniority
- role:eng · role:design · role:sales · role:ops
- seniority:jr · seniority:mid · seniority:sr · seniority:lead
Stage & Region
- stage:sourcing · stage:screen · stage:onsite · stage:offer
- region:emea · region:na · region:apac
Assets, Ownership & Governance
- asset:jd · asset:rubric · asset:scorecard · asset:sourcing · asset:sequence · asset:dashboard · asset:policy
- owner:recruiting · owner:hm · owner:coord
- sensitivity:public · sensitivity:internal · sensitivity:confidential
- status:approved · status:draft · status:deprecated
Common questions & objections
“We already have an ATS.”
Perfect—keep it. Linkinize is the front door that unifies JDs, rubrics, scorecards, sourcing, and scheduling into one governed portal.
Perfect—keep it. Linkinize is the front door that unifies JDs, rubrics, scorecards, sourcing, and scheduling into one governed portal.
“Will candidates see internal documents?”
No—publish a minimal, candidate-facing Public Page. Keep internal rubrics and scorecards in private workspaces with SSO/SAML.
No—publish a minimal, candidate-facing Public Page. Keep internal rubrics and scorecards in private workspaces with SSO/SAML.
“Another tool to maintain?”
You save canonical URLs; content stays in ATS/docs/sourcing tools. Portals auto-update as links change.
You save canonical URLs; content stays in ATS/docs/sourcing tools. Portals auto-update as links change.
“Privacy & compliance?”
Linkinize stores links and metadata only. Keep PII in your ATS. Enforce least-privilege roles and audit logging.
Linkinize stores links and metadata only. Keep PII in your ATS. Enforce least-privilege roles and audit logging.
Faster hiring, consistent interviews
Recruiting teams use Linkinize to align hiring managers, interviewers, and coordinators—everything current in one place.
- • One hub for JDs, rubrics, scorecards, loops & scheduling
- • Candidate-facing and internal portals
- • SSO/SAML, roles, and audit logging
- • Works with Greenhouse/Lever/Ashby, Calendly/GoodTime
Frequently Asked Questions
- Do we store resumes or feedback in Linkinize?
- No—keep PII and evaluations in your ATS. Linkinize stores links/metadata only and honors source permissions.
- Can interviewers access only their loop?
- Yes—scope portals by role/stage and use viewer roles. Keep score entry inside the ATS.
- How do we keep rubrics current?
- Tag with
status:approved, assign owners, and set areview:quarterlycadence. Archive deprecated versions.