1) Recommendation

Promote the internal engineering lead into an “acting VP of Engineering” role now (90–120 days), while simultaneously running a light but real external search for a proven VP Eng.
At the end of the trial window, make a hard decision: confirm the internal leader as permanent VP Eng, or hire the external VP Eng and place the internal leader into a clearly-scoped senior role (e.g., Director of Engineering / Head of Platform / Senior Engineering Manager) with retention incentives.

This “promote-now + validate-in-parallel” approach is usually the best balance when the org context is unclear because it preserves momentum, reduces cultural risk, and still protects you if the company actually needs a scale-experienced VP Eng quickly.

---

2) Rationale (mapped to your evaluation criteria)

1. Team stage

• If you’re early-stage / small-to-mid team (roughly 5–25 engineers): internal promotion tends to work well because the job is often 60% execution + 40% management systems. The fastest way to improve delivery is usually tighter prioritization, better planning rituals, and removing blockers—things an internal lead can do immediately.
• If you’re scaling fast (25–80+ engineers, multiple teams, managers-of-managers emerging): an external VP Eng can add significant leverage if they’ve built org design, career ladders, planning systems, and operating cadence at that scale.
  Because we don’t know your stage, the acting role + parallel search de-risks both possibilities.

2. Cultural fit risk

• External VP Eng: higher cultural fit risk (values mismatch, leadership style mismatch, credibility issues, “big-company playbook” pushed too early). A mis-hire at VP level is expensive and destabilizing.
• Internal promotion: lower culture risk and typically higher trust, but can expose gaps in executive presence, cross-functional influence, and performance management maturity.
  Acting VP lets you test whether the internal leader can operate at the exec level without permanently committing.

3. Ramp time

• Internal: fastest ramp (days to a couple weeks). They already know the codebase, product context, team strengths/weaknesses, and historical decisions.
• External: typically 60–120 days to be meaningfully effective (relationships, architecture context, talent assessment, process changes).
  If you have near-term delivery commitments, customer escalations, funding milestones, or reliability issues, ramp time alone often justifies promoting internally now.

4. Cost

• External VP Eng (US market): high base + bonus + meaningful equity; plus recruiting fees (often 20–30% of first-year cash comp) and opportunity cost if the hire misses.
• Internal promotion: cheaper in cash, may require equity refresh, and you may need to backfill their previous role.
  The acting approach keeps cost controlled while you validate the right long-term shape.

5. What the team needs at this stage

Most teams considering a VP Eng change are feeling one (or more) of these pains:

• Delivery is inconsistent; planning is chaotic; priorities churn.
• Quality/reliability is slipping; incidents are frequent.
• Hiring is slow; onboarding is weak; performance management is avoided.
• Product/Engineering tension; unclear ownership and decision-making.
• Architecture is drifting; too much tech debt; no technical strategy.

Internal acting VP is best if the immediate need is execution stabilization and team coherence.
External VP is best if the immediate need is organizational scaling (multiple teams, managers, hiring machine) and executive-level cross-functional leadership.
Running both paths in parallel is the most practical hedge given missing context.

---

3) Trade-offs (pros and cons)

Promote internal lead (acting VP)

Pros

• Fastest impact; minimal disruption.
• Stronger trust and morale signal (“we grow leaders”).
• Lower cultural risk.
• Better continuity on architecture and delivery.

Cons

• Capability gap risk (org design, exec communication, conflict/performance management).
• May create internal politics if others expected the role.
• If they struggle, it can be awkward to “undo” without a plan.

Hire external VP Eng now

Pros

• Brings pattern recognition from scaling (hiring, leveling, org design, operating cadence).
• Can reset standards and introduce proven systems quickly (if they fit).
• Useful if you need a “change agent” with authority.

Cons

• Slower ramp; may miss near-term goals.
• High cost and high mis-hire blast radius.
• Can unintentionally demotivate current leaders (“ceiling effect”).
• Risk of over-processing or premature structure.

---

4) Implementation (key steps)

Step A — Define the VP Eng outcomes (1–2 weeks)

Write a one-page scorecard with 6-month outcomes, e.g.:

• Delivery: predictable planning cadence; on-time roadmap hit rate improves (define baseline + target).
• Quality: incident rate / MTTR targets; release confidence metrics.
• People: hiring plan; retention; performance review cycle; leveling framework draft.
• Tech: architecture priorities; tech debt burn-down plan; platform/reliability roadmap.
• Cross-functional: product/eng operating model; decision rights; stakeholder satisfaction.

Step B — Appoint the internal lead as Acting VP Eng (immediately)

• Communicate clearly: “acting” for 90–120 days with explicit evaluation criteria.
• Adjust scope: move them from “hero IC” work to leadership work (planning, hiring, coaching, quality).
• Backfill tactical gaps: appoint a tech lead/EM to own day-to-day delivery on the most critical team.

Step C — Add lightweight executive support (optional but high ROI)

• If no experienced CTO/COO exists, consider a fractional VP Eng / advisor 4–8 hrs/week to coach the acting VP on:
  • org design, hiring loops, performance management, exec comms
  • implementing metrics without bureaucracy

Step D — Run a parallel external search (start within 2–3 weeks)

• Don’t do a 6-month “beauty contest.” Time-box it.
• Use the scorecard to screen for:
  • stage match (have they led at your scale?)
  • systems built (career ladder, incident mgmt, planning)
  • references that validate leadership behaviors (not just outcomes)
• Include a practical exercise: “First 90-day plan given this scenario.”

Step E — Decide at day 90–120

Use a structured review:

• Did delivery predictability improve?
• Did the acting VP make (and communicate) hard calls?
• Did hiring/performance management progress?
• Do Product/CEO trust them as an exec peer? Then:
• Confirm internal leader as VP Eng + comp/equity adjustment + backfill plan; or
• Hire external VP Eng and transition internal leader to a defined role with growth path.

---

5) Risks and mitigations

1. Risk: Acting VP fails, causing uncertainty and morale drop

   • Mitigation: time-box the trial, publish the scorecard, provide coaching, and communicate that this is a structured evaluation—not a vague experiment.

2. Risk: Internal promotion creates a “missing layer” (their old job doesn’t get done)

   • Mitigation: explicitly reassign their prior responsibilities; appoint an interim EM/tech lead; reduce WIP; pause non-critical initiatives.

3. Risk: External search undermines the acting VP

   • Mitigation: be transparent: “We are validating the best long-term structure; internal candidate is the front-runner if goals are met.” Avoid secret searches.

4. Risk: External mis-hire at VP level

   • Mitigation: rigorous reference checks (including back-channel), stage-fit validation, and a 30/60/90 plan review with clear success metrics.

5. Risk: Politics/retention issues among other senior engineers

   • Mitigation: communicate why this person was chosen, clarify career paths, and consider retention grants for key leaders during the transition window.

---

6) Alternatives considered (briefly)

1. Hire a Director of Engineering now (instead of VP)

   • Good if you need execution management more than executive leadership; cheaper and easier to hire; may still require a VP later.

2. Split the role: VP Eng (people/ops) + Principal/Chief Architect (technical)

   • Works when the internal lead is a strong architect but not yet a people leader, or vice versa.

3. Keep current structure and add a program management layer (TPM/Delivery Lead)

   • Helps delivery predictability quickly, but doesn’t solve leadership, hiring, and performance management needs.

---

If you answer these 6 questions, I can tighten this into a single-path recommendation (promote vs hire) rather than a hedged approach: current engineer count; number of teams; are there EMs already; next 6-month business milestone; top 2 engineering pain points; and whether the internal lead has managed managers before.

1. Recommendation

Promote the existing internal engineering lead to VP of Engineering.

2. Rationale

This recommendation prioritizes speed, cultural alignment, and cost efficiency in the absence of specified triggers for radical change (e.g., no mention of scaling crises, technical debt overload, or market pivots). It directly addresses the evaluation criteria as follows:

1. Team stage: Without specifics on team size or maturity (e.g., startup vs. scale-up), assume a mid-stage engineering function (10-50 engineers, post-MVP but pre-hypergrowth), common in US tech hubs like Ashburn, VA (near AWS/data centers). An internal promotion ensures continuity during iterative growth, avoiding disruption in delivery pipelines.

2. Cultural fit risk: Internal candidates inherently match the company's values, communication norms, and unwritten rules, reducing alienation risks by 50-70% per SHRM studies on promotions vs. hires. External hires often fail (up to 40% within 18 months, per Gartner) due to fit mismatches.

3. Ramp time: Internal leads ramp in 1-3 months vs. 6-12 months for externals (Heidrick & Struggles data), as they already know the stack, roadmap, team dynamics, and pain points—no learning curve on tribal knowledge.

4. Cost: Promotion costs ~$50K-$150K (backfilled lead role + bonus), vs. $300K-$600K+ for external (recruiter fees 20-30% of $250K-$400K salary, signing bonus, relocation). Savings fund team tools/training.

5. What the team needs at this stage: Stability, retention, and execution focus—internal leaders boost morale (20-30% lower turnover, Gallup) and align leadership with current realities, enabling quick wins like process tweaks over wholesale overhauls.

This choice aligns with best practices from companies like Basecamp (internal promotions for engineering leads) and avoids the "hire fast, fire faster" trap seen in 60% of VP hires (Korn Ferry).

3. Trade-offs

Pros:

• Immediate impact: No hiring delays (2-6 months typical for VP roles via LinkedIn/VC networks).
• High retention: Team loyalty surges; internals are 2x more likely to stay 3+ years (LinkedIn data).
• Cost-effective scaling: Frees budget for hires/tools amid uncertain funding.

Cons:

• Limited fresh perspective: Risks "incumbent bias" (stuck in old habits, e.g., legacy architecture).
• Skill gaps: May lack enterprise experience (e.g., multi-cloud migrations) if team is maturing.
• Opportunity cost: Delays external expertise for pivots (e.g., AI/ML shifts).

External hire pros/cons flipped: Brings innovation/networks but at higher cost/disruption.

4. Implementation

1. Assess & Announce (Week 1): Conduct 360° feedback on the lead (via anonymous surveys/tools like Culture Amp, 5-7 interviews). CEO/C-suite approves; announce internally with town hall.
2. Formalize Role (Weeks 1-2): Update org chart (e.g., via Lucidchart), contract (10-15% salary bump + equity vest), backfill lead role (internal shuffle or $150K hire via Indeed/AngelList).
3. Onboard & Empower (Weeks 3-4): 30-60-90 day plan (e.g., audit tech debt via SonarQube, set OKRs in Lattice). Pair with executive coach ($10K/6 months via BetterUp).
4. Monitor Progress (Ongoing): Quarterly KPIs (e.g., velocity +20%, churn <10%) via OKR tools; external advisor check-ins (e.g., fractional CTO 4 hrs/week).
5. Budget: $100K total (comp adjustment $75K, coach/tools $25K); track via QuickBooks.

5. Risks

• Risk: Promotion breeds complacency/internal politics (20% chance; leads to stagnation). Mitigation: Mandate 90-day external benchmark (e.g., Gartner peer analysis); rotate deputies for diverse input.
• Risk: Skill shortfall halts growth (e.g., no SRE expertise). Mitigation: Hire 1-2 specialists ($200K each) as direct reports; upskill via Pluralsight/Udacity ($5K/engineer).
• Risk: Team resentment if seen as "default" choice (morale dip). Mitigation: Transparent process (share feedback summary); incentives like team bonus pool.
• Risk: Misses external talent wave (tight VP market). Mitigation: Keep recruiter warm (e.g., Betts Recruiting, $30K retainer) for future hires. Uncertainties: If undisclosed crises (e.g., delayed funding), reassess in 30 days.

6. Alternatives

• Hybrid: Promote internal as interim VP (6 months), hire external later—balances speed but dilutes focus.
• External hire now: For transformation needs (e.g., post-Series B scale)—higher reward but 2x risk/cost.
• Delay decision: Status quo with fractional VP (e.g., Toptal, $20K/month)—viable short-term but erodes momentum.

VP of Engineering: Hire Externally or Promote Internally?

1. Recommendation

Default to promoting your internal engineering lead — unless you can identify a specific, critical capability gap that no one on your current team can grow into within 3–6 months.

This is a conditional recommendation because the right answer genuinely depends on factors you haven't specified. But in the absence of a clear, urgent reason to go external (e.g., you're scaling from 10 to 80 engineers in the next year, entering a heavily regulated domain, or recovering from a serious engineering crisis), the internal promotion carries less risk, costs less, and preserves more organizational value.

Below, I'll walk through the detailed reasoning across your five evaluation criteria, then lay out how to execute either path well.

---

2. Rationale (Evaluated Across Your Five Criteria)

Criterion 1: Team Stage

This is the single most important variable, and you haven't specified it — so let me give you a decision tree:

Team Stage	Likely Best Path	Why
Early stage (3–12 engineers)	Internal promotion	You need a player-coach who knows the codebase and the people. An external VP will be over-titled and under-utilized, or will try to impose premature process.
Growth stage (12–40 engineers)	It depends — see capability gap analysis below	This is the inflection point where you're introducing team structure, delivery processes, and hiring systems for the first time. If your internal lead has never built these, an external hire with that specific experience is justified.
Scale stage (40–100+ engineers)	Lean external	At this point you need someone who has operated at the next level of complexity — multi-team coordination, engineering budgeting, cross-functional executive partnership. Few first-time VPEs succeed here without prior experience.

My default assumes you're early-to-mid growth stage, which is the most common scenario for this question. At that stage, the internal lead usually knows more about what actually needs to happen than an outsider would for the first 6 months.

Criterion 2: Cultural Fit Risk

External hire: HIGH risk. Internal promotion: LOW risk.

This is not a soft concern — it's an operational one. A VP of Engineering sets the norms for how engineers work: how decisions get made, how code gets reviewed, how incidents get handled, how people get promoted. A cultural misfit at this level doesn't just cause discomfort; it causes attrition.

Specific risks with an external hire:

• Process shock: They import processes from their last company (e.g., SAFe, rigid sprint ceremonies, heavy JIRA workflows) that don't match your team's working style
• Trust deficit: Engineers don't grant authority to someone who hasn't earned it by shipping alongside them. The new VP starts with zero credibility and must build it while simultaneously making high-stakes decisions
• Values misalignment: Their definition of "engineering excellence" may differ from yours (e.g., they prioritize velocity over quality, or vice versa), and this only surfaces 60–90 days in
• Departure cascade: If your internal lead was expecting the role and doesn't get it, there's a meaningful probability (I'd estimate 40–60%) they leave within 6 months, and they may take 1–3 engineers with them

An internal promotion carries almost none of these risks. The person already embodies the culture because they helped create it.

Criterion 3: Ramp Time

Dimension	External Hire	Internal Promotion
Understanding the codebase and architecture	2–4 months	Already there
Understanding team dynamics and individual strengths	2–3 months	Already there
Understanding the product and customer context	1–3 months	Mostly there
Building trust with the team	3–6 months	Already there
Learning VP-level responsibilities (budgeting, exec communication, cross-functional leadership)	Already there (if hired well)	3–6 months
Net time to full effectiveness	4–6 months	2–4 months

The key insight: an external hire ramps on things that are hard to teach (context, trust, relationships), while an internal promotion ramps on things that are easier to teach (management frameworks, executive communication, budgeting). You can coach someone on how to run a quarterly planning process. You cannot coach someone into having 18 months of context about why the authentication service is architecturally fragile.

Criterion 4: Cost

External hire is significantly more expensive across every dimension.

Direct compensation (US market, 2024–2025 benchmarks):

• External VP of Engineering: $280K–$400K+ total comp (base + equity + bonus), depending on company stage, location, and candidate caliber. In the Northern Virginia / DC metro area, expect the higher end if competing with government contracting firms, AWS, and other tech employers
• Internal promotion: Typically a 15–30% increase from their current senior/staff/lead compensation, landing in the $200K–$300K range

Recruiting costs:

• External: Executive recruiter fees run 20–30% of first-year base salary. For a $250K base, that's $50K–$75K. Timeline: 3–5 months for a quality search
• Internal: $0 in recruiting fees. Timeline: 1–2 weeks for the decision

Hidden costs of external hire:

• Productivity loss during the 4–6 month ramp period
• Risk of a mis-hire (industry data suggests ~40% of external executive hires fail within 18 months), which means restarting the process and absorbing 6–12 months of lost momentum
• Potential severance if it doesn't work out ($50K–$150K+)

Hidden costs of internal promotion:

• Investment in coaching/mentorship ($15K–$30K/year for an executive coach)
• The promoted lead's IC or technical contributions decrease — you may need to backfill their previous role
• If they struggle, the performance conversation is harder because of the existing relationship

Net cost difference: An external hire is typically 2–3x more expensive in year one when you account for all costs.

Criterion 5: What the Team Needs at This Stage

Again, without knowing your specific situation, here's a framework for diagnosing what your team actually needs:

Signs you need an INTERNAL promotion:

• The team is functioning well but needs a formal leader to represent engineering at the executive level
• The primary challenges are execution and delivery, not organizational design
• Morale is good and you want to preserve it
• Your internal lead already informally does VP-level work (prioritization, hiring, cross-team coordination)
• The team is small enough that the VP needs to remain hands-on technically

Signs you need an EXTERNAL hire:

• You're about to scale headcount by 2x or more in the next 12 months and no one on the team has done that before
• You have systemic engineering problems (reliability, technical debt, delivery predictability) that the current team hasn't been able to solve
• You need to establish engineering processes and structure that don't exist today
• You're entering a new domain that requires specific expertise (e.g., compliance-heavy infrastructure, ML/AI platform, real-time systems)
• Your internal candidates have been assessed and genuinely lack the aptitude (not just the experience) for the role

---

3. Trade-offs Summary

Factor	Internal Promotion	External Hire
Cultural continuity	✅ Strong	⚠️ Risk
Team morale & retention	✅ Positive signal	⚠️ Can cause departures
Ramp time	✅ 2–4 months	⚠️ 4–6 months
Cost (year 1, all-in)	✅ Lower	❌ 2–3x higher
New perspectives & frameworks	⚠️ Limited	✅ Strong
Scaling experience	⚠️ May lack it	✅ Can hire for it
Network for recruiting	⚠️ Smaller	✅ Broader
Risk of failure	✅ Lower (~20%)	❌ Higher (~40%)
Ceiling / growth potential	⚠️ Unknown	✅ Proven (if hired well)

---

4. Implementation

Path A: Internal Promotion (Recommended Default)

Week 1–2: Assess and Decide

1. Have an honest conversation with your internal lead about the role. Ask them: Do you want this? What parts excite you? What parts concern you?
2. Evaluate them against the specific VP-level responsibilities you need filled (not a generic job description — your actual needs for the next 12–18 months)
3. Get input from 2–3 people who work closely with them (peers, direct reports) — not a formal 360, just candid conversations

Week 2–3: Structure the Transition 4. Define the role clearly in writing: scope, decision rights, reporting relationships, expectations for the first 90 days 5. Set compensation. Benchmark against market data (Levels.fyi, Glassdoor, Pave, Option Impact). Don't underpay — if you're promoting someone, pay them the role rate, not their current rate plus a token bump 6. Identify the gap areas (likely: executive communication, budgeting, organizational design, hiring at scale) and build a development plan

Month 1–3: Support the Transition 7. Hire an executive coach. Budget $2K–$3K/month. This is the single highest-ROI investment you can make. Look for someone who has coached first-time VPEs specifically 8. Pair them with a mentor — ideally a VP or CTO at another company who's 2–3 years ahead. Your investors or board members can often make introductions 9. Give them explicit air cover: announce the promotion clearly, give them real authority, and publicly back their decisions during the transition period 10. Have weekly 1:1s focused on the leadership transition, not just status updates. Ask: What's harder than you expected? Where do you feel unsupported?

Month 3–6: Evaluate and Adjust 11. At 90 days, do a structured check-in against the expectations you set. Be honest about what's working and what isn't 12. Backfill their previous technical leadership role if needed 13. If it's clearly not working by month 4–5, have the conversation early — don't let it drag to month 12

Path B: External Hire (If Justified)

Month 1: Define Before You Search

1. Write a detailed role scorecard (not a job description). Specify: the 3–5 outcomes this person must deliver in their first year, the specific experience that's non-negotiable, and the cultural attributes that matter
2. Be brutally honest about what you're actually hiring for. "VP of Engineering" means very different things at different companies. Are you hiring a people manager? A technical architect? A process builder? A recruiter-in-chief?

Month 1–2: Source Strategically 3. Use a specialized executive recruiter if budget allows. For VP-level engineering roles, firms like Riviera Partners, Daversa Partners, or True Search have strong networks. Expect to pay $60K–$100K 4. Simultaneously work your own network. The best candidates are often not actively looking 5. Talk to your internal lead before you start the search. Be transparent. Explain why you're going external and what role you see for them. Offer them a meaningful growth path (e.g., Senior Director, Principal Engineer, or a clear timeline to VP)

Month 2–4: Evaluate Rigorously 6. Interview process should include:

• A deep technical architecture discussion (can they go deep, or just talk process?)
• A real-world scenario: give them a sanitized version of an actual challenge you're facing and ask how they'd approach it
• Team interaction: have 2–3 engineers interview them, and weight their feedback heavily
• Reference checks: talk to at least 2 people who reported to them and 1 peer. Ask specifically: What was it like when things went wrong?

7. Red flags to watch for: name-dropping, process-first thinking ("at my last company we did X"), inability to articulate technical trade-offs, lack of curiosity about your specific context

Month 4–5: Onboard Intentionally 8. Structured 90-day onboarding plan. First 30 days: listen, learn, build relationships. No major changes. Days 30–60: identify and propose changes. Days 60–90: begin implementing with team buy-in 9. Assign an internal "onboarding partner" — ideally your internal engineering lead — to provide context and introductions 10. Set explicit expectations with the rest of the executive team about the ramp period

---

5. Risks and Mitigations

If You Promote Internally

Risk	Likelihood	Impact	Mitigation
They plateau — can lead a team of 10 but not 30	Medium	High	Executive coaching, clear milestones, honest 90-day reviews
They struggle with executive-level communication	Medium	Medium	Coach them specifically on this; have them shadow exec meetings before the transition
They lose the respect of peers who are now direct reports	Low-Medium	High	Clear announcement, explicit authority delegation, and you publicly defer to their decisions
They burn out trying to do their old job AND the new one	High	High	Backfill their previous role immediately; explicitly tell them to stop doing IC work
The team outgrows them in 18–24 months	Medium	Medium	This is okay. Plan for it. A successful 18-month stint as VP buys you time and preserves culture during a critical period

If You Hire Externally

Risk	Likelihood	Impact	Mitigation
Cultural misfit	Medium-High	Very High	Rigorous cultural interview, team involvement in hiring, structured onboarding
Internal lead leaves	Medium-High	High	Have the conversation early, offer a compelling alternative path, consider a retention package
Mis-hire (doesn't work out within 12 months)	Medium (~40%)	Very High	Strong reference checks, 90-day evaluation checkpoints, don't ignore early warning signs
They impose processes that slow the team down	Medium	Medium	Explicitly set the expectation: "Listen for 30 days before changing anything"
Search takes too long, creating a leadership vacuum	Medium	Medium	Appoint an interim internal lead during the search; set a hard deadline on the search (4 months)

---

6. Alternatives Considered

1. Fractional / Part-time VP of Engineering: Hire an experienced engineering leader for 2–3 days/week to mentor your internal lead while they grow into the role. Cost: $8K–$15K/month. This is an excellent hybrid option if your internal lead has high potential but needs guidance. Companies like Fractional Jobs or your investor network can source these.

2. Promote internally now, hire externally in 12–18 months: Use the internal promotion as a bridge. Let them stabilize the team and build processes. When you hit the next scaling inflection point, bring in a more senior external leader and transition the internal person to a Senior Director or Principal Engineer role. This is the most common successful pattern I've seen in practice.

3. Hire a VP of Engineering AND keep the internal lead in a co-leadership model: Risky. Dual-leadership structures in engineering almost always create confusion about decision rights. I'd avoid this unless you're splitting clearly along functional lines (e.g., VP of Engineering for delivery/people, CTO/Principal for architecture/technical direction).

4. Hire a strong Engineering Manager layer instead: Sometimes the real need isn't a VP — it's middle management. If your internal lead is effective as a technical leader but overwhelmed by people management across multiple teams, hiring 2–3 Engineering Managers underneath them may solve the actual problem at lower cost and lower risk.

---

Final Word

The question "hire or promote?" is often a proxy for a deeper question: "Do we believe our current team can take us to the next level?" If the answer is yes — even with support and coaching — promote. If the answer is honestly no, hire externally, but do it with eyes open about the cost and risk.

The most expensive mistake isn't choosing the wrong path. It's choosing the external path out of insecurity about your internal talent, losing that talent as a result, and then discovering the external hire doesn't work out either. That sequence — which is distressingly common — sets an engineering organization back 12–18 months.

If you can share more about your team size, stage, and the specific challenges driving this decision, I can sharpen this recommendation significantly.

Based on the constraints provided and standard industry trajectories for engineering organizations, here is a detailed consultation on how to proceed.

1. Recommendation

Conduct a "Scale vs. Context" Gap Analysis, then proceed with a split-strategy.

Because the context is unspecified, a binary answer is dangerous. However, based on best practices for high-growth US technology companies, my recommendation is:

• Hire an External VP of Engineering IF: Your organization is approaching an inflection point of "hyper-growth" (e.g., doubling the team size in the next 12 months, moving from Series A to B, or needing to implement formal management layers). The skillset required to build the machine that builds the product (Org Design) is fundamentally different from building the product itself.
• Promote the Internal Lead (with a "Head of Engineering" title) IF: Your immediate focus is delivery velocity, stabilizing the current stack, or if the team size is under 15–20 engineers.

The "Hybrid" Recommendation (Safest Path): If you are unsure, promote the internal lead to "Director/Head of Engineering" immediately with a specific mandate to stabilize delivery, while acknowledging that a VP search may occur in 12–18 months. This tests their ceiling without the risk of a high-stakes external executive hire failing.

---

2. Rationale

Here is how the decision maps against your specific evaluation criteria:

A. Team Stage

• Early/Seed (<10 Engineers): Promote Internal. You cannot afford a non-coding executive. You need a "Player-Coach." An external VP will likely be bored and too expensive.
• Growth (15–50 Engineers): Hire External. This is the "Valley of Death" for engineering management. Processes break. You need someone who has seen this movie before to implement career ladders, performance reviews, and recruitment pipelines.
• Scale (50+ Engineers): Hire External. At this stage, the role is financial, strategic, and political. An internal lead rarely has the experience to manage budgets, board expectations, and cross-departmental politics effectively.

B. Cultural Fit Risk

• External Hire: High Risk. This is the "Organ Rejection" factor. A new VP bringing "Big Corp" processes to a scrappy team can destroy morale and cause attrition.
• Internal Promotion: Low Risk. The team already trusts this person. They embody the current culture. However, there is a distinct risk that they cannot make "hard decisions" (firing, restructuring) regarding their former peers/friends.

C. Ramp Time

• External Hire: Slow Context, Fast Execution. They will take 3–6 months to understand your technical debt, domain, and legacy code. However, they will be immediate experts on how to run an engineering org (hiring, 1:1s, agile processes).
• Internal Promotion: Fast Context, Slow Execution. They know the codebase and the business logic on Day 1. However, they will likely struggle with the "VP" aspect: strategic planning, conflict resolution, and letting go of coding. You will need to budget time for them to learn leadership skills.

D. Cost

• External Hire: High. A VP of Engineering in the US market (especially East Coast/Tech hubs) commands a high salary ($250k–$400k+ base + equity) plus recruiting fees (20–30% of first-year salary).
• Internal Promotion: Medium/Low. Likely a salary bump, but usually lower than market rate for an external VP.
• Hidden Cost: The hidden cost of the internal promotion is the loss of an individual contributor. If this lead is your best coder, your velocity will drop when they stop coding to manage.

E. What the Team Needs at This Stage

• If the team needs Process/Scaling: Hire External. If the team is chaotic, burning out, or hiring too slowly, you need a professional manager.
• If the team needs Technical Direction: Promote Internal. If the issues are architectural, related to product-market fit, or technical debt, the internal lead is better equipped to solve them.

---

3. Trade-offs

Feature	Hire External VP	Promote Internal Lead
Pros	• Brings a "Playbook" of established processes.<br>• Unbiased view of team performance.<br>• Existing network to recruit talent.<br>• Frees up internal lead to focus on architecture.	• Immediate trust and morale boost.<br>• Deep domain/codebase knowledge.<br>• Retains institutional memory.<br>• Significantly cheaper/faster to implement.
Cons	• High risk of culture clash.<br>• Long recruiting cycle (3–6 months).<br>• Expensive (Salary + Equity + Recruiting fees).	• "Peter Principle" risk (promoted to incompetence).<br>• Difficulty managing former peers.<br>• Loss of your best individual contributor.<br>• Likely lacks experience in org design.

---

4. Implementation

Scenario A: Promoting Internally

1. Backfill Immediately: You must hire a Senior Engineer to take over the lead's coding responsibilities before the promotion takes full effect.
2. Change the Title: Use "Head of Engineering" or "Director of Engineering" rather than VP. This leaves room for a future VP hire above them if they hit a ceiling, without requiring a demotion.
3. Support Structure: Hire an executive coach or mentor for them. Do not assume being a good coder makes them a good executive.
4. Define Success: Explicitly state that their job is no longer writing code, but unblocking others.

Scenario B: Hiring Externally

1. Involve the Internal Lead: The internal lead must be part of the interview loop. If they veto the candidate, do not hire. You need their buy-in to prevent sabotage.
2. Define the Profile: Are you looking for a "Recruiter-in-Chief," a "Technical visionary," or an "Operational expert"? You rarely get all three.
3. The First 90 Days: Mandate a "listening tour." Prevent the new VP from making drastic changes in the first 60 days until they understand why things are the way they are.

---

5. Risks & Mitigation

• Risk: The Internal Lead quits if you hire externally.
  • Mitigation: Create a specialized "Principal Engineer" or "Chief Architect" track. Show them that they can advance in career and compensation without managing people. Make them a partner to the new VP.
• Risk: The Internal Lead fails as VP.
  • Mitigation: Set a 6-month review period. Be honest that this is a trial of a new role. If it fails, have a path for them to return to a technical role without shame.
• Risk: The External VP destroys culture.
  • Mitigation: Heavy vetting for "EQ" (Emotional Intelligence) over "IQ". Reference check specifically for how they handled their previous team's existing culture.

---

6. Alternatives

• Fractional VP of Engineering: Hire a consultant part-time (10–15 hours/week) to set up processes, strategy, and mentoring for the internal lead. This bridges the gap without a full executive salary.
• Split Roles: Promote the Internal Lead to CTO (focused on technology, architecture, and vision) and hire a Director of Engineering/VP of Operations (focused on people management, hiring, and delivery) to report to them or alongside them. This plays to the internal lead's strengths while outsourcing the management burden.