The Services Firm Hiring Rubric: 5 Attitudes Worth More Than a Perfect Portfolio

The portfolio trap

A candidate walks into your office with a portfolio full of impressive work. Clean designs. Complex code. Happy client logos. You spend 20 minutes walking through case studies and nodding. The resume is a checklist of exactly what you need. You make the offer.

Six months later, that person has delivered technically adequate work and alienated three clients, two project managers, and a junior team member who quit without giving you the real reason. The portfolio did not lie. It just did not tell you what actually mattered.

Services firms do not sell products. They sell trust, judgment, and the ability to manage relationships under pressure. A developer who writes beautiful code but cannot explain a delay to an anxious client costs you more than a decent developer with sharp client instincts. A designer who produces stunning visuals but treats feedback as an insult will burn through your account managers until there are none left.

Technical skill gets you the interview. But five specific attitudes keep you on the team, retain your clients, and make your firm a place where good people want to stay. Here is the rubric.

Attitude 1: Client empathy

Client empathy is not about being nice. It is about the ability to read what a client actually needs versus what they said they wanted, and to navigate that gap without creating friction or resentment.

In a services firm, every person who touches a client relationship needs this muscle. The account manager needs it to spot a misaligned expectation before it becomes a crisis. The developer needs it to push back on a technically bad request in a way that makes the client feel heard, not overruled. The project manager needs it to know when to absorb a small scope change versus when to flag it for a change order.

Behavioral indicators to look for:

Green flag	Red flag
Tells you about a time they disagreed with a client and how they resolved it, including what the client felt	Cannot recall a single disagreement with a client, or describes every disagreement as the client being wrong
Uses phrases like "the client was worried about" or "what they really needed was" naturally	Only talks about deliverables, timelines, and technical specs
Describes client relationships in terms of trust built over time	Describes clients as obstacles, unreasonable, or "the stakeholder" in the abstract
Can articulate what a client was trying to accomplish, not just what they were asked to build	Cannot distinguish between "what the client asked for" and "what the client needed"

How to probe for it in an interview:

Ask: "Tell me about a project where what the client asked for turned out to be the wrong thing. How did you figure that out, and what did you do?"

A strong candidate will walk you through the moment of realization, the conversation they had, how they framed the alternative, and what happened afterward. They will describe the client's reaction, not just their own reasoning. They will mention some anxiety about the conversation because client empathy requires caring about the relationship enough to risk a difficult moment.

A weak candidate will pivot to "well, the client didn't really understand the technology" or describe sending an email that explained the right approach. That is technical correctness, not empathy. Technical correctness without empathy is how services firms lose clients they never saw coming.

Attitude 2: Transparent communication

In a product company, if a developer is behind schedule, they might update a Jira ticket and hope nobody notices until standup. In a services firm, that same delay has a client on the other end who scheduled a launch, promised their boss a date, or booked contractor hours around your delivery window.

Transparent communication means surfacing problems before they become emergencies. It means giving bad news early, with enough lead time for someone to do something about it. It means not assuming someone else will catch the ball.

Behavioral indicators to look for:

Green flag	Red flag
Describes a time they raised a flag on a project that was not their responsibility to raise	Every story is about problems they solved alone, with no mention of communicating status along the way
Can give a specific example of delivering bad news to a client or team lead	Has never had to deliver bad news, or describes problems as "we just worked harder and made the deadline"
Mentions what they did to give others time to react: "I told Sarah on Tuesday so she had three days before the client call"	Timeline in their stories is always retrospective: "it turned out fine" with no mention of when they communicated
Uses concrete status language: "I'm 40% done" vs. "I'm working on it"	Uses status language that is impossible to act on: "making progress," "on track," "should be fine"

How to probe for it in an interview:

Ask: "Walk me through the hardest project you have ever been on. When did you first realize it was going to be hard, and who did you tell?"

Listen for timing. A strong answer includes a specific moment of realization and a specific communication that followed within hours or a day, not weeks. A weak answer describes a project that was "hard but we got through it" with no mention of communication at all, which means either the candidate does not communicate or the project was not actually hard.

The most revealing answer is one where the candidate describes telling someone who was not their direct manager: a peer, a client contact, someone on another team who would be affected downstream. That is ownership beyond the org chart.

Attitude 3: Ownership instinct

Ownership instinct is the difference between someone who does what they are told and someone who sees what needs to be done and does it without being asked. In a 25-person services firm, the founder cannot assign every task. The people who thrive are the ones who notice the client deck has inconsistent branding, fix it, and mention it in standup. The ones who realize a deliverable is going to miss the mark and flag it before anyone asks for a status update.

This is not about working harder. It is about a mental model where "my job" includes the outcome, not just the task.

Behavioral indicators to look for:

Green flag	Red flag
Describes a project where they did something beyond their stated role because it needed doing	Every contribution is framed inside their job title: "as a designer, I designed"
Can articulate what "done" means beyond their piece: "the client needed the site to convert, not just look good"	Defines success only in terms of their own deliverables
Mentions noticing problems during other people's work and acting on them	Has never noticed or acted on anything outside their scope
Can describe a decision they made without asking permission because the situation required speed	Every decision in their stories required manager approval

How to probe for it in an interview:

Ask: "Tell me about the last time you did something at work that nobody asked you to do."

This question separates the ownership-instinct people from the task-doers immediately. A strong answer is specific, recent, and describes something the candidate noticed and acted on. It does not have to be heroic. Fixing a broken onboarding doc, reorganizing a chaotic asset library, or flagging a client risk that nobody had raised all count. What matters is the pattern: observing, deciding, acting.

A weak answer is vague ("I'm always looking for ways to help"), ancient ("a few years ago I..."), or describes something that was clearly part of their job. If the candidate cannot produce an example from the last six months, ownership is not an instinct for them. It might be an aspiration, but that is not what you are hiring for here.

Attitude 4: Adaptability under ambiguity

Services work is inherently ambiguous. Clients change their minds. Scope drifts. Budgets get cut mid-stream. The person who needs structure and clear requirements to function will struggle. The person who can navigate ambiguity without freezing, complaining, or shipping something wrong is gold.

This attitude is especially important in founder-led firms where processes are still forming. If you hire someone who needs a well-defined RACI matrix before they can start, and your firm is 18 people with no RACI matrix, you have a mismatch that will frustrate both sides.

Behavioral indicators to look for:

Green flag	Red flag
Describes making a reasonable decision with incomplete information	Needs "all the requirements" before doing anything
Can talk about a time they were wrong and what they learned, without defensiveness	Every story ends with them being right
Mentions pivoting mid-project without describing it as a failure or crisis	Describes change as a problem rather than a condition of the work
Uses phrases like "my best guess was" or "I assumed X and checked it later"	Uses phrases like "that was not in scope" or "the brief changed so I waited"

How to probe for it in an interview:

Ask: "Tell me about a time you had to make a decision without all the information you wanted. What did you rely on instead?"

Strong candidates will describe their mental model: the principles or past experiences they used as a compass. They will mention what they got right and what they adjusted later. They will sound comfortable with the idea of being directionally correct rather than perfectly precise.

Weak candidates will describe a hypothetical or say they always push back until they have enough information. That is reasonable in some contexts, but not in a services firm where the client is waiting and the founder is in another meeting.

Attitude 5: Low-ego collaboration

Services firms are team sports. No single person delivers a client engagement alone. The person who needs to be the smartest person in the room, takes feedback as a personal attack, or hoards credit will corrode your culture faster than any bad client.

Low-ego collaboration does not mean being a pushover. It means being able to hear "this is not working" without hearing "you are not good enough." It means sharing credit generously and absorbing blame when things go wrong, even if the fault is shared.

Behavioral indicators to look for:

Green flag	Red flag
Uses "we" naturally when describing successes and "I" when describing mistakes	Uses "I" for successes and "they" or "the client" for failures
Describes receiving tough feedback and what they did with it, including how it felt	Cannot recall receiving significant critical feedback, or describes all feedback as unfair
Credits specific teammates by name for project outcomes	Every story centers on the candidate as the hero
Mentions a time they were wrong about something and someone else was right	Has never been wrong in a professional context, or describes being wrong only in terms of a technical detail

How to probe for it in an interview:

Ask: "Tell me about a project that succeeded because of someone else on the team. What did they do that made the difference?"

This is the fastest culture-fit test I know. A high-ego candidate will struggle with this question. They might mention a teammate but quickly pivot back to their own contribution. They might give a generic answer like "the whole team worked hard." They might visibly search for something to say.

A low-ego candidate will light up. They will give you a specific person, a specific contribution, and genuine enthusiasm about it. They will describe what that person did in detail, because they paid attention to it at the time. This is the person you want on your team: someone who notices and celebrates other people's strengths.

Using the rubric without overcomplicating it

You do not need a formal scoring system to use this rubric. For each candidate who passes your technical screen, ask yourself five questions:

1. Can this person read a client's actual need behind their stated request?
2. Does this person surface problems early or hide them until someone asks?
3. Does this person act on what needs doing without waiting for permission?
4. Can this person make reasonable decisions when the requirements are fuzzy?
5. Does this person share credit and absorb feedback without taking it personally?

If you cannot answer at least four of these with a confident yes, you do not have enough data. Do not fill in the gaps with assumptions. Ask better questions in the next round or call a reference who can speak to these attitudes specifically.

The reference call is especially important for founder-led firms. When you are 22 people, you probably do not have enough interviewing reps to reliably assess all five attitudes in a 45-minute conversation. But you can call someone who has worked alongside the candidate for two years and ask them directly: "Did this person communicate bad news early or late? Did they step outside their role when something needed doing? How did they handle client feedback that contradicted their own judgment?"

Three reference calls structured around these five attitudes will tell you more than six additional interview rounds.

One last thing

This rubric only works if you know what attitudes your firm actually rewards. If your firm says it values transparent communication but the last person who delivered bad news early got blamed for causing a panic, your culture trains people to hide problems regardless of what the rubric says.

Before you interview anyone, look at the last three people you promoted and the last three people who left. Write down why. If the people you promote do not demonstrate the attitudes above, either the rubric is wrong for your firm or your promotion criteria are. Fix that first. No hiring framework survives a culture that contradicts it.