Most advice about how to assess soft skills is fluff wearing a blazer.
You'll hear “look for culture fit,” “trust your instincts,” or my personal least favorite, “you can tell a lot from the conversation.” Sure. You can also “tell a lot” from a founder's headshot. Doesn't mean it predicts whether they'll reply to your Slack messages without causing a small constitutional crisis.
The usual advice breaks because it treats soft skills like mystical traits instead of business-critical behaviors. That's lazy. Communication, accountability, judgment, adaptability, and teamwork are not vibes. They show up in emails, handoffs, deadlines, conflict, feedback, and how someone behaves when things get messy.
I learned this the expensive way. The technically brilliant hire who can't collaborate will eat more team energy than three mediocre hires and a broken sprint board. If you're hiring for remote, cross-border teams, the stakes get even higher. You can't patch bad communication with hallway chats or “quick syncs.” You need a system.
“Soft skills” is a terrible label.
It makes essential operating traits sound optional. Like office snacks. Nice if present, survivable if not. In reality, these are the skills that decide whether someone can work on a team without turning your calendar into a hostage situation.
If a developer writes clean code but creates confusion in every handoff, that's not a personality quirk. It's a delivery problem. If an ops hire misses details, avoids ownership, and gives vague updates, that's not “something to coach later.” That's a systems failure you just added to payroll.
Brookings made this point in a smarter way than most HR playbooks. Its soft skills framework pushed assessors to focus on observable behaviors like “persisting on tasks” instead of abstract labels like “grit,” which makes assessment more actionable and less hand-wavy in practice, as explained in the Brookings soft skills report card.
Soft skills get called “soft” right up until a team misses deadlines because nobody can communicate clearly.
Founders love to say they're good at reading people. I'm a founder. I've said it too. I was wrong often enough to stop saying it out loud.
A strong hiring process doesn't remove judgment. It contains judgment. That's the difference. You want a process that forces candidates to show how they work, not one that rewards confidence, charisma, or shared taste in overpriced coffee.
A structured values screen helps. If you need a practical starting point, use a structured culture values interview scorecard so interviewers evaluate the same behaviors instead of freelancing their own definitions of “great attitude.”
Teams often don't fail because they ignore soft skills. They fail because they talk about them in mushy, generic language.
They say “good communicator” when they mean “writes clear async updates without being chased.”
They say “team player” when they mean “resolves tension without becoming the tension.”
They say “adaptable” when they mean “doesn't melt down when priorities change.”
That translation matters. If you can't define the behavior, you can't assess it. And if you can't assess it, you're guessing.
“Strong communicator” is hiring junk food.
It feels productive because everyone nods at it. Then the person starts, misses context in Slack, writes updates nobody can parse, stays quiet on blockers, and your distributed team pays the price. In remote, cross-border hiring, vague language gets even more expensive because people are working across time zones, writing more than they talk, and interpreting tone through a screen.
A Brookings report made the right point earlier in this article. Assess observable behaviors, not abstract labels. That approach matters even more for remote teams, where performance shows up in writing, follow-through, response habits, and judgment without supervision.
Copy that standard.
Do not hire for “ownership” as a slogan. Define the behaviors:
Do not hire for “teamwork” as a personality vibe. Define the behaviors:
For remote, cross-border teams, get even more specific. “Good communicator” in a US office can hide behind charm on Zoom. In a US and Latin America team running asynchronously, it usually means something sharper: writes updates in plain English, gives context without being asked, asks clarifying questions early, and does not vanish for six hours while a project stalls.
Every role needs a short soft skills list tied to the actual work. Three to five is enough. More than that and interviewers start inventing reasons to like whoever feels familiar.
For a remote engineer, the list might be:
For a customer success manager, it might be:
Write this into the role before you interview a single person. If your posting still sounds like generic startup theater, fix it first with a better guide to creating job descriptions that spell out real responsibilities.
One more rule. Avoid traits that are really culture-coded preferences pretending to be standards.
“Executive presence” often means “sounds American enough for me.”
“Proactive” sometimes means “talks a lot in meetings.”
“Confident” can mean “uses my communication style.”
That is how good candidates get screened out for the wrong reasons, especially in cross-border hiring. Define the work standard instead. For example: “escalates risks within 24 hours,” “summarizes decisions in writing,” or “pushes back with evidence.”
If candidates want help practicing those situations before the interview, point them to an AI assistant for interview preparation. It is useful for rehearsing clear written and verbal answers, which matters a lot more in remote hiring than polished small talk.
For each soft skill, ask this: What would this person do in week two if they had it?
That question kills fluff fast.
“Adaptable” becomes “re-prioritizes after scope changes and updates everyone affected.”
“Leadership” becomes “drives a decision when ownership is fuzzy.”
“Communication” becomes “posts concise updates with status, risks, and asks.”
Write those behaviors down and use the same language everywhere. Job description. Interview kit. Scorecard. Debrief.
If a trait cannot be seen, heard, or read in actual work, it does not belong in your hiring process.
Once you know the behaviors you care about, build a process that makes candidates prove them.
Not explain them. Not claim them. Prove them.
A resume can hint at context. A casual chat can reveal polish. Neither tells you much about how someone handles ambiguity, conflict, or accountability when work gets real. You need a gauntlet.
The fastest way to get fake-good answers is to ask hypothetical questions.
“What would you do if a stakeholder changed priorities?”
They'll tell you they'd communicate proactively, align the team, and ensure successful delivery. Of course they would. In fake scenarios, everyone's a composed genius.
Ask for specifics instead:
Use STAR if you want structure, but don't worship the acronym. Push for detail. Actions. Tradeoffs. Consequences. The point is to hear what they did when things got annoying.
If your interviewers need help tightening their own questioning and follow-ups, an AI assistant for interview preparation can help them rehearse structured prompts before they walk into the call half-prepared and overly impressed by confidence.
One interview is not enough. One test is not enough. One “strong feeling” definitely isn't enough.
Research summarized by SkillPanel says organizations that combine psychometric tests, STAR-based behavioral interviews, and situational judgment tests can reduce final interview candidates by 50% while identifying twice as many high-potential candidates, according to the SkillPanel assessment guide.
That matches reality. Different methods catch different failure modes.
Good for hearing how people frame problems, take ownership, and talk about others.
Bad when used alone, because polished candidates can narrate a better story than they can live.
Good for forcing tradeoffs. Give a realistic scenario and ask them to rank responses or choose a path.
Bad if the scenario is generic. “A coworker is upset. What do you do?” means nothing. Make it role-specific and messy.
This is the one people resist because it takes effort to design. It's also the one that exposes the truth fastest.
Give candidates a task that mirrors actual work:
A work sample reveals soft skills through execution. Is the response clear? Structured? Calm? Practical? Do they ask smart clarifying questions? Do they overcomplicate everything because they want to sound impressive?
The best soft skills tests don't ask who someone is. They force them to show how they operate.
For top candidates, I like a small paid situational task.
Not a free consulting project. Don't be that company. A contained, paid exercise.
For remote roles, this is gold. You see how they communicate expectations, manage timelines, surface assumptions, and deliver something useful without constant hand-holding. That's half the job in distributed teams anyway.
Keep it short. Keep it fair. Score it against the same behaviors you defined earlier. If someone aces the interview but falls apart in a realistic task, believe the task.
Interviews measure storytelling. Work measures working.
After interviews and tasks, many hiring groups make the same mistake. They gather in a debrief and compare vibes.
“He seemed sharp.”
“She was polished.”
“I just wasn't sure.”
That's not evaluation. That's group improvisation with payroll consequences.
A scorecard doesn't make hiring robotic. It stops interviewers from changing the rules midway through the game.
The cleanest way to score soft skills is to define each competency with behavioral anchors on a simple scale. The exact numbers matter less than the consistency. What matters is that everyone knows what a weak answer looks like, what a strong answer looks like, and what evidence counts.
Resumly's framework gets this right. To make soft skills measurable, tie them to business value with “Action verb + soft skill + project context + quantifiable metric + result”, and combine that with structured scorecards and multiple raters, as outlined in the Resumly guide to quantifying soft skill impact.
That framework is useful because it forces specificity. “I'm a collaborative leader” is empty. “Led cross-functional work during a process change and improved the handoff metric we cared about” is the beginning of evidence.
If your team hasn't standardized interviews yet, this primer on what competency-based interviewing is is a practical baseline.
Here's a straightforward scoring table for Problem Solving.
| Score | Behavioral Indicator (What It Looks Like) | Sample Interview Question |
|---|---|---|
| 1 | Jumps to conclusions, blames others, offers vague fixes | Tell me about a time a project went off track. How did you respond? |
| 2 | Identifies the issue but struggles to structure a response | Describe a work problem where you had limited information. What did you do first? |
| 3 | Breaks the problem into parts, proposes a reasonable path, misses some tradeoffs | Tell me about a time you had to choose between speed and quality. |
| 4 | Clarifies constraints, evaluates options, explains tradeoffs clearly | Walk me through the hardest operational issue you solved recently. |
| 5 | Diagnoses root causes, communicates decisions clearly, adapts as new facts appear | Tell me about a problem where your first approach failed. What changed in your thinking? |
Three rules make scorecards work:
Hiring rule: If a score can't be defended with a quote, example, or work sample, it doesn't count.
This isn't about pretending humans are machines. It's about making your human judgment less sloppy.
Remote hiring exposes every weakness in your assessment process.
In an office, people can compensate for poor communication with proximity. Someone overhears a problem. A manager notices tension in a room. A teammate fills in the blanks after a confusing update. Remote work removes that safety net. Cross-border hiring removes another one. Shared assumptions.
Generic soft skill advice fails at this point. Most guides assume domestic hiring, real-time collaboration, and a shared communication norm. That's not the world many startups operate in.
A 2025 report found that 67% of global hires fail due to soft skill mismatches in remote roles, with cultural misreads 40% higher in LatAm-US pairings. It also notes that traditional Likert scales can inflate scores by up to 25% in high-context cultures like Latin America compared with low-context North America, which is exactly why simple self-ratings can mislead in cross-border hiring, according to Peregrine Global's analysis of the soft skills gap.
That matters. A candidate may sound less direct because they're culturally calibrated to be more relational, not because they can't communicate. Another may rate themselves highly because the scale itself lands differently across contexts. If you treat those signals as universal, you'll make bad calls and feel weirdly confident about them.
For remote, cross-border roles, I care less about charisma and more about operational clarity.
Test these directly:
If you're hiring from Latin America into US or Canadian teams, this breakdown of the role of soft skills in remote hiring from LatAm is worth reading because it addresses the gap most hiring playbooks ignore.
A remote hire doesn't need to sound like you. They need to be clear, reliable, and adaptable when you're not in the room to smooth things over.
A good remote soft skills test should work even when nobody is live.
Try this sequence:
That exposes judgment, initiative, and async discipline in one shot.
If you want candidates to strengthen the specific communication habits remote teams depend on, this guide on effective communication skills for remote professionals is a useful companion resource.
For teams hiring at scale, tools can help operationalize this. For example, LatHire uses AI assessments, skills evaluations, and human-led background checks to vet remote talent from Latin America before employer interviews begin. That kind of front-end structure is useful when you want consistency without turning every hiring manager into a full-time assessor.
Bad hiring processes fail in two ways. They either run on vibes, or they pile on so many rounds that strong candidates drop out and managers stop following the system.
You want neither.
The fix is simple. Build a hiring process that collects enough evidence to make a confident call, then stop. For remote, cross-border teams, that matters even more. A weak process will miss the people who communicate clearly across cultures and time zones, and it will reward the people who just interview well in live calls.
Do the hard thinking upfront, not from scratch for every open role.
Write down the behaviors that matter for your team. Define what “clear communicator” means in a remote US and Latin America setup. Does the person ask sharp clarifying questions? Do they flag blockers early? Can they write an update a US manager can scan in 30 seconds without guessing what happens next? That level of specificity saves time later.
Then turn those definitions into reusable parts:
That gives hiring managers a repeatable process instead of a pile of opinions.
A hiring stage needs a job. If it does not produce new evidence, cut it.
Too many teams create bottlenecks because nobody decides what each step is for. Then the recruiter tests communication, the manager tests communication again, two panelists ask the same “tell me about a conflict” question, and everyone pretends that repetition equals rigor. It does not. It equals waste.
A lean process usually looks like this:
That is enough for most roles. It is also enough for remote hiring across borders, if your task and interview are designed well.
Many teams get sloppy. This occurs when they standardize the wrong thing.
You do not need candidates to sound American, mirror your founder, or perform confidence in a Zoom room. You need them to be understandable, dependable, and easy to work with in an async environment. Those are different standards.
For cross-border hiring, score the habits that reduce friction:
That prevents a common mistake in US companies hiring Latin American talent. They confuse accent, style, or cultural familiarity with communication skill. Those are not the same thing.
A good process filters for work habits that travel well across borders, not for people who feel familiar in a 45-minute call.
A strong soft-skills process does more than improve hiring quality. It makes the company easier to run.
Managers spend less time translating vague updates. Handoffs get cleaner. Async work stops breaking because someone waited too long to ask a question. Teams trust each other faster because expectations are clear from day one.
That is the point.
If your current process feels slow, do not remove the structure. Remove the duplication. Keep the steps that reveal how someone will operate on a remote team where half the communication happens in writing and nobody is around to clean up misunderstandings in real time.
Audit your last three bad hires. Ignore the resume. Ignore the technical screen. Ask one question: which behavior did we fail to test?
Fix that, and your hiring process gets faster and sharper at the same time.
