How to Hire Employees — What 10,000+ Hours of Interviews Actually Taught Me

When I set out to write this article, the #2 ranking page on Google for “how to hire employees” was the IRS.

The God-damn IRS. That cockroach of an bureaucratic pit.

An agency that has never hired a productive employee in its existence. An agency whose entire function is to make it harder for you to hire, pay, and retain people.

An entity that does nothing but leech and take value from the people of the world actually producing — trying to give advice about how to create value in the world.

It’s a disgrace.

That’s like your divorce attorney writing a guide on how to have a happy marriage.

Or a 400 pound personal trainer teaching you how to get a 6-pack.

And the rest of page one? LinkedIn. Indeed. Generic HR platforms listing the same ten steps that have been recycled since 2007.

“Step 1: Determine what you need. Step 2: Write a job description. Step 3: Interview candidates.”

Groundbreaking stuff.

I’ve personally overseen more than 10,000 interviews at my company. We’ve placed over a thousand people into businesses across the US, UK, and Europe. I’ve put in my 10,000 hours on this — literally.

And the single biggest thing I’ve learned?

You’re hiring a person. Not a skill set.

Anyone who knows X Platform can learn Y Platform. Anyone who knows A Software can learn B Software. It’s all the same. Only the colors and logos change.

Skills transfer. People don’t.

If you hire someone with the perfect resume and the wrong personality, you’re going to spend the next six months managing someone who technically knows how to do the job but makes everything harder.

If you hire a sharp, hungry, self-aware human being who’s missing one tool on your checklist — they’ll figure it out in a week and outperform the “perfect candidate” by week two.

But here’s the part nobody talks about:

Everyone wants A-players. Are you an A+ company?

Are you enthusiastic? Is your team bought in? Do people leave interview #1 and actually want to come back for interview #2?

Or are you running a disorganized hiring process with four rounds of interviews, shifting requirements, and a “we’ll get back to you” that turns into three weeks of silence?

A-players have options.

They are evaluating you just as hard as you’re evaluating them. If your company isn’t somewhere people are excited to work, the best candidates will pass — and you’ll be stuck choosing from whoever’s left.

That’s the foundation. Now let’s get into what actually works.

---

Last Updated: March 9th, 2026

---

“Hire Slow, Fire Fast” Is Wrong

Every business guru on the internet screams this.

“Hire slow. Fire fast. Promote fastest.”

Sounds great on a podcast.

And by the way — many of those “gooroos” who made this famous?

Those are the exact people the IRS is auditing right now.

They’re uncovering the leased Lamborghinis, the rented mansion photoshoots, and the $50,000/month lifestyles funded by course sales to people who can’t afford the course. These are not operators. These are performers. And they’re telling you how to build a team.

Here’s what actually happens when you “hire slow”:

You find someone great. You’re 90% sure. They check every box except one thing you can’t quite articulate. So you say, “Let’s keep looking. Let’s be thoughtful about this.”

Three weeks later, that person took another job. You’re still looking. Two months in, you’re exhausted. You start lowering your standards. You hire out of desperation. Now your new problem starts because you were indecisive.

That’s not “hiring slow.” That’s analysis paralysis, and it kills companies slowly but surely.

I’m not saying to hire recklessly. Don’t hire just to fill a seat. A warm body in a role is worse than an empty role — because a warm body costs money, takes management energy, and produces the illusion that the position is handled when it isn’t.

But if you’ve done the work — you’ve interviewed properly, you’ve tested them, and you’re sitting at 90% confidence — act.

There’s a concept in Morgan Housel’s The Psychology of Money that changed how I think about hiring.

He tells the story of Warren Buffett. Buffett’s net worth is $84.5 billion.

Of that, $81.5 billion came after his 65th birthday.

And $84.2 billion came after his 50th.

Read that again.

Over 96% of his wealth was accumulated after the age most people start thinking about retirement.

Buffett didn’t make one genius trade. He didn’t time the market. He didn’t find one perfect investment and bet the farm. He started investing at age 10. By 30, he was a millionaire. But the vast majority of his fortune wasn’t built in those early decades. It was built by staying in the game for seventy-five years and letting compounding do what compounding does.

His skill is investing.

His secret?

Time.

Housel says that we’re wired to chase the highest possible return — the one big win, the perfect play. It’s what draws people back to the blackjack boards in Vegas and gets poor people to buy Lotto tickets with their food stamps.

But long-term company health doesn’t care about perfect plays.

Then there’s Rick Guerin. Buffett and Charlie Munger’s third partner. Just as smart. Same investing instincts. Same circle. But Guerin was in a hurry. He used leverage to accelerate his returns. When the 1970s bear market hit, he got margin-called and had to sell. Many of the Berkshire Hathaway shares that Buffett still holds today — the ones worth billions — once belonged to Rick Guerin.

Buffett said himself: “Charlie and I always knew we would become incredibly wealthy. We were not in a hurry. Rick was just as smart as us. He was in a hurry.”

Guerin failed because he tried to force an outcome instead of letting the process work.

Sound familiar?

Hiring works the same way.

You don’t need to find one perfect employee.

You need to make enough good hires, over enough time, that the compounding effect of a strong team does the work for you. You aren’t going to get it right every time. Any hiring agency or expert who claims this is simply wrong.

Every month you spend paralyzed looking for the “perfect” candidate is a month your business isn’t compounding. Every month you delay because you’re 90% sure but not 100% is a month of lost output, lost revenue, and lost momentum.

And just like Guerin — the people who blow up at hiring aren’t usually the ones who made a bad hire. They’re the ones who made no hire at all because they were trying to force a certainty that doesn’t exist.

It doesn’t exist. We have a stellar track record at HireUA. And sometimes, even though we really, really try to make sure it doesn’t — we place a potato into a business. A useless, brown, spud. It happens. And we fix it when it does.

But nobody is perfect.

Steph Curry doesn’t shoot 100% from the line.

Cristiano Renaldo doesn’t make 100% of his penalty shots.

Max Verstappen doesn’t win 100% of the races he enters.

Tom Brady didn’t win every Super Bowl he entered.

But you have to take your shots on goal.

The best return in hiring isn’t the perfect candidate. It’s consistent, good hires that you stick with long enough for the team to compound.

Make the 90% decision. Move. If it doesn’t work out — you’ll know fast, and you’ll fix it fast.

That’s the real version. Not “hire slow.” Hire decisively.

---

The Thread Method — How to Actually Interview People

Before I started my recruiting company, I ran a dating coaching business called This Is Trouble. Over a million unique readers per year on my little blog. Over $1M in lifetime revenue.

The entire business was built on one skill: Teaching people how to have real conversations.

Not scripts. Not pickup lines. Not “what to say when she says X.”

How to listen. How to follow what someone just said into something deeper. How to not just wait for your turn to talk.

That skill is the single most transferable thing I brought into recruiting. And after 10,000+ interviews, I can tell you with certainty:

The reason most interviews are useless is because the interviewer is reading a checklist instead of having a conversation.

They ask a question. They get a rehearsed answer. They write down the answer. They move to the next question.

They never pull the thread.

Here’s what I mean. Most interviewers ask these same ten questions. Every candidate on earth has rehearsed answers for all of them. And every interviewer accepts the surface answer and moves on.

I don’t.

1. “What’s your biggest weakness?”

Surface answer: “I care too much.”

Thread:

“Why do you care so much?”

“Because it physically makes me sick when I don’t perform my best.”

“Why is that? Were you competitive as a child?”

“Yeah, my parents were both athletes. Second place wasn’t really a thing in our house.”

Now you know something real. You know this person is driven by internal standards, not external validation. You know where the drive comes from. You know they probably hold themselves — and their teammates — to a high bar. Or maybe the thread goes differently and you discover they’re just neurotic and anxious, not driven. Either way, you know. Because you pulled the thread instead of writing down “cares too much” and moving to question two.

2. “What’s your biggest strength?”

Surface answer: “I’m a great communicator.”

Thread:

“What do you mean by that? Give me a specific example.”

“I managed a team of five and had to coordinate across three departments.”

“What was the hardest part of that coordination?”

“Getting the engineering team to commit to deadlines.”

“How did you handle that?”

“I started sending weekly status summaries so they couldn’t claim they didn’t know the timeline.”

Now you’re hearing about problem-solving, proactive communication, and how they handle friction with other departments. “Great communicator” turned into a real story with a specific tactic. That’s the difference.

3. “What would your last boss say about you?”

Surface answer: “She’d say I’m reliable and hardworking.”

Thread:

“If I called her right now, what’s one thing she’d say you need to improve?”

Pause. This is where it gets interesting. The surface answer was about strengths. Now you’re asking them to predict their boss’s criticism. Watch the body language. Watch how long they take to answer. If they say, “Honestly, she’d probably say I take on too much” — keep pulling. “Why do you take on too much?” “Because I don’t trust other people to do it right.” Now you’re uncovering a potential delegation problem. Or you’re uncovering someone who’s been surrounded by underperformers and had to compensate. The thread tells you which one.

4. “Tell me about a time you handled conflict.”

Surface answer: “A coworker and I disagreed on a project direction. We talked it out and found a compromise.”

Thread:

“What was the specific disagreement?”

“He wanted to launch a feature without testing. I thought we needed another two weeks.”

“Did you bring it to your manager?”

“Yes.”

“What did your manager say?”

“He sided with the other person.”

“Did it work out? Did launching early cause problems?”

“Yeah, we had three major bugs the first week.”

“Did your manager come back to you?”

“No.”

“Did you bring it up?”

“No.”

“Do you regret not bringing it up?”

Now you’re deep. You’re learning whether this person advocates for their position or folds when overruled. Whether they hold grudges. Whether they say “I told you so” or let it go. Whether they have the spine to push back AND the maturity to move forward. None of that shows up in “we talked it out and found a compromise.”

5. “Where do you see yourself in 5 years?”

Surface answer: “I’d like to be in a leadership position managing a team.”

Thread:

“What is it about management that appeals to you?”

This answer tells you everything. Some people want management because they want status. Some want it because they genuinely want to develop people. Some want it because they think it means less hands-on work.

“Is it the people development side? The strategic side? Or is it more that you want to have influence over how things get done?”

Each of those is a completely different person with a completely different motivation. The surface answer — “leadership position” — tells you nothing. The thread tells you what’s actually driving them.

6. “Why are you leaving your current job?”

Surface answer: “Looking for new challenges and growth opportunities.”

Thread:

“What would ‘growth’ look like for you specifically?”

“I want to take on more responsibility.”

“What kind of responsibility? Managing people? Bigger projects? Different skill sets?”

“Managing people.”

“What stopped you from getting that at your current company?”

“They don’t promote from within.”

“Have you asked?”

“No.”

Now you’re finding out if they’re running FROM something or running TO something. And in this case — they haven’t even asked for the promotion they say they want. That’s a signal. Maybe the company really doesn’t promote internally. Or maybe this person doesn’t advocate for themselves. The thread reveals which one.

7. “What’s your greatest professional achievement?”

Surface answer: “I led a project that increased revenue by 30%.”

Thread:

“How big was the team?”

“Just me and one other person.”

“What was the timeline?”

“About four months.”

“What was the hardest part?”

“Getting buy-in from leadership on the budget.”

“How did you get it?”

“I built a projection showing what we’d lose by NOT doing it.”

Now you’re hearing about initiative, persuasion, working with limited resources, and selling ideas upward. The “30% revenue increase” was a headline. The thread gives you the story behind the headline — and that story is where you actually evaluate the person.

8. “Tell me about a time you disagreed with a decision made at work.”

Surface answer: “My manager decided to change our process. I didn’t agree, but I went along with it.”

Thread:

“Did you voice your disagreement to your manager?”

If yes: “What did you say? Was there a compromise? Did you document it? Did their way work out — or would yours have been better? If yours would have been better, did they ever come back and acknowledge it?”

If no: “Why didn’t you say anything? Do you regret it? Did the decision end up going the way you thought it would?”

This is a full decision tree. Every answer branches into a different follow-up. And every branch reveals something different about the person — whether they have conviction, whether they can disagree constructively, whether they hold back out of fear or respect, and what they do when they turn out to be right.

9. “Why do you want this job?”

Surface answer: “Because I’m interested in the industry.”

Thread:

“What specifically about this company appeals to you?”

“I like recruiting and outsourcing.”

“OK — is there a particular part of what we do that interests you? Certain roles we place? Something about our mission or the way we operate?”

If they’ve done their homework, this is where it shows. They’ll reference something specific — a case study, a blog post, the fact that you source from a particular region, your core values on the website.

If they haven’t, they’ll fumble.

“I just think it’s a cool company.”

That tells you they don’t want THIS job. They want A job. And there is a MASSIVE difference.

Someone who wants a job at your company did the work before the interview. They read your website. They watched a video. They have specific questions. Someone who wants A job sent the same resume to thirty companies and yours happened to respond first.

10. “What type of work environment do you like?”

Surface answer: “I like a collaborative, supportive team with clear communication.”

Thread:

“Was your last job like that?”

“Yeah, mostly.”

“Were the KPIs being met?”

“Not really.”

“So the environment was supportive and collaborative — and the company was underperforming. Do you think that environment was actually the best thing for that company?”

…..

Watch them process that. You just caught them in their own logic. They said they want a happy, supportive environment. Their last job was exactly that. And it wasn’t working.

Now, the trick is: Let them squirm. Be silent. Do not fill it. Get comfortable with watching people be uncomfortable.

Maybe the answer is “Yeah, fair point — we were too comfortable.” That’s self-awareness. That’s a good sign.

Or maybe they double down: “Well, the problem was management, not the culture.”

Fine.

Pull that thread too. “What was management doing wrong?” And now you’re back in a real conversation.

The point of all ten of these is the same:

The question is not the interview. The question is the door. The interview is what you find when you walk through it.

If you ask ten questions and get ten surface answers, you learned nothing. You wasted an hour confirming that this person can perform well in a structured Q&A — which has zero correlation with whether they’ll perform well in your business.

Follow the thread. That’s the skill. And it’s a skill most interviewers have never been taught.

---

The Lightning Round

This lives inside the thread philosophy but it deserves its own moment.

At some point in every interview, I run a lightning round. Nothing to do with the job. Everything to do with the person.

Does pineapple belong on pizza?

Ferrari or Lamborghini?

What did you want to be as a kid?

Snow or surf?

Favorite place you’ve traveled?

What’s the craziest thing you’ve done?

Not because the answers matter. Because I’m watching whether this person HAS answers.

If someone can’t have an opinion about pizza, how are they going to push back when a client sends a bad brief? How are they going to flag a problem in a process? How are they going to tell you something isn’t working?

People with no personality in an interview have no personality at work. And personality — the kind that lights up, that has opinions, that engages — is what separates someone who does the job from someone who makes your company better.

The lightning round takes two minutes. It tells me more about someone than twenty minutes of behavioral questions.

---

BONUS: “WHAT Questions Do You Have For Me?”

This is not “Do you have any questions for me?”

That’s a throwaway line at the end of an interview. It implies the answer could be “no” and that’s fine.

I say, “WHAT questions do you have for me?” I put a lot of emphasis on the first word, even as I ask it.

I assume they have questions. I’m asking what they are. And I’m judging them heavily based on the answer.

Here’s what separates a great candidate from a warm body at this stage:

Good questions show that someone has done research, thought about what the role actually looks like day to day, and is evaluating whether this company is the right fit for THEM — not just hoping you’ll say yes.

Bad questions show that someone is thinking about what they can extract from the job rather than what they can contribute to it.

Great questions sound like this:

“I saw a Glassdoor review from someone in a similar role who mentioned the workload was intense during client onboarding periods. Do you think that person had some valid points, and how has the team addressed that since?”

That’s someone who researched the company, found real feedback, and is asking about it directly instead of pretending everything looks perfect. That takes guts and preparation.

“What does the current workflow look like for this role? How messy is it, honestly? Is there an existing system I’d be stepping into or would I be building from scratch?”

That’s someone who’s already thinking about what they’ll be working with on day one. They’re not asking IF the job is hard. They’re asking what KIND of hard it is.

“Do you believe the current team has the capacity to handle the projects coming in over the next six months, or is this hire specifically because you’re stretched?”

That’s someone evaluating whether they’re walking into a functioning team or a fire drill. It also tells you they understand that WHY you’re hiring affects what the job actually looks like.

“What does success look like in this role at 90 days? What would make you say this worked out great?”

That’s someone who’s already thinking about delivering results. Not about settling in. About performing.

“I noticed your company went through [specific change — a rebrand, a pivot, a leadership transition]. How has that affected the team dynamic, and what does that mean for this role going forward?”

That’s someone who read beyond the careers page and is thinking about context. They want to understand what they’re walking into, not just what the job description says.

Now compare those to:

• “How many vacation days do I get?”
• “What’s your work-from-home policy?”
• “How soon do people usually get promoted?”
• “Is there a team happy hour?”
• “What are the hours?”

Those aren’t bad questions on their own. But if that’s ALL someone asks — if their entire curiosity about your company is about PTO and perks — they’re telling you where their priorities are.

The best interview questions I’ve ever heard from candidates were ones where they clearly read the website, watched a video, and came with something specific.

“I noticed you source primarily from Eastern Europe — have you expanded into Latin America? What’s the quality difference?”

That’s a person who wants THIS job. Not A job.

I don’t ask follow-up questions during this section. I just listen.

What they ask — and what they don’t ask — tells me everything.

---

Know What Your Company Stands For (Before You Hire Anyone)

Here’s the thing:

If you can’t say two or three things your company stands for — like, actually stands for, not the poster on the wall in the break room — then you have no basis for evaluating whether someone fits.

You’re just guessing. Vibes. Gut feeling. “Seemed nice in the interview.”

That’s not a screening process. That’s a coin flip.

This isn’t some abstract HR exercise. The biggest companies in the world treat their core values as hiring filters — and it shows in who ends up on their teams.

Netflix

Netflix built what’s arguably the most influential hiring document in corporate history — their culture deck.

Sheryl Sandberg called it one of the most important documents ever to come out of Silicon Valley. The core premise: they’re a professional sports team, not a family. Performance is the standard. They run what they call the “Keeper Test” — managers ask themselves, “If this person told me they were leaving, would I fight to keep them?” If the answer is no, they part ways with a generous severance package. Not a PIP. Not a 90-day improvement plan. A goodbye. Their values are specific and measurable: judgment, communication, curiosity, courage, selflessness, inclusion, integrity, impact. Every hire gets evaluated against them. “Adequate performance” isn’t good enough. Netflix hires for extraordinary — and fires for average.

Apple

Apple doesn’t publish a flashy culture deck.

But their values are embedded in everything they build: accessibility, privacy, innovation, environmental responsibility. When Apple designs a product, every decision traces back to one question — does this serve the user?

Steve Jobs said it himself: “You’ve got to start with the customer experience and work back toward the technology, not the other way around.” That obsessive focus on user experience isn’t just a product philosophy. It’s how they hire. If you don’t think that way instinctively — if your first question is “what’s technically possible” instead of “what does the user actually need” — you don’t last at Apple.

Chiptotle

Chipotle — a fast food chain — has clearer operational values than most tech companies.

“Food with Integrity” means they use 53 ingredients you can pronounce, source responsibly raised meat, and don’t use GMOs. That’s not a marketing slogan. That’s a sourcing standard that drives every hiring decision in their supply chain. Eighty-four percent of their restaurant management positions are filled through internal promotion. They hire for values and develop from within — from a single restaurant in Denver to over 3,500 locations.

The point is not that you need a 125-slide culture deck or an 80-year-old mantra. The point is that every company that hires well knows exactly what it stands for — and uses those values as a filter, not a decoration.

At HireUA, our core values are Win-Win-Win, Hospitality, and Real = Results.

Win-Win-Win means every decision has to work for the client, the candidate, and HireUA. If any one of those three loses, the model breaks.

Hospitality means treating everyone — clients, candidates, even people we reject — like guests at a five-star hotel.

Real = Results means we don’t do theater. No alignment meetings. No updates that sound productive but produce nothing. Did the client get the hire? Did the hire work out? That’s the scoreboard.

Those three things drive every hiring decision we make internally.

When I interview someone for HireUA, I ask, “What do you think is so difficult about the recruiting industry?”

If they can intuitively get to something like, “It must be hard to keep both sides happy — the client wants one thing, the candidate wants another, and you’re in the middle” — that person gets Win-Win-Win. They don’t have to say it perfectly, nor do I expect them to. They don’t have to quote our website. But if they can identify that core tension without being told, they understand the value.

If they say something generic like, “Finding clients” — they’re not seeing the full picture. That’s not a disqualifier on its own. But it tells me they don’t naturally think about all sides of a transaction.

What are YOUR core values? Not the ones you put on a careers page because a consultant told you to. The real ones. The ones you’d fire someone over if they violated them.

If you can answer that — you can build interview questions that reveal whether someone aligns with those values.

If you can’t answer that — go figure it out before you hire anyone. Because without it, you’re screening for skills and hoping the personality works out.

That’s how most companies hire. And that’s why most companies have turnover problems.

---

The GWC Framework — Three Yes-or-No Questions

I’m going to simplify the entire candidate evaluation process into three questions. Gun to your head. Yes or no.

Do they GET it?

Do they understand what this job actually is? Not the title. Not the description. The reality.

If the role is “account manager” and the reality is “you’re going to get yelled at by clients every day and your job is to keep them from leaving” — do they get that? Or do they think “account manager” means “send a few emails and join a weekly call”?

You can test this. Describe the worst day in the role. Describe the hardest client. Describe the moment where everyone is stressed and the ball is in their court. Watch their face. Do they lean in or lean back?

Do they WANT it?

Not a job. This job.

This goes back to the “why do you want this job” thread. Did they research the company? Do they know what you do? Can they articulate why THIS role at THIS company?

Someone who wants a job at your company came prepared. They have specific questions. They reference specific things.

Someone who wants a job came because you were hiring and they need a paycheck.

Both might be competent. Only one is going to stick around when things get hard.

Do they have the CAPACITY?

And here’s where you have to be honest with yourself:

Does this role need a killer? Or does it need a floor?

Not every role needs a genius. Some roles need someone who can reliably execute a repeatable process without screwing it up. That’s not an insult. That’s reality. If you’re hiring someone to categorize transactions in QuickBooks, you need accuracy and consistency — not a visionary.

Other roles — your Operations Manager, your senior sales person, your lead Developer — those need someone who can think independently, solve problems nobody anticipated, and make judgment calls without being told what to do.

Match the evaluation to the role. Holding an entry-level hire to the same standard as a senior leader is how you end up searching for six months and finding nobody.

3 questions. Yes or no.

If all three are yes — hire them. If any one is no — pass.

Don’t overthink this. The simplicity is the point.

---

Job Descriptions — What Everyone Gets Wrong

I put this section here on purpose. Counter-intuitive.

Because if you made it this far and you’re thinking, “Wait — I still don’t actually know what this person is going to DO every day…” then maybe you need to answer that question before you do anything else, bucko.

This is the single most common problem we see. And we see it multiple times a week.

Someone books a call with us. They want to hire. They have a title in mind. And when I ask, “What is this person going to DO every day?” — they can’t answer it in one sentence.

That’s the test. One sentence. If you can’t describe the role in one sentence, you’re not ready to hire.

“Design WordPress pages in Elementor for our agency’s client sites.”

That’s a sentence. That’s a search we can run today.

“Help with the website and also some design stuff and maybe social media and possibly email campaigns.”

That’s a wish list. Come back when you know what you need.

Here’s a real example from last week. A company came to us looking for a “Technical Project Manager.”

The job description listed fifteen responsibilities. Notion was their primary tool.

Notion.

Serious Project Managers — the ones managing six-figure builds, coordinating engineering sprints, handling stakeholder communication across time zones — don’t use Notion as their core PM tool.

Notion is not a serious project management platform.

Sorry, not sorry.

Coda is superior anyway.

That single detail told us this role wasn’t what the title said it was. They didn’t need a Technical Project Manager. They needed an organized person who could keep track of tasks in Notion and make sure deadlines got met. That’s a different hire, at a different price, requiring a different search.

The title was wrong. The tool was wrong. The expectations were misaligned from the first sentence.

And here’s the other thing we see constantly:

All the responsibility…but none of the authority.

Companies write job descriptions that say, “Own the client relationship. Drive project timelines. Manage cross-functional teams. Ensure quality standards are met.”

Then they hire someone, give them the title, and micromanage every decision they make.

You gave someone the RESPONSIBILITY of owning the client relationship. But you didn’t give them the AUTHORITY to make a call without checking with three people first. So what you actually hired was an expensive messenger. Not a manager.

If you’re going to write “own” in a job description, that person needs the ability to actually own it. Make decisions. Push back on scope creep. Say no to a client when necessary. If you’re not ready to give someone that authority — rewrite the job description to reflect what you’re actually offering.

The gap between what job descriptions promise and what companies actually allow is where most hires fail. Not because the person wasn’t capable. Because the company wasn’t ready to let someone be capable.

The Communist Factory — What Happens When You Hire Wrong

I wrote a full piece on this. It’s called The Communist Factory: How Thriving Start-Ups Evolve, or Die.

I almost killed my company with kindness.

Not the fluffy, feel-good kind. The dangerous kind. The kind that lets people feel busy while nothing actually moves.

In a Soviet factory, nobody gets judged on whether the car actually drives. They get judged on how many cars they reported that they produced.

That happens in businesses every day. Updates that sound productive. Slack messages that look professional. “Alignment meetings” that produce nothing but more alignment meetings.

Eventually, participation trophies replace results. Theater replaces performance. And the company — without you realizing it — stopped being judged on whether it actually produces the cars.

I’ve watched this play out in my own company and in companies we’ve placed people into. The pattern is always the same:

You hire good people. Things work. You step back. New hires come in without the same standards. Titles inflate. Activity replaces output. Nobody flags it because everyone is busy. Revenue slides. And by the time you notice, the culture has already shifted.

If anything in this section made you uncomfortable — go read it. That discomfort is useful.

Read The Communist Factory: How Thriving Start-Ups Evolve, or Die.

---

The Committee Problem

You must have one person whose neck is on the line if the hire doesn’t work out.

When you have 3, 4, 5+ people — it’s a committee. And committees are where hiring goes to die.

It sounds smart on paper. “Let’s get input from all stakeholders. Let’s make sure everyone’s aligned. Let’s build consensus.” Blah blah blah.

Here’s what actually happens:

Everyone adds requirements. Nobody strips requirements back. The ideal candidate goes from “strong developer with React experience” to “strong developer with React, TypeScript, Kubernetes, AI/ML experience, fin-tech background, startup mentality, fluent in Swahili, and willing to work EST hours and Saturday mornings.”

That person doesn’t exist.

And six weeks months later, nobody has been hired. The committee is still “being thoughtful.” And the business is still running without the person they needed two months ago.

One person should own the hiring decision. Everyone else can give input. But ONE person makes the call and takes the responsibility if it doesn’t work out.

No one’s neck on the line = no one making a decision = no one getting hired.

---

Your Screening Changes Based on What You’re Hiring For

Everything in this article — the thread method, the Pineapple Test, the GWC framework — applies to hiring broadly. But your specific screening process should change dramatically based on the role.

An Executive Assistant needs to follow conversational threads. They need personality. They need to anticipate what you need before you ask. The soft skills ARE the job.

A Developer doesn’t need to be a conversationalist. They need to write clean code, solve technical problems, and communicate clearly in async environments. The hard skills dominate.

A Social Media Manager needs taste. A Bookkeeper needs precision. An Operations Manager needs to think in systems. A Video Editor needs creative judgment.

The pineapple pizza question matters a lot when you’re hiring an EA. It matters almost zero when you’re hiring a backend engineer.

We’ve written deep guides on how to hire for every one of these roles:

→ How to Hire a Virtual Assistant

→ What Does an Executive Assistant Do?

→ How to Hire an Inbox Manager

→ How to Hire a Social Media Manager

→ How to Hire an Operations Manager

→ How to Hire a Bookkeeper

→ How to Hire a Video Editor

→ How to Hire Remote Developers

→ How to Hire a Web Designer

→ How to Hire a Media Buyer

→ Offshore Outsourcing — The Complete Guide

Each one covers the specific screening, pricing, frameworks, and case studies for that role. If you know what you’re hiring for — start there.

---

How to Hire Remote Employees

Remote hiring follows the same principles as everything above. The thread method works. The GWC framework works. Core values still matter.

What changes is the weight you put on communication.

In an office, a mediocre communicator can survive because they’re physically present. You can tap them on the shoulder. You can read their face in a meeting. The environment compensates for what they lack.

Remote work strips all of that away. If someone can’t communicate clearly in writing, can’t provide proactive status updates, and can’t manage their own time without someone checking in — remote won’t work. No matter how skilled they are.

The other shift is trust. You have to be willing to manage output rather than activity. If your instinct is to track hours, monitor screens, and check that someone is online at all times — remote hiring is going to be painful. For you and for the person you hire.

---

How to Hire International Employees

This is where it gets interesting.

The honest one-paragraph version: Hiring internationally is the same as hiring domestically, with one critical addition — you have to understand the culture.

I’ve lived abroad for over ten years. Poland. Ukraine. Portugal. That’s the real competitive advantage of what we do at HireUA. We can see what American business owners are looking for and what international candidates bring to the table — and more importantly, where those things align and where they don’t.

The cultural differences are real. Communication styles are different. Work expectations are different. What “proactive” means in Ukraine is different from what it means in the Philippines, which is different from what it means in Argentina.

Figure out what region interests you. Understand the culture. Then go for it.

---

FAQ

How do I hire good employees?

Stop looking at resumes and start having real conversations. Skills transfer between tools and platforms. Personality, work ethic, and cultural fit don’t. Use the thread method to get past rehearsed answers, define your core values before you start interviewing, and evaluate candidates with the GWC framework: Do they get it? Do they want it? Do they have the capacity?

How do I hire employees for a small business?

The same way a big company should — but with less bureaucracy and faster decisions. Small businesses actually have an advantage here because the founder is usually doing the interviewing. You’re closer to the work, you know exactly what the role needs, and you can make a decision without running it through a committee. Use that speed. Don’t try to replicate corporate hiring processes at a company with eight people.

How do I find employees to hire?

Job boards (LinkedIn, Indeed) cast a wide net. Referrals from your existing team are usually the highest-quality source. Specialized agencies (like HireUA for international talent) pre-screen candidates so you’re only talking to people who’ve already been vetted. The best approach depends on the role, the budget, and how fast you need someone.

How much does it cost to hire an employee?

Depends on the role, the location, and the model. A US-based employee costs salary plus 25-35% in benefits, payroll taxes, and overhead. An international hire through HireUA typically costs 50-80% less for equivalent experience. We’ve published real pricing breakdowns in every one of our role-specific guides.

Should I hire full-time or part-time?

If the work is consistent and ongoing, full-time. If the work is variable or project-based, part-time or contract might make more sense. The mistake most people make is hiring part-time for a role that clearly needs full-time attention, then wondering why nothing gets done. Be honest about the workload before you decide.

How do I hire remote employees?

The same interview process applies. What changes is the weight on communication skills, self-management, and async work habits. If someone can’t communicate clearly in writing and provide proactive updates without being chased, remote won’t work regardless of their skills.

How do I hire international employees?

Understand the culture of the region you’re hiring from. Communication styles, work norms, and expectations vary significantly across countries. A dedicated guide is coming — in the meantime, our Offshore Outsourcing guide covers the framework for thinking about international hiring.

How long does it take to hire an employee?

Through HireUA, we set up interviews within 5-10 days. You’d interview 3-5 pre-vetted candidates and could have someone starting within 2-4 weeks. On your own, the timeline varies wildly — anywhere from 2 weeks to 6+ months depending on role complexity, how many people are involved in the decision, and whether you fall into the committee trap.

What’s the biggest mistake people make when hiring?

Hiring for skills instead of the person. A perfect resume with the wrong personality will cost you more in the long run than a strong person who needs two weeks to learn your tools. The second biggest mistake is not knowing what your company stands for — which makes every interview a guessing game instead of an evaluation.

---

How to Hire Employees — Final Thoughts

If you’ve read this far, you know more about hiring than 90% of the people posting jobs on LinkedIn right now.

• You know why “hire slow” is usually wrong.
• You know how to pull threads instead of reading checklists.
• You know that personality matters more than most interviewers give it credit for.
• You know that your company needs to stand for something before you can evaluate whether someone fits.
• And you know that one person needs to own the decision — not a committee.

What you do with all of that is up to you.

If you want HireUA to run the search — pre-vetted, interview-ready candidates set up within days — start here:

Book a call with HireUA.

If you want to handle it yourself, go back to the top and start with the one question that matters most:

What is this person going to DO?

If you know that, you’re ready.