At one place, I gave the strongest possible recommendation of a hiring candidate, even though they barely had the senior-level track record on paper that we wanted, because (in addition to signs that they already grokked real-world team software engineering like a smart senior) <i>it seemed clear they cared about the craft, were already skilled and wise about it, and would keep learning.</i><p>I advocated for the candidate, and also gave HR a heads-up that, if the other interviewers didn't agree to leveling the candidate at senior, we needed some promotion path with clear criteria that we could communicate, to distinguish us from the candidate's current company.<p>(Unfortunately, I was splitting that job req. with another team, who had some work before the hire would move fully to my team. The other team lead gave the candidate a CS-student Leetcode gatekeeping, which the candidate didn't do well at. These "coding" interviews need to end before they started, IMHO. It blocks some of the best people, and reinforces the counterproductive thinking among new grads that team software engineering is anything like school homework assignments or interview performance art.)