The three stages of an evaluated hire, on a synthetic example.

The seat. InsightAI, 24 people, sells machine learning and predictive analytics. They are hiring a senior lead engineer who reports to the CTO, with 5 junior engineers reporting in. The seat exists because the CTO is building the data pipelines and running the team at the same time and cannot keep doing both.

The client's value: One Team. Their definition, which they wrote and signed off before anyone was interviewed: works effectively with others by fostering collaboration, open communication and shared success. Relentlessly seeks to learn, adapt and grow within a team. Consistently receptive to feedback, and willing to support and uplift others to reach collective goals.

Why this client holds it. Their junior engineers sit with clients and come back with information senior people need to act on. A senior hire who cannot take a junior's input becomes the bottleneck at this company specifically.

The 3 written levels, from the client's own criteria. Does not meet: struggles with the basics of working in a team. Does not communicate effectively with people at different levels. Shows little willingness to learn, grow, or work with others. Meets: works well with others in a team. Communicates appropriately in difficult situations. Shows a willingness to learn, grow, and improve as part of a team. Exceeds: actively builds collaboration and takes responsibility for the team's result. Communicates effectively with people at every level, with a daily commitment to improvement and self-growth.

The trait it is read against: the ability to act on the instruction of a non-superior peer. Scored on a written scale where every level carries its own definition. The bar for this seat is a band with an ideal at its center, set before anyone was interviewed. The band, the ideal, the scale text and the scenario that tests it are not published, because an assessment whose items are public is one candidates prepare to.

Why the 2 are read together. The value interview shows how someone works inside a team and how they take direction from a person senior to them. The trait shows what happens when the direction comes from someone junior. Most people behave differently in those 2 cases, and the difference is the finding. A candidate who can separate the source of an idea from the merit of it is the one who multiplies a team rather than performing well inside it.

Candidate A, on the value. "We were migrating a legacy API to microservices on a tight timeline. I architected the solution, cleared roadblocks for the team, and kept the backend developers, QA and product on the same page. I ran whiteboard sessions where the whole group mapped the dependencies together rather than me handing down a design, and I put our technical milestones in business terms for the executives. When an integration bug threatened the launch date, I took the delay to the executives as mine, then sat with the developers until it was fixed. We shipped on time with no downtime, and the daily retrospective we started on that project is still running."

Rated exceeds. Specific, responsibility taken in public, and the practice outlived the project. One note recorded beside the rating: in an answer about a value built on the collective, there is no instance of another person's idea changing his plan. The value does not ask for one, so it does not move the rating. It is the reason the second reading exists.

Candidate A, on the trait. Written summary of his answer: he sets up frequent standing time with the peers, captures their instructions in detail, works from those instructions rather than rebuilding the approach himself, and checks their tactical steps against the manager's milestones as he goes. He lands below the ideal for this seat and inside the acceptable band.

Written finding: he asks for peer instruction often and acts on it, at moderate depth. The risk at this seat is dilution rather than refusal, since 5 junior engineers feeding frequent shallow direction can fragment a 30 day plan. A coaching note, not a blocker.

Result: passed both behavioral interviews, moved to the technical assessment, finding attached and given to the client.

Candidate B, on the value. He described rebuilding a data pipeline his team had inherited against a deadline set by a client renewal. He brought QA in early, ran the weekly review himself, and when the work slipped he told the client directly rather than letting his manager carry it. He named 2 people on the team by their contribution without being asked. Rated exceeds, on an answer as strong as Candidate A's.

Candidate B, on the trait. He routed the request back through his own manager rather than acting on it, framing the peers' input as something to be consolidated into a single prioritized list before he would work from it, and he defended that as the way to keep a 30 day project from becoming a 45 day one. He lands well below the band.

Written finding: disciplined about scope, and the concern he raises is a real one. What the answer does not contain is any step where he judges a peer's instruction on its merits. He routes it to authority instead. At this seat, where 5 junior engineers carry client information upward and the CTO is the person the seat exists to unload, that turns the role into the bottleneck it was created to remove.

Result: the 2 evaluators split, one rating him exceeds on the value while the trait score fell outside the band. Both reviewed the recording of the other's interview, compared the totals, and the trait carried under the standing rule. He did not advance. The client saw the reasoning.

What the example shows. 2 candidates, the same value, the same trait, indistinguishable on the first reading and separated by the second.