Every hire keeps what the role actually needed.
A hiring manager asks for a new role in Slack. Nieme turns it into the job description, the scorecard and the interview kit, from the team's real work and the company's hiring policy, for the manager and HR to approve.
What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.
A message in #hiring: the payments team needs a second backend engineer.
A document changed in a connected folder.
A message was observed in a selected channel.
A manager asks for a new role
A message in #hiring: the payments team needs a second backend engineer.
Observed event
- Source
- Slack
- What happened
- A manager asks for a new role
- When Nieme saw it
- 12 min ago
Nieme recorded that this event happened. Observation alone authorizes nothing.
Why it matters
Nieme's reason
the source is selected for this Project
Status
Raised as a Signal. Nieme proposes the work; a person decides.
This title is independent of the Objective.
Produces each declared file as a governed Artifact of this one Operation, reviewed together.
Project: Hiring · Payments
From Signal · a message in #hiring
Selected Operation Sources (4) — explicitly chosen
Hiring · Payments · operation.on
- DOCXjob-description-backend-payments.docx22 KBproduced
- XLSXscorecard.xlsx19 KBproduced
- DOCXinterview-guide.docx28 KBproduced
Where the work breaks now
Without a record
- The job description is copied from the last one.It describes the role you had, not the one you need.
- Every interviewer asks something different.Without a shared scorecard, the debrief is opinion against opinion.
- Why we hired stays unwritten.Six months later, nobody can say what the role was meant to solve.
With Nieme
- Drawn from the actual work.The description is built from the team's sources, not a template.
- One scorecard, one kit.Every interviewer gets the same criteria and questions, tied to the role's objective.
- The reason is on record.What the role was meant to solve stays attached to the hire.
From a request in Slack to a hiring kit the manager approves
-
01 · Observed
A manager asks for a new role
A message in #hiring: the payments team needs a second backend engineer.
Slack -
02 · Governed
The hiring work is opened
Objective, the team's roadmap, the career ladder and the hiring policy are admitted.
operation.onpolicy.on -
03 · Executed
The hiring kit
Job description, scorecard and interview guide, consistent with each other.
DOCXXLSX -
04 · Reviewed
The manager and HR approve
Accept, request changes or reject. Publishing the role stays with HR.
Review -
05 · Carried forward
The next hire starts from this one
Scorecards and outcomes are there when the next role opens.
decision.on
The work outlives the session that did it.
Every step above writes to one record. Swap the model, the agent or the person who executes, and the objective, the sources, the authority and the decision stay attached to the work.
- objective
- Open a second backend engineer role for payments
- context
- Payments roadmap · career ladder · hiring policy · #hiring thread
- authority
- Approved by the hiring manager and HR
- executor
- Nieme Generalist, a governed Role
- evidence
- Job description, scorecard and interview guide
- decision
- Accepted; salary band adjusted by HR
The fields Nieme stores for every Operation.
Hire deliberately.
Remember why.
We turn one hiring request into a job description, a scorecard and an interview kit, for the manager and HR to approve.
Rather talk to a person? Email the founder.