Working with founders is its own discipline. Founders are typically high-conviction, high-velocity, and deeply attached to their own ideas. EMs who manage these dynamics well thrive at startups and growing companies; those who do not get filtered out fast. Senior interviews increasingly probe these skills.
The founder personality archetype
Generalizations, but useful:
- Strong product intuition; opinions arrive faster than data
- Comfort with ambiguity and rapid decisions
- Willingness to override process
- High urgency; impatient with slowness
- Personal investment in the company that no employee fully matches
This is not a flaw — it is what makes them founders. The EM’s job is to translate this energy into engineering execution.
The first founder meeting
If you are joining a startup, your first 1:1 with the founder/CEO matters disproportionately. Goals:
- Understand the vision (where is the company going?)
- Understand the constraints (what is the runway, the must-hit?)
- Establish communication norms (how often do they want updates? what format?)
- Surface concerns early (better than ambushing later)
Communication patterns
Most founders prefer:
- Short written updates over long meetings
- Specific asks (decisions, resources, escalations) over open-ended check-ins
- Bad news delivered fast and direct
- Optimism balanced with realism
Avoid:
- Long status updates that bury the lede
- Hedging that obscures what you actually think
- Hiding problems hoping they resolve
The “founder swoop” problem
Founder appears mid-sprint, says “we should rewrite this in Rust” or “stop everything and ship X by Friday.” Engineering plans evaporate.
Strategies:
- Acknowledge the input genuinely — it usually contains a real signal
- Translate the input into a concrete decision: “are you saying we should pause the Q3 plan and ship X? If yes, here is what we defer.”
- Make tradeoffs explicit. Do not pretend you can do everything.
- Get a clear decision in writing before changing direction
Managing up to a CEO
If you report to a CEO (not just a founder), the dynamic is similar but more formal. Patterns:
- Quarterly written strategy memos from you
- Monthly business reviews with metrics
- Quick decisions over Slack for tactical issues
The “do everything yourself” trap
Some founders intervene at the IC level. They review code, redesign features, write the marketing copy. As an EM you may feel undermined.
Counter:
- Recognize the founder’s input as content, not authority — they are an unusually opinionated stakeholder
- Help your team translate input without losing momentum
- Coach the founder where helpful: “for this kind of work, let us iterate with the team and check in at week 2”
When founders are wrong
Sometimes you genuinely disagree with a founder’s technical or product call. Strong patterns:
- Disagree in private, in 1:1, with data
- Frame as a question: “What if we tried Y instead? Here is the tradeoff.”
- Be willing to commit and execute if the founder holds the position
- Reserve “hill to die on” status for genuinely catastrophic calls
The “founder mode” debate
The 2024 essay by Paul Graham argued founders should stay close to the work and override “manager mode” wisdom when needed. The interview-relevant takeaways:
- EMs should expect founder involvement deeper into the org than at non-founder companies
- Skip-level conversations from founder to IC are normal and not undermining
- Your role is to amplify good founder input, filter chaos, and keep execution moving
Surviving multiple founders
Co-founders sometimes disagree publicly. Avoid getting in the middle:
- Don’t take sides
- Push for written decisions when there is conflict
- Surface the conflict to the founders rather than papering over it
Frequently Asked Questions
How do I work with a founder who is technically wrong?
Bring data and named alternatives. Do not become the “no” person. Pick which battles to fight; founder relationships outlast any single decision.
What if the founder is taking too much of my team’s time?
Address it directly: “the team needs uninterrupted execution time. Could we limit your direct conversations to design reviews on Tuesday?” Most founders are reasonable when asked.
How does this differ at a non-founder-led company?
Bigger companies have more process; less founder volatility. The skill of communicating up still matters — same content, more formal channels.