When a role's stated requirements and its values paragraph pull in different directions, which do you tailor toward?

## Why the two halves disagree Mark a job description in two colours and you will sometimes find the halves describing different jobs. The requirements list asks for deep, long-horizon platform work; the working-style paragraph says the team ships weekly and expects engineers in front of users. Both were written honestly, usually by different people, and the gap between them is rarely an editing mistake. It is normally one of three things: **A team in transition.** The requirements describe the work as it is; the values describe how they intend to work once the current effort lands. **Two audiences in one document.** A manager wrote what the role does; a talent or leadership function wrote how the company likes to describe itself. **A genuine unresolved argument.** Somebody wants the surface rebuilt properly and somebody wants weekly visible progress, and nobody has decided. All three are useful to know before you accept anything, which is the first reason not to treat the conflict as noise. ## The default ordering The two halves do not have equal function. **Requirements gate.** They determine which stories are eligible. If the role owns a long-lived surface and none of your work has that shape, cultural alignment does not rescue the application, and leading on it makes you look like you skimmed. **Values choose.** Among the stories that clear the gate, the working-style lines decide which goes first and which beats get airtime. So the crude rule is: **requirements to be taken seriously, values to be chosen.** Most postings need nothing more than that, because their halves agree. ## When they actually conflict The weak response is averaging: a bit of platform depth, a bit of speed, both thin. It produces a candidate who is defensible on paper and memorable to nobody. The stronger move is to find one story that honestly contains both threads and open on the tension. From a frontend bank, a redesign of a long-lived surface that was nevertheless delivered in shippable slices is exactly such a story — the depth is real, the cadence is real, and the interesting part is how the two were reconciled. Opening on *the hard part was keeping weekly releases going through work that wanted to be a three-month branch* does three things at once: it satisfies both halves, it demonstrates that you read the document closely enough to notice the tension, and it hands the conversation somewhere genuinely worth going. If no story in the bank contains both threads, choose the requirements side and be explicit about the other. Claiming a working style you cannot evidence is the failure that costs most, because the claim invites exactly the follow-up you cannot answer. ## The judgment nobody can make for you There is a real disagreement in the coaching world about which half to weight, and it turns on what you are optimising. - **Weighting requirements** maximises the chance of an offer for the role as written. It is the right call when you need the role, or when the work itself is what you want. - **Weighting values** maximises the chance the job is the one you actually want to hold in a year. It is the right call when you have options, because the working-style lines predict your daily experience far better than the requirements list does. A useful stance: tailor toward the requirements, and use the conflict as your own material for the questions you ask. A tension you noticed in the document is one of the few genuinely specific things a candidate can raise, and the answer tells you which half of the posting is currently true. ## Where tailoring stops Two limits are worth deciding in advance. **Do not tailor into a role you would decline.** Being persuasive about a version of yourself you do not want to be is an expensive skill to exercise: it works, and then you hold the job. **Do not let the values half rewrite your record.** A posting that prizes autonomy will tempt you to promote the story where you decided alone, even if the truthful version is that you were overruled and it went better. Emphasis is free; the facts underneath are not. ## The reduced form Requirements decide eligibility. Values decide order. A conflict between them is information about the team, best answered with one honest story that carries both threads and, at the end of the conversation, a specific question about which half is currently winning.