EMPLOYER USE CASE · SKILLS-BASED HIRING & ONBOARDING
Bring job requirements, candidate examples, and human review into a clearer hiring process—then carry the relevant, agreed context into onboarding.
An illustrative scenario, not a completed customer deployment or measured hiring outcome. This page describes intended capabilities at different stages of development. See current product availability.
Imagine a company hiring an operations coordinator. An applicant’s previous title looks different, but their examples show relevant scheduling, customer communication, and handoff experience.
The hiring conversation also identifies a system they have not used. If hired, they will need time and support to learn it. That context should inform the first assignment rather than disappear when recruiting ends.
01 · DEFINE THE WORK
The hiring team describes the responsibilities, expected outputs, and working conditions. They distinguish requirements needed at entry from capabilities the organization can help someone develop.
What will the person actually need to do?
What examples would help reviewers assess preparation?
What can someone learn after joining, and who will help?
A role Profile could organize these expectations so applicants and reviewers work from a clearer starting point.
02 · INVITE EXAMPLES THAT EXPLAIN CAPABILITY
The applicant describes a situation where they coordinated deliveries, resolved a scheduling conflict, and kept customers informed. They clarify their own role and the support they received.
TalentPass is intended to help people organize selected professional experience. Pythia could guide a relevant account, with the applicant reviewing its accuracy and choosing what to share.
An applicant should have a clear way to ask questions and provide relevant context. Missing documentation is not automatically missing capability.
Connect what was learned about the person with what they need to begin the work.
03 · REVIEW EVIDENCE IN CONTEXT
Reviewers compare the examples with the role requirements and ask about scope, decisions, and results. They distinguish the applicant’s account, supporting records, and their own assessment.
A Learning and Employment Record may support a particular learning, credential, or experience claim. Any supported verification method establishes only what that method checks; it does not prove every aspect of job readiness.
TalentSync’s intended role is to connect requirements with relevant candidate context for human review. This scenario does not propose automatic ranking, rejection, or hiring decisions.
04 · AGREE WHAT SHOULD CARRY FORWARD
If the person is hired, the organization and new employee clarify which information is relevant to onboarding and who needs it. The hiring team identifies confirmed expectations, preparation needs, and support commitments.
Relevant experience and the responsibilities agreed for the role.
Learning time, introductions, resources, and the person responsible for help.
Areas needing clarification or observation during the first assignments.
Passport Pages are intended to support purposeful exchanges. Access, retention, correction, and any transfer between systems must be defined for the implementation. Private reflections, unrelated information, and recruiting assessments should not automatically become a team-wide profile.
05 · BUILD THE FIRST ASSIGNMENT AROUND REAL NEEDS
The manager gives the new employee a bounded coordination task and pairs them with a colleague to learn the internal system. They agree on the expected output, review step, and where to ask for help.
The plan recognizes the employee’s prior experience without assuming it transfers perfectly. It also avoids making them repeat learning solely because earlier experience was overlooked.
Intended TalentSync capability views could help organize development questions, but the manager still needs to confirm the task is appropriate and support is available.
06 · REVIEW THE FIRST EXPERIENCE
At a check-in, the manager and employee discuss what went well, where the system training helped, and what needs another supported attempt. They adjust the plan using actual work examples.
The employee can clarify or correct earlier information. An interview interpretation should not become a permanent label that follows someone unquestioned.
Learning and Employment Records can carry information about learning, credentials, experience, and achievements. Their value here is supporting specific questions about preparation and development across the hiring-to-onboarding transition.
Gobekli’s Human Intelligence Layer is intended to connect those records with what people can explain and what the work requires. TalentPass brings the individual perspective; TalentSync connects it with organizational needs; Passport Pages support selected exchanges.
This does not replace the organization’s hiring procedures, required checks, assessments, or onboarding responsibilities. System connections and available workflows need to be confirmed before implementation.
Did applicants and reviewers understand the role criteria?
Could reviewers explain their assessment using examples and visible uncertainties?
Did appropriate context and agreed support reach the onboarding owner?
Did the first assignments and check-ins address the needs identified?
These are questions for a scoped engagement, not measured customer results. Faster hiring, reduced bias, retention, or productivity improvements are not guaranteed.
Describe the actual work and what preparation it needs.
Clarify what applicants can provide and how reviewers should use it.
Connect starting responsibilities with learning and support.
The examples and preparation needs discussed in hiring can help shape an appropriate first assignment. Only relevant information should carry forward through an agreed sharing process.
Not by themselves. A record supports a particular claim. Reviewers still need to examine relevance, context, and any further assessment or checks required for the work.
This scenario does not propose automated ranking, rejection, or selection. Intended views support accountable human review of requirements and evidence.
No. The scenario calls for a defined handoff of relevant context. Recipients, access, retention, and correction arrangements need to be agreed rather than copying the full application by default.
Any connection depends on the current capabilities, supported sources, and agreed implementation. This page does not promise a seamless integration with every system.
Choose one role. Clarify the criteria, useful candidate examples, review responsibilities, onboarding handoff, and first-assignment support. Then evaluate the transition before expanding it.
Start with one role, relevant evidence, and a clear handoff into the work.