Hiring Signals from a Manager’s Perspective

“I ended up doing everything myself.” One interviewer hears a strong hire. Another hears a poor team player. Neither has learned much yet, but both already have an explanation for their decision.

I care about recurring ways of working: decisions, knowledge sharing, mistakes and risk. They are worth exploring in hiring. A single account cannot reliably reveal someone’s personality, motives or future compatibility. An overconfident interviewer can become the larger risk.

Updated 30 September 2026. This develops my original article, published on Habr on 20 October 2025. I retain its practical questions while replacing broad labels with observations, alternative explanations and checks.

What the discussion changed

The Habr discussion raised valid objections: a lone expert may reflect how the team is managed, not a desire for control; an hour does not authorise personality classification; and a manager can use convenient labels to explain hiring failures after the fact.

I take those objections seriously. A memorable pattern should help us remember a question, not replace its answer. When something concerns me, the sequence should be:

1. What exactly did the person say or do?
2. What risk would that create in this particular role?
3. What other explanation fits?
4. What question or work sample could distinguish the explanations?
5. What evidence would change my initial opinion?

If no answer could change your mind, the interview is already over. The remaining conversation is theatre.

A radar of working behaviour

These six areas form a question map, not a psychometric test. Posture, eye contact, accent and response speed are not reliable shortcuts to professional competence.

Observation → hypothesis → follow-up → evidence

01OwnershipWhat could the person affect?

02DepthWhy choose this option?

03CooperationHow is knowledge shared?

04RiskWho knows the trade-off?

05LearningWhat changed after a mistake?

06OutcomeWhat evidence shows an effect?

Define role expectations first. A specialist and a cross-team leader need different evidence. Otherwise one candidate loses for being too independent and the next for lacking initiative, because the standard changed mid-conversation.

The dialogues below are illustrative, not transcripts. Each label describes a possible pattern in a situation, not a permanent type of person.

The wronged hero: everyone else’s mistakes

Observation: several accounts explain other people’s failures but leave the candidate’s own actions unclear.

Possible risk: difficulty learning from setbacks or agreeing on improvements. Alternative: the environment really was dysfunctional, and the person lacked authority.

“Management kept changing priorities, so we missed the launch.”
“What could you influence? How did you show the consequences?”
“I documented the impact, but I could not stop new work arriving.”
“What helped? What would you do differently now?”

I look for actions and a realistic boundary of influence. I do not demand a ritual confession that everything was the candidate’s fault. Criticising a former employer is not, by itself, a reason to reject someone.

Concern decreases when the person separates facts from interpretation, describes attempts to improve matters and recognises what they could change.

The lone coder: independence or a single point of failure

Observation: only one person can make a key change or recover the service. Risk: knowledge concentration and a team dependent on one person’s availability.

That can result from personal habits, staffing, poor planning or pressure from management. Ask before assigning a motive.

“Doing it myself was faster.”
“Who could take over while you were away?”
“Nobody. There were two of us, and the other person kept being reassigned.”
“What did you propose? How would you begin transferring one scenario with adequate time?”

Now there is a work situation to discuss. Check whether the person can explain a design, accept review, delegate a bounded task and plan a handover. Also check whether the prospective manager will allocate time for it.

Hiring a hero, putting them into another permanent emergency and blaming their habits when the pattern repeats is poor management analysis.

Flexible about rules: a trade-off or a concealed risk

Observation: the candidate describes bypassing a check or rule, but it is unclear who knew about the consequences.

An emergency release may legitimately follow an approved exception process. A departure from routine is not automatically misconduct. Ask about authority, visibility and recovery.

“We shipped without the usual checks to meet the deadline.”
“Who approved that? Which checks remained? How did you monitor it, and what would trigger a rollback?”

The serious concern is knowingly hiding consequences, proposing to use someone else’s confidential data or treating the accountable person’s awareness as unnecessary. Base that assessment on evidence, not a guess about morality.

Useful evidence includes an identified decision owner, bounded exposure, monitoring and a plan to address the resulting debt.

The unfocused star: breadth or a display of terminology

A long technology list is not a problem. Neither is specialisation. The question is whether the claimed depth matches the role.

Take one decision and follow it through: problem, constraints, options, choice, failures and verification. Then change one condition.

“Why use a queue?”
“To decouple services.”
“What happens on duplicate delivery? What if the consumer falls a day behind?”

Specific reasoning can substantiate breadth. Repeating “scalability” does not. I do not demand memorisation of an obscure setting I looked up myself yesterday.

The missing contribution: participation and ownership

A manager is entitled to say “we.” Team outcomes do not become less valuable because the manager did not write every line of code. Their own decision responsibilities still need to be clear.

Ask for situation, authority, action, outcome and evidence. What changed? How was that observed? What else might have contributed? What remained unresolved?

An absent percentage is not an absent result. NDA constraints or missing historical metrics may require qualitative evidence. Do not pressure a candidate to disclose confidential figures while claiming to value security.

Two further signals: perfect endings and never changing one’s mind

If every mistake becomes a triumph, ask about one without a satisfying ending. The point is learning, not confession.

If every disagreement ends with everyone accepting the candidate’s view, ask when a colleague’s argument changed their decision. Give time to recall an example. One awkward answer is not a diagnosis.

Then ask yourself the same question: would you accept evidence that overturns your favoured assessment of this candidate?

Record evidence that another person can assess

The OPM guide to structured interviews connects questions to job competencies and recommends a consistent core of questions and common assessment standards. That discipline helps structure the conversation; it does not make hiring a precise prediction.

Record	Useful example
Observation	Only the candidate knew the recovery procedure for the release described
Risk hypothesis	Team dependence on one specialist
Alternative explanation	No allocated handover time or prepared deputy
Check	Discuss a handover plan for one scenario and previous attempts to organise it
Evidence obtained	Candidate identifies transfer steps and an independent recovery criterion
Still unknown	How successfully this was implemented in practice

“Difficult personality, not our kind” supports neither comparison nor improvement.

Distinguish supported, conflicting evidence and not assessed. These are evidence states, not universal personality scores. Define role-specific expectations before applying them. Missing information is not automatically a weakness.

With multiple interviewers, record observations independently before discussion. Otherwise the first confident opinion can become the group’s supposedly shared impression.

Work samples and feedback

A small, relevant exercise can test a hypothesis. For a leader, discuss a release plan with dependencies and scarce capacity. For an analyst, clarify a contradictory requirement. For an engineer, explain a system fragment under failure.

Explain conditions and criteria in advance. Do not turn the exercise into unpaid product development or a guessing game about the interviewer’s preferred answer.

Useful feedback connects an observation to the role: “We did not obtain enough evidence of how you organise operational handovers between teams.” “You are not a team player” is a much broader claim with less practical value. If the decision rests only on a feeling, acknowledge the weak basis.

I have red flags too

I am not an infallible assessor. To someone else I may have been, or may still be, too quick to conclude, too forceful in disagreement or unaware of my own difficult behaviour. That adds responsibility rather than removing it.

Before deciding, I ask:

• Am I mistaking similarity to me for competence?
• Am I penalising disagreement or an uncomfortable question?
• Am I explaining my team’s problems through people’s supposed personalities?
• Have I described authority, workload and role difficulties honestly?
• Which notes are observations, and which are interpretations?
• What evidence would change my decision?

Nervousness, pauses, an accent, introversion, career breaks, limited eye contact and questions about compensation do not establish professional unfitness. Respecting working hours does not establish weak motivation.

Hiring is reciprocal. A candidate may see my limitations and decline. A strong team needs an honest working agreement, not an interviewer winning a psychological contest.

Change the next interview

Choose one role and three to six relevant competencies. Prepare a common question core and explicit expectations. Separate observations from hypotheses, investigate consequential doubts and then decide.

A smaller starting point is to replace “I didn’t like them” with “Which working behaviour could I not substantiate?” The conversation immediately becomes more useful.

I help review team structures, responsibilities and decision processes. If hiring repeatedly produces disappointing results, let’s examine the situation. The necessary change may be in the working conditions rather than the list of red flags.

Yours, DPUPP