Vet both sides
Vet the client the way you vet the developer
Stackologists checks the project as hard as the developer, because a technology list nobody on the team will touch wastes both sides’ time.
Most staffing shops treat the client as the buyer and the developer as inventory, and they take the job post at its word. Then six weeks in, the “Kubernetes plus GraphQL plus three clouds” posting has landed someone who spends their days writing stored procedures on SQL Server.
So before we look at a person, we ask what will actually ship in the next increment. When the posting and the increment disagree, we go with the increment.
What a kitchen-sink posting actually costs
A requisition that lists every framework the company has ever mentioned forces a bad match. Candidates cram for logos nobody will use, and the team really needs the two technologies that touch production next. Everyone burns calendar.
- The posting names eight stacks and the increment uses two.
- Hosting and identity are assumed, never written down.
- “Senior full-stack” doesn’t say whether the seat is API work, UI work, or both.
That’s a project problem before it’s a hiring problem, and fixing the list is a lot cheaper than placing someone against a fiction.
What we ask the client before we open a résumé
- Which languages, data stores, and hosting the next increment will really touch.
- Who reviews pull requests, and how often “done” gets redefined mid-sprint.
- Whether the seat is ongoing capacity or a finished piece with a date. That’s the hire-versus-build call.
If those answers come back empty, we’re not ready to introduce anyone, and we’ll say so. That’s a legitimate outcome, not a stalled sale.
What we ask the developer
The person still gets a hard review. Years on a résumé and a wall of logos don’t settle it. We look at what they’ve owned against the technologies that will ship, including the hosting model when the ask is Blazor Server or WebAssembly.
- Which surfaces they’ve owned in production, not just in demos.
- Whether they can name the API or module the first sprint will call.
- Whether they’ve handled prerender or first-HTML work when public routes matter.
The match is for both of you
Most firms skip the part where they show you the fit, including when it’s weak. A weak match tells you something. You see the same score the candidate sees, which keeps everyone honest about where the work will live.
We don’t bump a score to clear a sales target.
No match is a finished outcome
If we can’t pair you, we stop. An empty seat today beats a bad hire you unwind in ninety days, and that’s true for the client and for the developer.
What this costs you up front
Some of your time on the real stack list. In return you skip a long engagement spent managing someone hired against a fantasy posting.
Bring the languages, data stores, and hosting the next release will touch. If you clear the bar together, you get a name and a short note on why that person fits the next increment.