Good platform hires earn founder trust fast, act before they're asked, and build systems instead of heroics. Look for operating experience founders respect, sound judgment about where to spend time, comfort with data and AI tools, and the ability to influence partners without formal authority. Test those traits with real work samples and structured interviews.
When I was on the founder side, the people at our investors who actually helped had two things in common. They knew what we were working on before we told them, and they moved fast. Neither of those shows up on a résumé, which is a big part of why platform hiring is hard to get right.
Platform roles also look different at every firm. One fund's head of platform runs events and the newsletter. Another's runs talent searches, LP reporting and the CRM. Great hires come from recruiting, marketing, banking, consulting and startups, and weak hires come from all the same places. Background predicts less than you'd hope. So define the job first, then test for the traits that make someone good at it.
Start with the outcomes, not the résumé
Before you write a job post, write down what this person must deliver in their first year. Be concrete. "Build community" isn't an outcome. "Every portfolio company with an open executive role gets qualified candidates within a week" is.
The outcomes tell you which kind of platform person you need:
| Role focus | Example first-year outcomes | Backgrounds that often fit |
|---|---|---|
| Talent | Candidates for every open role within a week, exec searches supported | In-house or agency recruiting, startup people ops |
| Community and events | A recurring event series with intros and outcomes tracked | Startup community, events, founder programs |
| GTM and BD | Customer intros tracked through to pilots and contracts | Startup sales or partnerships, enterprise BD |
| Data and ops | Portfolio data partners trust, reporting that runs on its own | Startup ops, fund ops, analytics |
| Generalist | Founder asks answered fast, a value-add log, one strong program | Chief of staff, early startup operator |
The table is illustrative. The point is that "platform" covers several jobs. The generalist version is the hardest one to hire for, because it needs judgment across all of them.
The traits that separate good from fine
Most candidates who reach a final round are smart, likeable and organized. Here's what separates the ones who turn out great.
Founders trust them quickly. Founders give their time to people who understand their problems. Usually that comes from having worked inside a startup, though not always. In the interview, listen for whether the candidate talks about founders as people with problems or as an audience for programs.
They act before they're asked. Good platform people watch for signals: a founder posting a role, an ask buried in an update, the same problem showing up at three companies. Then they reach out with something specific. Ask them: "Tell me about a time you helped someone who hadn't asked you for help yet."
They build systems, not heroics. A platform person who answers every request personally at midnight burns out by year two, and the work leaves with them. Look for people who have turned a repeated task into something that runs without them.
They're comfortable with data and AI, and a little skeptical of both. They should use AI tools every day and know where those tools fall short. A good answer to "how do you know the output is right?" mentions checking the source.
They can move partners without authority. Platform people rarely have formal power over partners, yet they need partners to make intros, show up to dinners and agree to goals. Ask how they got a busy senior person to do something they didn't have to do.
They spend time where it pays off. Ask what they'd stop doing in their first quarter. Strong candidates name things. Weaker ones only list what they'd add.
Use a work sample that looks like the real job
Interviews show you how someone talks about work. A work sample shows you how they do it. Keep it to two or three hours, give every candidate the same task, and pay for it if it runs longer.
Three samples that work well for platform roles:
- The update triage. Give the candidate four or five made-up founder updates with asks hidden inside: a hiring struggle in paragraph four, a vague request for "intros to banks," a runway number that quietly dropped. Ask them to find every ask, rank them, and draft the replies they'd send. This tests signal-spotting, judgment and writing at once.
- The mini-event plan. Three founders mentioned the same pricing problem this month. Ask for a one-page plan for a small event to help them, including who's in the room and how they'd know it worked.
- The partner email. Ask them to write the email that gets a partner to agree on two goals for the platform team this year.
Score each sample against the scorecard before you meet the candidate to discuss it. Otherwise a great conversation will lift a weak sample.
Red flags worth probing
None of these rule a candidate out on its own, but each one deserves a follow-up question:
- Programs over outcomes. They describe what they launched and never what it changed.
- A portal as the first idea. Founders rarely log in to portals. A candidate who leads with a resource hub may not have watched how founders actually work.
- No examples of saying no. Platform work is an endless stream of requests. Someone who has never turned one down will drown.
- Heroics as the main story. "I worked weekends for three months" tells you about effort, not about a system.
- Vague about results. Ask for a number. If they can't give one, ask how they'd know whether their last program worked.
For references, go beyond the names the candidate offers. Ask to speak with one or two founders they supported (with the candidate's permission, of course). Founders will tell you quickly whether this person made their life easier or gave them homework.
How do you evaluate platform candidates consistently?
Agree on a scorecard before the first interview, give every candidate the same work sample, and assign each interviewer specific traits to probe. Interviewers score independently with evidence before the debrief. Then compare scores trait by trait, not on overall impressions, so the loudest voice in the room doesn't decide.
A simple loop for a four- or five-person panel:
- Before interviews. The hiring lead shares the scorecard and assigns traits. A partner covers partner influence, a portfolio founder covers founder trust, and a platform peer covers systems and data.
- During interviews. Each interviewer asks for specific stories, with dates and results, about their assigned traits.
- Right after. Everyone scores in writing, with a line or two of evidence per rating, before talking to anyone else.
- Debrief. Go trait by trait. Where two scores are more than a point apart, the people furthest apart explain their evidence.
Putting a portfolio founder on the panel is worth the ask. They'll spot a candidate who sounds great to investors but would wear founders out.
What should a platform job scorecard include?
A scorecard should state the role's mission in one sentence, three to five outcomes the hire must deliver in the first year, and the competencies needed to get there. Each competency gets a definition and a rating scale with examples of weak, solid and strong evidence, so interviewers score against the same bar.
Here's an illustrative scorecard for a generalist platform hire at a seed fund with around 30 companies.
Mission: Make every founder in the portfolio feel the firm's help within days of needing it.
First-year outcomes:
- Every founder ask in an update gets a response within five business days.
- Every open portfolio role gets candidates within one week.
- A quarterly value-add report shows the intros made and what came of them.
| Competency | Weak evidence | Solid evidence | Strong evidence |
|---|---|---|---|
| Founder trust | Talks about founders in general | Names founders who sought them out | Founders describe them as their first call |
| Proactive help | Responds well to requests | Spotted some needs before being asked | Built a routine for catching signals |
| Systems | Did the work personally | Documented a process others followed | Built something that ran without them |
| Data and AI | Uses tools casually | Uses AI daily and checks the output | Can explain where each number came from |
| Partner influence | Waited for direction | Got partners to act now and then | Got senior people to commit to goals |
Write the outcomes so they can become the new hire's goals on day one. That way the scorecard is also the first draft of their role charter, which the first 90 days in a platform role covers in more detail. For how to report against those goals later, see what platform teams should measure.