Chapter 23: Sourcing & Screening

Every company has its own interviewing pipeline and decision-making protocol. I am not a psychologist, nor do I intend to step on HR’s toes. What I am offering is an operational perspective on selecting a candidate to enter a trial period.

We have already established that to a manager, team members function as the tools required to achieve project objectives. Let us follow this logic when selecting a new instrument for our toolset.

I admire tech giants, but frankly, I struggle to comprehend how calculating the number of golf balls that fit inside a school bus demonstrates a project manager’s operational sanity. If the goal is to corner a candidate and look intelligent, perhaps it is an ideal question. But practically, how do you apply the answer on the factory floor?

Imagine a carpenter stepping into a hardware store and inspecting a microscope to see how well it drives nails. That is precisely how I view trick questions wrapped in 18 layers of hidden meaning. If you need a cobbler's hammer, inspect its weight, dimensions, handle durability, and whether its head can maneuver into the tight contour of a boot heel. Naturally, it must coexist with the other tools on your workbench without scratching everything around it. Crucially, check the price tag and the availability date. If you need to repair boots today, what good is a hammer delivered in three years?

Evaluating Technical Capabilities

The same logic applies to hiring a developer. Need a backend engineer for a distributed system? Verify what they actually need to know:

• Language Fluency & Code Literacy: Focus on daily operational proficiency rather than obscure compiler trivia. Do not grill candidates on writing 24 operators on a single line without documentation. Test the core patterns and architecture they will touch daily. In an era where generative AI can draft syntax on demand, typing speed is irrelevant—the true test is code literacy: the candidate's ability to read, audit, and debug what the machine generates.
• Architectural Thinking: Present an abstract problem spanning multiple system layers. It doesn't need to be an enterprise-grade architecture; a slightly complex task is enough to reveal whether they understand system design or if they've never written anything beyond text-output scripts.
• Technology & Infrastructure Foundations: Is your server running as a thread pool? Ask them about the constraints of that approach. What breaks if the server reboots, and how do you mitigate it? If they are passing data over HTTP, ask about the protocol's mechanics and security boundaries.
• Practical Logic: General logical reasoning is necessary, but keep it grounded. Ask them to sketch a non-trivial database schema or set priorities of modules' implementation rather than solve abstract riddles.
• Client Communication: Clear articulation is vital; articulating in the client's language is doubly so. They don't need a doctorate in linguistics, but they must frame a technical question clearly and understand the answer. Otherwise, you will have to open a second requisition for a full-time translator.

Who Conducts the Interview?

Who buys the hammer? The craftsman who will use it.

If you are hiring to reinforce a specific team lead's squad, bring that lead into the room. They are the one who has to live with the hire.

If you need a team member but don't yet know which project they will join—like buying a wardrobe before deciding which room it goes in—bring a trusted team member. Pick someone who knows the project landscape, grasps the technical baseline, understands your culture, and isn't afraid of human interaction or daylight.

Decision Protocols: Fast Rejections and Immediate Offers

Once technical capability is established and your internal specialist is satisfied, clarify two operational metrics: start date and salary expectations. By this point, you should have a solid read on where this candidate sits on your technical ladder.

If ten minutes in you realize the candidate is wrong—whether due to technical deficits or because they continuously spit on the floor, plan to quit for professional ballet, or smell like a train station—end it immediately. People do not change overnight. Do not waste your time or theirs. A "no" is a "no"—the earlier you deliver it, the better.

The same applies to a "yes." If the candidate fits, their availability aligns, and the compensation fits your budget—hire them immediately. They will be poached while you hesitate. Candidates accept rival offers simply because a company insisted on a dramatic pause to "see a few more people." Be the team that skips the theatrical deliberation and extends a firm, mutually beneficial offer. Candidates are often stunned by direct efficiency.

Pitching the company is essential. Even rejected candidates leave with an impression—they might recommend you to colleagues or reapply once they gain experience. For a new hire, this context provides the ground beneath their feet.

To summarize, hiring answers three fundamental questions:

1. Can this person do the required work?
2. Do they want to do it?
3. Do they fit your team's operational ecosystem?