How MySkillsSpace works
Start with a simple conversation, or send one structured invitation: the role, your message, a pipeline of named stages and any assessments. The candidate reads every condition before saying yes, and both sides follow one timeline.
These are not two versions of one button. A message is how you talk; an invitation is how you run a process. Use whichever the moment calls for.
A direct conversation, without opening any process.
Good for
A message is just a message. It does not enter anyone into a recruitment process, assign assessments or create any obligation.
One structured invitation: the role, your terms, your message, a pipeline of stages, and assessments when they add value.
Good for
The invitation stays open for 30 days, and attached assessments share that deadline. You can withdraw it any time before it is answered; a candidate can withdraw from a running process at any point.
Message when you want to talk. Invite when you are ready to run a structured process.
Every recruitment runs on a pipeline: a short sequence of stages the company names in its own words. The candidate sees the whole sequence before accepting, and every move lands on a timeline both sides can read.
Invitation, assessments, review, interview, offer or custom. The company writes the label; the type decides how the stage completes.
An assessment stage closes itself when every required result is in, including a verified skill the candidate already holds. Review, interview and offer move only when a person moves them.
Sent, opened, accepted, started, submitted, moved, noted, decided. The candidate reads their own history; internal notes and reasons stay with the company.
A candidate can withdraw at any point. It ends the process as a withdrawal, never as a rejection, and the company hears it at once.
The structured path in three moves: what each side does, and what each side sees.
Role, terms and a personal message in one place. Pick one of your pipelines or keep the standard sequence, search the assessment catalogue, mark each pick required or optional, and watch the candidate's total time as you choose. If a valid public verification already covers a skill, the composer says so.
The candidate reads who is asking, the role, your message, every stage, each assessment with its length, who will see the results, that integrity signals go to a reviewer and never reject anyone, and the deadline. Accepting starts the process. It never starts an assessment.
Each completed assessment updates the process for both sides, and the assessment stage closes itself when the last required result lands. You move the candidate through review and interview, leave internal notes, and end with hired or not selected. Nothing is ever decided for you.
The three states one skill can be in, and the rules that keep the evidence fair.
A skill the specialist lists on their profile. A useful signal, with no proof attached.
Earned by passing an assessment that defines a pass mark. Time-limited, and shown publicly only if its owner chooses to.
A result produced inside your own process: a score you can open in full, visible to you and the candidate.
When a requirement allows it, a valid verification the candidate already holds satisfies it: publicly visible ones at send time, private ones by the candidate's own click. Nobody proves the same skill twice for no reason.
Recruiters select, preview, assign and review. Only the candidate completes an assessment.
The recruiter preview shows sections, question mix, timing and rules. The live questions stay sealed.
Recruitment results stay inside the process. Verified skills appear on a profile only when the candidate turns them on.
A score informs a human decision. Nothing here auto-rejects or auto-hires anyone.
Yes. Write about any published service and it is just a conversation: no process, no assessments, no pipeline. Even inside a recruitment invitation, either side can ask questions before any decision.
No. An invitation can be just the role, terms and your message. Attach assessments only when the evidence genuinely helps.
A reusable sequence of named stages a company builds once, for example invitation, skills check, portfolio review, interview, offer. Each stage is required or optional. Invitations sent without one use the standard sequence.
Yes, up to five, each marked required or optional, with the candidate's estimated total time shown while you compose.
No. Reading an invitation, and even accepting it, starts nothing. An assessment begins only when the candidate presses start in the assessment itself.
No. Recruiters preview an assessment's structure and review results; only candidates complete attempts. A preview never creates an attempt or a result.
Yes, when the requirement allows it. A publicly visible valid verification counts immediately; a private one counts the moment the candidate chooses to apply it.
No. Results are visible to the candidate and to the recruiter who asked for them. A verified skill appears on the public profile only if the candidate enables it.
Both sides see the shared events: sent, accepted, assessments started and completed, stages entered, the outcome. Internal notes, waiver reasons and rejection reasons are visible only to the company.
Yes, at any point, with an optional message to the company. The process ends as withdrawn, never as rejected, and the company is notified.
No. It supplies evidence: scores, verified skills, integrity signals and context. Nothing auto-rejects or auto-hires; every decision stays with people.