Skip to main content
Venture Stories

Hiring Technical Talent with Kathy Copic and Lindsay Pettingill

57 min episode · 2 min read
·
Kathy Copic

Episode

57 min

Read time

2 min

Topics

Career Growth, Startups, Software Development

AI-Generated Summary

Key Takeaways

  • First Technical Hires: Founding engineers need strong cross-functional communication skills to gather requirements, explain trade-offs, and recruit future team members—not just coding ability. Poor communicators struggle to align with company direction and fail to excite interview candidates about joining.
  • Interview Curiosity Test: Evaluate candidates across three interview stages by tracking how their questions evolve. Strong candidates ask progressively deeper questions about the company, sector, team structure, and growth plans at each stage, demonstrating genuine interest and learning ability beyond technical skills.
  • Diversity From Day One: Building diverse teams becomes exponentially harder after the first ten hires. If early hires are homogeneous, future candidates notice and self-select out. Direct recruiters to actively source underrepresented candidates and examine applicant pools at every stage to correct imbalances early.
  • Brand Through Specificity: Compete with large tech companies by writing detailed job descriptions that explain actual first projects, specific challenges, interview process stages, and team dynamics. Specificity helps candidates self-select for fit rather than competing on generic brand recognition or compensation alone.

What It Covers

Kathy Copic and Lindsay Pettingill explain how early-stage startups can hire technical talent effectively, covering role definition, interview processes, diversity strategies, and competing with large tech companies for engineering and data science candidates.

Key Questions Answered

  • First Technical Hires: Founding engineers need strong cross-functional communication skills to gather requirements, explain trade-offs, and recruit future team members—not just coding ability. Poor communicators struggle to align with company direction and fail to excite interview candidates about joining.
  • Interview Curiosity Test: Evaluate candidates across three interview stages by tracking how their questions evolve. Strong candidates ask progressively deeper questions about the company, sector, team structure, and growth plans at each stage, demonstrating genuine interest and learning ability beyond technical skills.
  • Diversity From Day One: Building diverse teams becomes exponentially harder after the first ten hires. If early hires are homogeneous, future candidates notice and self-select out. Direct recruiters to actively source underrepresented candidates and examine applicant pools at every stage to correct imbalances early.
  • Brand Through Specificity: Compete with large tech companies by writing detailed job descriptions that explain actual first projects, specific challenges, interview process stages, and team dynamics. Specificity helps candidates self-select for fit rather than competing on generic brand recognition or compensation alone.

Notable Moment

Copic reveals that interrupting candidates mid-explanation during technical interviews serves as a reliable test for collaboration readiness. Candidates who gracefully handle interruptions to define acronyms or clarify details demonstrate the communication flexibility startups require, while defensive responses signal poor team fit.

Know someone who'd find this useful?

Episode Transcript

Hey, everybody. This is Ben Kesnoka, cofounder and partner at Village Global, a network driven venture firm. And this is our podcast where we go deep on all things business and technology with world leading experts. I heard we have a lot of, first timers on on this call. We're so we're really glad you're here, and excited to share, learnings with you. So just to get started, you know, Cathy, this we don't wanna take this for granted in terms of, like, understanding what technical role actually means. So can you just kick us off with an explanation there? What do we mean by hiring for technical roles? Yeah. Sure. Sure. Yeah. Thanks for having me. Sometimes people don't even like the word technical. But I think here, just to kind of set the stage, we're talking about roles where there's some code or data component to them. So it'd be engineering, could be data, AI machine learning, folks where people are touching keyboard, thinking building out models where people are building part of the product. I think, there's a lot in common with hiring for technical and nontechnical roles. I'm happy to talk about what's what's the same, what's different, I think. Yeah. I think that'd be great. Let's get right into that. Right? What is the same, when you're hiring for technical and nontechnical and and when you're not? Yeah. So I think, actually, all most of it is the same. So for folks who are coming from a nontechnical background, they don't consider themselves software engineers or data folks. There might be a lot of, like, imposter syndrome worry about hiring for folks coming from these technical backgrounds. But, actually, I would say, I think a lot of the hiring and scoping of the roles is very, very similar, especially as the tools and techniques used to do things like sales, marketing, product, operations are also changing a lot. So maybe five, ten years ago, folks in sales or marketing were or product were not using a lot of complicated tools. But now it's like the tool landscape for every kind of role has really exploded. And so if you're hiring folks into whatever roles in background that you've come from, probably they ended up using a lot of different you know, even for things like product confluence, there's notion. There's lots of different things out there for tracking things, for building stuff. And so I think when you're assessing folks for their skills, there's a lot in common about how you assess for technical skills or skills for other roles. And, when you're assessing people for their, like, interest and ability to be productive in the start up environment, there's a lot that's the same. And I think when you're assessing folks for culture, for how much they're gonna fit into your team, what they're gonna add to your team, there's a lot that's the same. Really interesting. I I I'm I think that last …

Get the full transcript (10,547 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Venture Stories transcripts →

You just read a 3-minute summary of a 54-minute episode.

Get Venture Stories summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Venture Stories

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Investing Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Venture Stories.

Every Monday, we deliver AI summaries of the latest episodes from Venture Stories and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime