● Hiring, start to signed

One hire. Seven moments. One thread.

Most hires are a search tool, an inbox, a calendar, a signing service and a spreadsheet that is supposed to remember all four. Here it is one pipeline that both sides can see — follow a single hire through it, from the first search to the first day.

Included in every paid planNo signing vendorBoth sides keep the record
The workspace
Northwind Labs

Twelve people, one open role: an iOS developer. Nadia Laurent runs the hire.

The candidate
Maya Okafor

iOS developer, listed in the directory. 1,310 recorded hours, open to offers.

The hire

Seven moments, in the order they happen.

On the left and right, the same moment from each side. Between them, the thread it all hangs on.

  1. Mon 12 Oct09:41

    An invitation, not a cold message

    The invitation names the company, the role and why her. It lands on her profile, not in a recruiter's mail-merge. Nadia can see the moment it is read. Twenty minutes later Maya accepts, and a candidacy exists.

    Northwind Labs

    Sends one invitation with the role and a note, and sees when it has been seen.

    Maya Okafor

    Reads who is asking and what for before she answers. Accepting is her decision; declining ends it there.

    The ruleNothing begins until the candidate says yes.

    An invitation to the iOS Developer role travels from Northwind Labs to Maya Okafor, is marked seen, and is accepted: the candidacy is open.
  2. Tue 13 Oct10:05

    The chat opens when there is something to say

    Maya lands in a conversation she cannot write in yet. Then Nadia opens round one, and the composer unlocks with a line above it saying what this round is for. An inbox that is always open is a support queue; this is a conversation with a subject.

    Northwind Labs

    Opens a round and writes one sentence on what it is for. That sentence is what unlocks the chat.

    Maya Okafor

    Sees the lock lift and the purpose of the round, then talks to the people actually running it.

    The ruleThe candidate's chat is locked until a round opens it — enforced by the server, not by hiding a text box.

    The candidate's chat: a locked composer opens when round one begins, a banner says the round is an introductory call, and the conversation starts.
  3. Tue 13 Oct10:20

    A meeting that exists, not a link somebody pastes

    Nadia proposes Thursday at 14:30. Maya confirms it — or asks for another time and offers some. The moment it is settled there is a real calendar event with a Meet link, sent to her and to every interviewer, and posted in the chat where she is already looking.

    Northwind Labs

    Proposes a slot. The event is created on the company's own Google Calendar, with its own Meet link.

    Maya Okafor

    Confirms the time or proposes others. Her answer is on the meeting itself, where an interviewer can read it an hour before.

    The ruleOnly the candidate can confirm a proposed time. A company confirming its own proposal confirms nothing.

    A week of slots: Thursday 14:30 is proposed, Maya confirms it, and a meeting with a Meet link appears with every attendee invited.
  4. 15 – 27 Octthree rounds

    Round by round, with notes that travel

    An introduction, a technical round, a final. Northwind decided how many and of what kind. After each one the interviewers write what they saw, and when Maya moves on those notes go with her — so the next person in the room is not starting cold. One note does not move.

    Northwind Labs

    Runs as many rounds as it wants. Each has its own interviewers, its own meeting and its own notes.

    Maya Okafor

    Always knows which round she is in and what it is for. She is never asked the same first question three times.

    The ruleAnything about salary is a separate field, read by whoever runs the offer and by nobody else. A technical interviewer who knows the number is anchored by it.

    Three interview rounds: the candidate passes the introduction and the technical round and reaches the final; notes travel with her, and the salary note stays locked.
  5. Wed 28 Oct13:40

    The offer is signed here, by our own signing engine

    Nadia uploads the letter. The page finds where signatures are expected and proposes the boxes; she checks them and sends. Maya reads it on a page of its own, consents to sign electronically, and signs. Northwind counter-signs. No signing vendor ever holds the letter — or the salary in it.

    Northwind Labs

    Uploads the letter, confirms the signature boxes the system proposes, and counter-signs after the candidate.

    Maya Okafor

    Signs as herself: the signature belongs to her signed-in session, not to whoever opened an emailed link.

    The ruleEvery step is appended to a record sealed with a SHA-256 hash chain, with a certificate page for the finished document. Detection proposes; a person commits.

    An offer letter: two signature fields are found, the candidate signs, the company counter-signs, the letter is stamped executed, and each step is written to an append-only record.
  6. Mon 02 NovDay one

    Hired — and the record does not restart

    Passing the offer round is the hire: there is no separate form to fill in. An employee record is filed with the rounds she sat, who interviewed her and the letter both sides signed. On Monday she opens the desktop app, and her first recorded hour joins the profile that got her found.

    Northwind Labs

    Gets an employee record that answers, two years on, why this person was hired and who spoke to them.

    Maya Okafor

    Becomes a member of the workspace. The work she does from here is recorded, and adds to her own profile.

    The ruleThe employee record outlives the job. When somebody leaves, the membership ends and the record stays.

    An employee record for Maya Okafor is stamped hired, listing the rounds she sat, who interviewed her and the executed offer; her work starts being recorded.
The whole way through

Four things that never happen here.

01

No vendor reads the letter

Upload, signing, counter-signing and filing all happen on DeskTick. An offer letter — and the salary in it — is never sent to a signing service.

02

The number stays with the offer

Compensation notes are a separate field, not a convention. Interviewers see every other note and never that one.

03

No cold inbox, on either side

A candidate cannot be messaged before accepting, and the chat opens only when a round gives it a purpose.

04

Nobody loses the history

A candidacy that ends is kept, not deleted. A re-hire is a second candidacy beside the first, with both on the record.

FAQ

Before the first invitation.

Anyone in the talent directory. Developers choose to be listed there and choose what a company may read; nobody is scraped into it, and a developer who is not listed cannot be found or invited.

No. When somebody accepts an invitation the conversation exists but their side of it is locked. It opens when you open a round, with your sentence on what that round is for. The lock is enforced by the server.

Your own. A workspace connects its Google account under Settings → Integrations, so the event is created by your company, lands on your calendar and carries a Meet link on your domain. The invitation goes to the candidate and to every interviewer on the round, and the link is posted in the chat.

No. The signing engine is ours end to end: you upload the letter, confirm where the signatures go, and both sides sign on DeskTick. No third party receives the document.

Who signed, as the signed-in session that did it; their consent to sign electronically; when each step happened; and a SHA-256 hash chain over the events, with a certificate page for the finished document. Whether an electronic signature is sufficient for a particular contract depends on where you and the candidate are — check that with your own counsel.

The candidacy ends and its history is kept, for you and for them. It can be archived to tidy the list. Permanently deleting one is reserved to the workspace's owner and admins, and cannot be delegated.

Every paid plan includes talent search and the whole pipeline. The free plan is for one person and does not include invitations.

The next hire could be one thread.

Search the directory, send one invitation, and keep everything that follows in the place it happened.