Selection is a score, not a vibe
The old navigation called this Preferences and Selection Process. The steps did not need a redesign. They needed to be written down.
1. Write the stack that will ship
Not the wish list. The languages, data stores, and hosting that the next increment will touch. If that list is empty, we are not ready to score anyone.
2. Examine the person against that list
A Stackologist sits an examination for those technologies before we put a name in front of you. Readiness is not implied by years or by a logo wall.
3. Examine the client
We want to know how decisions get made, what “done” means, and whether the posting matches the work. Clients face the same scrutiny developers do. That is the philosophy this company was founded on.
4. Share the match score
You see the score. If it is low, we say why. A low score is not a sales objection to talk past.
5. Keep a scorecard after start
We stay invested past the start date. The scorecard is a feedback loop, not a performance-theatre document. The goal is the best fit, not a filled seat.