Team Building Consulting

Building Engineering Teams at Startups

Dipankar Sarkar
Dipankar Sarkar · · 6 min read

I’ve built engineering teams at five startups and advised many more on technical hiring. Here’s what I’ve learned about building teams that ship.

Hiring Philosophy

Hire for Trajectory, Not Just Current Skills

Early-stage startups need people who can grow with the company. Current skills matter, but growth potential matters more.

Look for:

  • Learning velocity: How fast do they pick up new things?
  • Ownership mentality: Do they see problems and fix them without being told?
  • Adaptability: Can they thrive in ambiguity and changing requirements?
  • Curiosity: Do they want to understand how things work?

A strong engineer who can grow into a lead is more valuable than someone who’s plateaued at their current level.

Culture Add, Not Just Culture Fit

“Culture fit” often becomes “people like us,” which limits diversity and thinking.

Instead, identify:

  • Values alignment: Shared beliefs about how work should be done
  • Complementary perspectives: Skills and viewpoints you’re missing
  • Constructive diversity: Different approaches that challenge groupthink

Technical Bar vs. Role Appropriateness

Your first 10 engineers should be exceptional generalists who can do anything. Your next 50 need specialists. Calibrate hiring bar to stage and role.

Early engineers need:

  • Broad technical ability
  • Comfort with ambiguity
  • Ownership of entire systems
  • Speed over perfection

Later engineers need:

  • Deep domain expertise
  • Experience at scale
  • Process discipline
  • Mentorship capability

Hiring Process That Works

Sourcing

Best sources:

  • Referrals from strong engineers (offer meaningful referral bonuses)
  • Technical community involvement
  • Open source contributions as signal
  • Targeted outreach on LinkedIn/Twitter
  • Engineering blogs and conference speakers

Avoid:

  • Over-reliance on recruiters early
  • Job board spray-and-pray
  • Lowering bar for speed
  • Hiring from only one source

Interview Process

Stage 1: Resume screen (30 seconds per resume)

  • Look for evidence of impact
  • Trajectory of growth
  • Relevant experience
  • Red flags (gaps, short tenures without explanation)

Stage 2: Phone screen (30 minutes)

  • Verify basic qualifications
  • Assess communication ability
  • Determine mutual interest
  • Explain role and company

Stage 3: Technical interview (2-4 hours)

  • Practical coding (not puzzle questions)
  • System design appropriate to level
  • Domain-relevant problems
  • Take-home option for schedule flexibility

Stage 4: Team interview (2-3 hours)

  • Cross-functional exposure
  • Values and culture assessment
  • Candidate questions answered
  • Reference to specific team members

Stage 5: Reference checks (2-3 calls)

  • Actually call references
  • Ask specific questions about performance
  • Look for patterns across references
  • Back-channel references when possible

Closing Candidates

Speed matters: Good candidates have options. Move in days, not weeks.

Sell the opportunity: Mission, growth potential, team quality, technical challenges.

Be transparent: Stage, risks, runway. Surprises later damage trust.

Competitive compensation: Equity matters more than salary at early stages. Be generous with equity early.

Team Structure

Early Stage (1-10 engineers)

  • Flat structure, everyone reports to CTO/founder
  • Full-stack generalists preferred
  • No formal process—high bandwidth communication
  • Ship fast, fix forward

What works:

  • Daily standups (quick, async-friendly)
  • Pair programming on hard problems
  • Shared on-call rotation
  • Collective code ownership

Growth Stage (10-30 engineers)

  • Team leads emerge from strong ICs
  • Begin specialization (frontend, backend, infrastructure)
  • Light process (sprint planning, retrospectives)
  • Start investing in tooling and automation

What works:

  • Small teams (5-8 people)
  • Clear ownership areas
  • Weekly team syncs
  • Cross-team communication rituals

Scale Stage (30+ engineers)

  • Engineering managers distinct from tech leads
  • Clear team boundaries and ownership
  • Documented processes and runbooks
  • Platform/infrastructure team separate from product

What works:

  • Manager of managers layer
  • Engineering-wide communication
  • Technical guilds for cross-team coordination
  • Investment in internal tools and processes

Engineering Culture

What to Establish Early

Code review expectations: Everyone’s code gets reviewed. No exceptions for seniority.

Testing philosophy: What requires tests? Unit test critical paths at minimum.

Documentation standards: What gets documented? Architecture decisions, onboarding, runbooks.

On-call culture: How do you handle production issues? Who gets paged?

Shipping cadence: How often do you deploy? Daily, weekly, continuous?

Practices That Scale

Written communication: Decisions in writing, not hallway conversations. Creates institutional memory.

Blameless postmortems: Learn from failures without finger-pointing. Focus on systems, not individuals.

Technical RFCs: Major decisions documented and reviewed before implementation.

Regular 1:1s: Managers meeting with reports weekly. Build relationships and catch issues early.

Career ladders: Clear expectations for each level. Growth paths that don’t require management.

Common Mistakes

Hiring Too Senior Too Early

Staff engineers expect established processes and defined problems. Early stage needs builders who thrive in chaos.

Result: Expensive hires who are frustrated and unproductive.

Better approach: Hire senior-enough people who want to build from scratch.

Not Firing Fast Enough

One wrong hire poisons culture for others. Keeping underperformers damages team morale.

Signs to act on:

  • Consistent underperformance after feedback
  • Cultural toxicity
  • Inability to work with others
  • Lack of improvement over time

Better approach: Clear expectations, direct feedback, reasonable timeline, then decision.

Promoting Top IC to Manager

Management is a different skill. Don’t lose your best engineer to bad management.

Better approach: Management should be opt-in. Provide training. Create IC career tracks. Let people try management and return if it doesn’t fit.

Ignoring Technical Debt

Eventually it stops all forward progress. Budget ongoing maintenance.

Better approach: Allocate 20% of capacity to debt reduction. Track debt explicitly. Pay it down alongside feature work.

Over-Processing Early

Heavy process when you have 5 engineers creates friction without benefit.

Better approach: Add process when pain justifies it. Start minimal and evolve.

Compensation Guidance

Salary

  • Pay market rate (slightly above for exceptional candidates)
  • Use levels and bands early to avoid inequities
  • Be transparent about compensation philosophy
  • Revisit regularly as market changes

Equity

Typical ranges (varies by market and stage):

Early employees (1-10): 0.5% - 2% Growth stage (10-30): 0.1% - 0.5% Scale stage (30+): 0.01% - 0.1%

Considerations:

  • Refresh grants for retention
  • Cliff and vesting schedule
  • Exercise windows
  • Clear explanation of equity value

How I Help With Team Building

My engineering team consulting includes:

Hiring process design: Interview loops, rubrics, closing strategies.

Organizational design: Team structure, roles, reporting relationships.

Leadership development: Coaching first-time managers, leadership training.

Culture assessment: Identifying and addressing team health issues.

Compensation benchmarking: Market-appropriate packages.

If you’re scaling your engineering team and want guidance from someone who’s done it, let’s discuss team building consulting.