Alex Furman, co-founder of Invitae ($12B peak valuation) and Performica, transitioned from a software engineer to Chief People Officer during Invitae's hypergrowth. This experience taught him invaluable, non-obvious lessons about scaling teams, which he later encoded into his new company, Performica. His journey also includes overcoming 116 investor rejections to fund Invitae, offering a powerful playbook on resilience and storytelling for founders.
Key takeaways
- Treat people operations as an engineering problem with systems, data, and APIs.
- When fundraising, treat every "no" as a data point to refine your pitch and targeting.
- Your biggest operational pains are often your best startup ideas.
- A technical founder can have a massive advantage running HR by applying first-principles thinking.
- Surviving hypergrowth requires building scaffolding: career ladders, comp bands, and communication cadences.
- Master your 30-second story. It’s the key to fundraising, hiring, and motivating your team.
Your Startup Is Breaking, And They Want You—The Engineer—To Fix It
Imagine this: your company is hitting escape velocity. Sales are soaring, the market loves your product, but internally, things are falling apart. Communication is breaking down, frustration is mounting, and the chaos of hypergrowth threatens to grind everything to a halt.
This was the reality for Alex Furman at Invitae, the genetic information company he co-founded. The company was scaling, but the organization itself was buckling. The founders agreed one of them needed to drop everything and build a real People function. Alex, a self-taught software engineer who started his career building automated trading systems, reluctantly raised his hand, assuming it would be a temporary crisis-management gig.
He was wrong. He discovered that building an organization was the ultimate systems-design challenge. The lessons he learned—transforming from a coder into the Chief People Officer of a public company—are a playbook for every founder who thinks of HR as "soft skills."
The Engineer's Playbook For Hypergrowth HR
Most founders see People Ops as a series of necessary evils: payroll, compliance, difficult conversations. Alex came to see it as an engineering problem. Your organization isn't a family; it's a complex, dynamic system that can be analyzed, debugged, and optimized.
The Technical Founder's Unfair Advantage
As a technical founder, you are uniquely equipped to excel at People leadership, even if you don't realize it. You bring three critical skills to the table that traditional HR often lacks:
Systems Thinking: You can see the org chart as an architecture diagram, inter-team communication as a set of APIs, and employee onboarding as a critical user workflow. You can diagnose bottlenecks in the system of work itself. · Data-Driven Approach: Instead of relying on gut feel, you can demand data. This means analyzing compensation against market rates, tracking employee engagement scores, and measuring the effectiveness of your hiring funnel. · First-Principles Thinking: You are more likely to ask "Why do we do it this way?" about established HR dogma. Do we really need a nine-box performance review? What is the actual goal of this policy? This allows you to build a people function that serves your company, not just copies others.
Your First 90 Days as the Accidental Head of People
If you find yourself in Alex’s shoes, don’t panic. Treat it like a new codebase. Here’s a tactical roadmap:
Your first job is to listen and learn. Conduct 30-minute 1:1s with as many people as possible. Your goal isn’t to solve their problems on the spot, but to gather data. Ask targeted questions:
"What is the most frustrating part of your week?" · "What is one thing we should stop doing immediately?" · "Who do you go to when you need help on a different team? How does that work?" · "What’s blocking you from doing your best work?"
You are mapping the "social graph" of the company and identifying the biggest points of friction.
Now you can start building the basic infrastructure every scaling company needs. Don't aim for perfection; aim for "good enough" scaffolding that provides stability.
Career Ladders: For your largest roles (e.g., Software Engineer), define what separates Level 1, 2, and 3. Write it down. This simple act reduces anxiety about career progression and provides a basis for promotions. · Compensation Bands: Research market data for your key roles. Create simple, defensible salary bands for each level. This moves compensation from a negotiation battle to a transparent process. A typical band might be +/- 10% from a midpoint salary. · Communication Cadence: Establish a rhythm. A weekly all-hands with Q&A, a monthly founder email update, and a quarterly business review. Predictable communication is the bedrock of a healthy remote or hybrid culture.
Roll out your first lightweight systems. Don’t try to boil the ocean. Launch a simple performance review cycle focused on peer feedback and manager coaching, not ratings. Introduce your career ladders and comp bands to the team, explaining the "why" behind them. Gather feedback and be prepared to iterate just like you would with a product.
Common Mistake: The "Culture Fit" Trap
Founders often hire for "culture fit," which devolves into hiring people they’d like to have a beer with. This leads to a homogenous and less effective team. Instead, hire for "values fit." Define your company values as a set of observable behaviors (e.g., "bias for action," "disagree and commit") and interview against those criteria. This creates a team that is aligned on how to operate but diverse in thought and background.
Surviving 116 "No"s: The Fundraising Gauntlet
Before Invitae’s hypergrowth, Alex and his co-founders spent a full year on the road fundraising. They were rejected 116 times.
Getting a "no" from an investor is painful. Getting over 100 of them can feel like a death sentence. But the Invitae team’s survival offers a masterclass in resilience.
How to Systematize a Tough Fundraise
When the market isn’t biting, you have to stop "taking meetings" and start running a process.
Build a CRM: Use a spreadsheet or a tool like Affinity to track every investor you talk to. Log the date, the contact, the feedback, and the next step. This is your single source of truth. · Reframe Rejection as Data: Every "no" contains information. After 10-15 meetings, patterns will emerge. Are investors consistently confused about your go-to-market? Do they doubt the market size? This isn’t failure; it’s user feedback on your pitch. · Iterate on the Story: Use that feedback to sharpen your narrative. The article mentions storytelling is key, but what does that mean? It means concisely articulating the future you’re building. Invitae wasn't just "offering cheaper genetic tests." They were "bringing comprehensive genetic information into mainstream medical practice to improve healthcare for billions." · Tier Your Targets: Don't just spray and pray. Group investors into Tier 1 (dream partners), Tier 2 (good fit), and Tier 3 (practice rounds). Warm up with Tier 3 to get feedback, refine your pitch, then go after your top targets.
Your pitch deck is not a comprehensive summary of your business. It is a 15-to-20-slide machine designed to get you the next meeting. Its only job is to tell a compelling story that makes an investor lean in.
From Pain to Product: The Origin of Performica
Alex’s journey from engineer to Chief People Officer revealed a massive gap in the market. He had to diagnose Invitae’s organizational problems using manual surveys, spreadsheets, and countless one-on-one meetings. It was slow, painful, and subjective.
After leaving Invitae, he co-founded Performica to build the tool he wished he’d had. Performica helps companies analyze their internal communication data (from sources like Slack and Google Calendar) to map the "organizational network." It provides objective answers to critical questions:
Are we developing silos between teams? · Who are the true influencers and information hubs in our company? · Which teams are at risk of burnout? · Is our onboarding process actually integrating new hires effectively?
This is the engineering mindset applied to people analytics—turning the invisible patterns of how work gets done into a visible, actionable dashboard.
How to Apply This This Week
You don’t need to become a Chief People Officer overnight to benefit from Alex’s journey. Here are four concrete actions you can take this week.
Map your fundraising feedback. Open a spreadsheet. List the last 10 investors who passed on your company. In the next column, write down the specific reason they gave. What is the pattern? What is the single biggest objection you need to overcome in your next pitch? · Draft a V1 career ladder. Pick one role, like "Software Engineer" or "Account Executive." Write down three bullet points for what a junior person does and three bullet points for what a senior person does. You’ve just created your first career ladder. · Audit your communication cadence. Do you have a weekly all-hands? A monthly business update? Is it consistent and predictable? If not, schedule the next four occurrences right now. · Articulate your story. Can you explain the "inevitable future" your company is creating in 30 seconds? Practice it. This isn’t just for investors; it’s for hiring, motivating your team, and reminding yourself why you’re doing this.
Frequently asked questions
- What are the early signs that hypergrowth is 'breaking' a startup?
- Common signs include communication becoming siloed, decision-making slowing down dramatically, employee frustration rising, and key talent starting to leave. You'll hear things like 'We don't know what other teams are doing' or 'This used to be simple.'
- What's a simple compensation framework for an early-stage startup?
- Define 3-4 job levels (e.g., Junior, Mid-Level, Senior, Lead) for your core roles. Research market-rate salary ranges for each level in your geography. Document these ranges and use them as the basis for all offers to ensure fairness and transparency.
- Why would a technical founder be good at running HR?
- They can view the organization as a complex system. They are comfortable using data to make decisions, can design 'social APIs' for communication, and apply first-principles thinking to challenge outdated HR dogma, focusing on what actually improves performance and morale.
- How can a founder handle dozens of investor rejections without losing motivation?
- Systematize the process. Log every meeting and the reason for the 'no' in a spreadsheet. This reframes rejection as data collection, helping you spot patterns in your pitch or targeting. Celebrate small wins with your team, like getting to a second meeting, to keep morale high.
