When a skip-level director and the hiring manager rank the team's work differently, how should a candidate weigh the two accounts?

## The gap is the finding Candidates who notice that a director and a hiring manager describe the same team's future differently usually do one of two things: ignore it out of politeness, or quietly conclude someone is spinning them. Both waste it. A discrepancy between two levels of an organization is the most useful raw material a loop produces, because it is the one thing nobody prepared an answer for. ## Four benign explanations, and one that is not **Different horizons.** A director plans a year ahead against funding; a manager runs the current cycle against commitments. A team can be committed to finishing something this quarter and attached to a different bet next year, and both descriptions are true. **Different vocabulary.** Leaders describe work in terms of outcomes for the organization; managers describe it in terms of systems and deliverables. The same work can sound like two things. Ask the mapping question and the two often collapse into one. **Translation lag.** A new ranking has been set upstream and has not yet reached the team's plan. Common after a re-plan or a reorganization, and usually visible as a director who is confident and a manager who is vague on the same point. **Advocacy.** The manager wants the role and describes the work as the version most attractive to a candidate. Not dishonest exactly, and easy to detect: their version is always the more exciting one. **The one that matters.** The role is being staffed for work whose funding is not secure — the manager is hiring against a plan the level above has already down-ranked. This is the case worth spending a question on, because it is the one that changes what your first year looks like. ## How to test it inside the loop Ask both people the same question, in the same words, and note not only the answers but the confidence. Ask a third person if you get the chance — the same question to a peer engineer produces a ground-level version that often adjudicates between the two. Then raise it directly, without an accusation in it: `The hiring manager described next year mostly around the platform work; how does that map against the three bets you named?` Delivered curiously this reads as diligence, and it is a question about the plan rather than about a person. Most leaders answer it straightforwardly, and the answer usually contains the reconciliation. If the discrepancy survives that, ask the consequence question rather than pressing the contradiction again: `If that bet does not get funded next year, what does this role work on instead?` A leader who has thought about the team's durability has an answer. A leader who has not gives you the same information in a different form. ## Deciding what to do with it Hold two things in tension. The first is scope: a role attached to a well-funded, highly ranked bet tends to come with more visibility, more headcount around it and more room to grow — a team going from eleven engineers into a range of fourteen to seventeen creates senior-shaped work simply by growing. The second is judgment about durability: a team whose funding story is contested may be re-pointed within a year, and re-pointed teams lose the work people joined for even when nobody loses a job. Neither factor decides alone. A role on a less-ranked team with a leader who arbitrates clearly and funds engineering work can be a better place to build a career than a role on the top-ranked bet with no mechanism for ending arguments. What a strong candidate does is decide *knowingly*: name the risk to themselves in one sentence, ask the question that would most reduce it, and then weigh what they heard rather than what they hoped. ## The artifact does the arguing By the end of a loop your sketch should carry the small set of bets, the teams under them, the arrows into the team you would join, and two versions of one arrow where the accounts differed. That drawing is what you take into the decision, and it is also what you take into your first week if you accept — the questions you could not resolve as a candidate are the first ones worth asking as an employee, when people can finally answer them fully. ## Tone, because this one can go wrong Raise a discrepancy at most once, and never as a challenge. You are not there to catch anybody out, and a candidate who audits leadership reads as someone who will litigate rather than build. One clear question, delivered plainly, then listen and let it go.