Solutions Engineering Hire & SE Function

⬅️ Back to Day 4: Convert

If you're a B2B SaaS at $5M+ ARR with technical or complex products and selling to mid-market or enterprise, you'll feel the pull for Solutions Engineering (SE / Sales Engineer / Sales Engineering / Pre-Sales Engineering). The naive approach: AEs do their own demos and POCs; quality varies; technical depth missing. The structured approach: hire SEs (technical pre-sales) who pair with AEs to drive technical wins — discovery + custom demos + POCs + technical objection handling + sales-engineering-CS handoff. SEs are the highest-leverage hire in technical sales orgs; great SEs accelerate deals 30-50% and lift win rates 20-40%. Done well, scales technical credibility; done poorly, wastes a senior hire on demo-running.

What Done Looks Like

A working SE function:

1. Decide if you need SE

Stage matters; not everyone needs SE early.

Decide SE readiness.

Right time signals:
- $5-10M ARR with sales-led GTM
- Product complexity (technical buyer / integration / customization)
- Deals $25K+ ACV
- AEs spending >40% time on technical work
- POCs / pilots required
- Customer integration questions

Wrong time signals:
- <$3M ARR (too early)
- Simple self-serve product
- Pure SMB (low ACV)
- AEs aren't technically stretched

Alternatives:

CTO / founder doing technical pre-sales:
- Until $5M ARR
- Doesn't scale beyond founder time

Technical AE:
- Hire AE with technical background
- Less specialization
- For simpler products

Customer engineer (post-sales):
- Different role (post-close)
- Some companies blur

SE/CS hybrid:
- Smaller orgs combine
- Until scale separates

For [COMPANY], output:
1. SE readiness
2. Alternative paths
3. Timing
4. First-year priorities
5. Profile match

The "AEs spending 40%+ on technical work" trigger: AEs aren't trained technical specialists. SE specializes; AE focuses on relationship + closing. Both more productive.

2. Define SE role — vs AE

Role split clarity prevents conflict.

Define SE vs AE roles.

AE owns:

Relationship + closing:
- Account ownership
- Discovery (business pain)
- Pricing + negotiation
- Decision-maker engagement
- Closing the deal
- Quota carry

SE owns:

Technical:
- Technical discovery
- Custom demos (not generic)
- POC / pilot design + execution
- Technical objection handling
- Architecture conversations
- Integration planning
- Technical RFPs

Joint:

Discovery:
- AE: business pain + budget + timeline
- SE: technical pain + integration constraints + architecture

Demo:
- AE: agenda + business value framing
- SE: technical execution + Q&A

Proposal:
- AE: commercial terms
- SE: technical scope of work

Coverage ratio:

AE:SE ratio typically 3:1 to 4:1
- 3 AEs per SE (heavy technical product)
- 4 AEs per SE (lighter technical)
- 2 AEs per SE (very technical, e.g., infrastructure)

Quota:

AE: revenue quota
SE: support multiple AEs; team-level quota OR no quota
- Some companies: team revenue with SE bonus
- Most: SE on base + variable tied to deal close (lighter than AE)

Anti-patterns:

SE doing AE's job:
- Demo without context; AE missing
- AE delegates everything technical

AE undermines SE:
- Goes around SE; promises product features
- SE caught fixing

Vague handoff:
- Who calls customer this week?
- Joint planning needed

Output:
1. Role split document
2. Joint activities (discovery / demo / proposal)
3. AE:SE ratio
4. Quota / comp design
5. Conflict resolution

The "joint discovery" rule: AE + SE both attend first-call. AE leads business; SE leads technical. Sets pattern for partnership.

3. Pick the right SE profile

Different products need different SEs.

SE profile by product.

Infrastructure / dev tools (e.g., Snowflake, Datadog):

Profile:
- 5-10 years technical experience
- Coding background; current
- Customer-facing skills
- Deep architecture knowledge

Comp:
- $130-180K base + variable
- Total: $200-300K

SaaS application (e.g., Notion, Asana):

Profile:
- 3-7 years experience
- Less coding; more workflow design
- Strong demo storytelling
- Customer empathy

Comp:
- $110-160K base + variable
- Total: $150-250K

AI / ML product (e.g., Anthropic, OpenAI):

Profile:
- 5-10 years; AI/ML background
- ML engineer or applied scientist
- LLM eval understanding
- Workshop / education skill

Comp:
- $150-220K base + variable
- Total: $250-400K

Enterprise complex (e.g., Salesforce CPQ):

Profile:
- 7-15 years experience
- Multi-product expertise
- Architecture-level
- Big-deal experience

Comp:
- $180-250K base + variable
- Total: $300-500K

Junior SE (entry-level):

Profile:
- 1-3 years experience
- Strong potential
- Smaller deals; ramp

Comp:
- $80-120K base + variable
- Total: $120-180K

Hiring sources:

Lateral SE:
- Other SaaS SE roles
- Most common

From engineering:
- Customer-facing developer
- Technical depth + new sales skills
- Strong if right person

From customer success:
- Already customer-facing
- Less technical typically

Anti-patterns:

Hire too senior:
- Overqualified; bored
- Or: too expensive for stage

Hire pure engineer:
- No customer-facing skills
- Steep learning curve

Hire pure salesperson:
- Lacks technical depth
- AEs already there

Output:
1. Profile by product type
2. Compensation by profile
3. Hiring sources
4. Interview rigor
5. Cultural fit

The "engineer-curious vs sales-curious" balance: best SEs love technology AND love customer interaction. Pure engineers find it draining; pure salespeople lack depth.

4. Compensation design

SE comp differs from AE.

SE compensation.

Components:

Base:
- 60-70% of total comp
- More than AE (AE 50% base typical)

Variable:
- 30-40% of total
- Tied to: deal closes (with AE) + team performance + individual contributions

Quota mechanics:

No individual quota (most common):
- Pool quota across AEs they support
- Bonus on team performance

Individual quota:
- Less common
- For revenue-attached SEs (rare)

Variable structure:

MBO (Management By Objectives):
- 40-60% of variable
- Quarterly objectives
- Examples: launch new SE collateral, win rate improvement

Deal close bonus:
- 40-60% of variable
- Per-deal or accelerator
- Based on deals SE supported

Stretch:
- 10-20% on team-level overperformance

Equity:

Same as AE / similar roles:
- Vest 4-year; 1-year cliff
- Refresh grants every 2-3 years

Total comp ranges (2026):

Junior SE: $120-180K total
Mid SE: $180-280K total
Senior SE: $280-400K total
Staff / Principal SE: $400-600K total
SE Director / VP: $400-700K + equity

Promotion path:

Senior SE:
- Run multiple complex deals
- Mentor junior

Staff SE:
- Strategic deals (Fortune 500)
- Architecture leadership
- Industry expertise

Principal SE:
- Industry-renown
- Strategic accounts
- Speaking + thought leadership

Director / VP SE:
- Manage SE team
- Org design + hiring
- Cross-functional with sales / product

Output:
1. Comp structure for SE
2. Variable design
3. Quota or no quota
4. Promotion path
5. Career framework

The "SE quota carrying" debate: minority of companies put quota on SE; most prefer team-based incentive. Either works; pick + commit.

5. SE recruiting + interview

Hiring SE is different from AE.

SE interview loop.

Stages:

Stage 1: Recruiter screen (30 min)
- Background; comp expectations

Stage 2: Hiring manager (Sales VP / SE Manager) (60 min)
- Mutual fit; product orientation
- Sales culture

Stage 3: Technical screen (60 min)
- Demo of past work
- Architecture discussion
- Technical depth

Stage 4: Mock demo (90 min, sometimes 2 hours)
- Given product info; prepare 30-min demo
- Present to panel (acting as customer)
- Q&A; technical objections
- Most-important interview

Stage 5: Cross-functional (60 min)
- AE: partnership style
- Engineering: product collaboration
- Customer success: handoff style

Stage 6: Customer-facing (60 min)
- Existing customer joins
- Real-product question
- See if SE handles real complexity

Stage 7: Final + offer

Mock demo evaluation:

Technical depth:
- Did they understand?
- Can they answer questions?

Storytelling:
- Compelling narrative?
- Or: feature-list reading?

Customer-readness:
- Comfort under pressure
- Adapt to questions

Energy / passion:
- Excited about product?
- Or: going through motions?

Slack / discomfort:
- Stay calm with hard objection?
- Or: defensive?

Reference + backchannel:

Technical references:
- Past SE colleagues
- Engineers who worked with

AE references:
- Did they help close deals?
- Easy to work with?

Backchannel:
- Common contacts
- Honest signals

Output:
1. Interview stages
2. Mock demo evaluation
3. Reference patterns
4. Decision criteria
5. Compensation negotiation

The mock-demo interview: best signal for SE quality. 90 minutes well-spent; predicts on-the-job performance.

6. Onboard SE — first 60 days

SE ramp is slower than AE; technical depth required.

SE onboarding.

Week 1: Product immersion

Goals:
- Understand product end-to-end
- Set up demo environment
- Meet team (AE / Engineering / CS)

Activities:
- Architecture deep-dive with engineering
- Product walkthrough
- Customer call shadow

Week 2-3: Demo development

Goals:
- Build personal demo setup
- Run mock demos
- Receive feedback

Activities:
- Customize sandbox
- Practice with team
- Record self-demos for review

Week 4: Live customer engagement

Goals:
- First live demo (with senior SE backup)
- Discovery call participation
- Begin owning small deals

Activities:
- Pair with senior SE on calls
- Lead 30-min portion
- Debrief after

Week 5-8: Independent ramp

Goals:
- Lead demos solo (with AE present)
- Run technical discovery
- Begin owning POCs

Activities:
- Pair-of-deals self-led
- Senior reviews
- Quarterly review at end

Week 9-12: Full ramp

Goals:
- Full responsibility for AE pairings
- Drive technical wins
- Contribute to playbook

Productivity expectations:

Month 1: shadow + learn
Month 2-3: pair + grow
Month 4-6: own deals (with support)
Month 7-12: full productivity

Anti-patterns:

Drop into customer calls week 1:
- Can't add value yet
- Embarrassing for SE; wastes customer time

No mentor / pairing:
- SE flounders alone
- Slow ramp

No structured curriculum:
- Random learning
- Gaps in knowledge

Output:
1. Onboarding plan
2. Pairing model
3. Demo development
4. Productivity expectations
5. Mentor assignment

The "month 1: shadow" rule: senior SE explains what they're doing; junior SE watches. By month 2-3, junior runs portions. Faster than learn-by-failure.

7. Demo + POC playbook

Demos are SE's bread and butter.

Demo + POC playbook.

Demo types:

Standard demo:
- 30-60 min
- Common use case
- 80% reusable; 20% customer-specific

Custom demo:
- 60-90 min
- Customer's data / use case
- Significant prep time

Proof-of-concept (POC):
- 1-4 weeks
- Customer evaluates in their environment
- Higher commitment; higher conversion

Free trial (self-serve):
- Customer drives
- Less SE involvement
- For simpler products

Demo flow:

Opening (5 min):
- "What we'll cover"
- Confirm goals from discovery

Demo (20-40 min):
- Story-driven (not feature tour)
- Map to customer pain
- Specific examples / data

Q&A (10-20 min):
- Open floor
- SE answers technical
- AE handles commercial

Close (5 min):
- Recap value
- Next steps
- Schedule follow-up

Demo principles:

Story > features:
- "Their team did X with this; saved Y"
- Not: "click here, button there"

Customer's data:
- Use their company name in examples
- Connect to their use case
- Pre-load their integration if possible

Show, don't read:
- Live demo (with backup if breaks)
- Don't read slides

Pause for questions:
- Every 5-10 min
- Engagement check

POC structure:

Pre-POC:
- Define success criteria (joint)
- Timeline (1-4 weeks)
- Scope (which features)

Mid-POC check:
- Weekly call
- Address questions
- Course-correct

POC close:
- Final review
- Did we hit criteria?
- Next step (close)

Anti-patterns:

Feature-tour demo:
- 40 features in 30 min
- Customer overwhelmed; remembers nothing

Demo without discovery:
- Generic; misses pain
- Conversion lower

Open-ended POC:
- No success criteria
- Drags on; nobody decides

Output:
1. Demo flow template
2. Customization checklist
3. POC structure
4. Success criteria framework
5. Common pitfalls

The "story-driven demo" win: demos that tell a story (problem → solution → outcome) close 30%+ better than feature tours.

8. SE-Engineering relationship

SE bridges sales + engineering.

SE-Engineering partnership.

SE's role with engineering:

Customer feedback channel:
- "Customers asking for X" → product team
- Prioritization signals

Roadmap input:
- Sales-side perspective
- Customer pain → feature requests

Beta testing:
- Demo new features pre-GA
- Catch demo-breaking bugs

Bug reports:
- Customer-discovered bugs
- Reproduce + report

Engineering's role with SE:

Technical updates:
- New features
- Architecture changes
- Roadmap visibility

Demo support:
- Help when demo breaks
- New feature training

Custom builds (rarely):
- Feature for big customer
- Engineering decides; not sales

Cadence:

Weekly:
- SE-Engineering sync (30 min)
- Top customer asks
- Bugs to file

Monthly:
- Roadmap review
- Field intelligence

Quarterly:
- Strategic input
- Big-deal architecture

Tools:

Shared Slack channel:
- #se-engineering
- Live customer questions

Linear / Jira:
- File bugs / feature requests
- Track resolution

Internal docs:
- Architecture for SEs
- Demo notes
- FAQ

Anti-patterns:

SE promises features:
- "We're building X next quarter"
- Engineering didn't agree
- Bad customer expectations

Engineering ignores SE:
- "Sales people don't know"
- Real customer pain dismissed
- Tension

Field intel filtered:
- Sales VP hides bad news from product
- Decisions made on incomplete info

Output:
1. SE-Engineering cadence
2. Tools / channels
3. Roadmap influence
4. Custom builds policy
5. Conflict resolution

The "SE-as-customer-voice" channel: best product orgs treat SE feedback as critical signal. Sales-side often sees patterns engineering misses.

9. Tools + sandbox

SE needs the right tools.

SE tooling.

Demo environment:

Sandbox:
- Personal customer-facing demo instance
- Pre-loaded with realistic data
- Resettable / shareable

Per-customer:
- Custom configurations
- Customer's logo / branding
- Real (anonymized) data sets

Architecture:
- Subdomain per SE / per demo
- Shareable URLs
- Time-limited if external

Tools:

CRM:
- Salesforce / HubSpot integration
- Per-account context

Conversation intelligence:
- Gong / Chorus
- Recording demos for review + training

Sales engagement:
- Outreach / Salesloft
- Less SE-centric; AE-led

Demo tools:

Reprise / Demostack:
- Demo automation; consistent demos
- Used at mid-market+

Walnut / Storylane:
- Interactive demos for self-serve

Loom:
- Async demo videos

Slack / Teams:
- Quick collab with AE / engineering

Demo data:

Synthetic data:
- Realistic but not real
- For sandbox

Industry-specific:
- Healthcare patients
- Financial transactions
- Customer-relatable

Customer logos / brands:
- For impact

Documentation:

SE wiki:
- Demo flows
- Common objections + answers
- Architecture diagrams
- Customer references

Updated:
- Engineering changes
- Sales feedback

Output:
1. Sandbox architecture
2. Tool stack
3. Demo data strategy
4. Documentation
5. Update cadence

The "Reprise / Demostack adoption" trend: at $20M+ ARR, demo-automation tools become standard. Consistent demos at scale; record once, use everywhere.

10. Measure SE impact

Metrics for SE function.

Measure SE function.

Per-SE metrics:

Win rate:
- Deals SE supported vs not
- Target: 20%+ improvement

Deal velocity:
- Time-to-close with SE vs without
- Target: 30%+ faster

ACV:
- Avg deal size SE-supported
- Often higher (technical deals)

POC conversion:
- POCs run → close rate
- 50%+ healthy

Team metrics:

SE attach rate:
- % of deals with SE
- 50-80% typical for technical SaaS

Coverage:
- AE:SE ratio in practice
- Compare to plan

Customer feedback:

SE quality:
- Survey customers
- "How was the technical engagement?"
- 1-10 score

Revenue impact:

SE-influenced revenue:
- $ closed-won with SE involvement
- % of total

ROI:
- SE compensation cost vs influenced revenue
- Should be 5-10x positive

Common signals:

SE under-utilized:
- Low attach rate
- AEs running their own demos
- Adjustment: train AEs to bring SE in

SE over-utilized:
- Burned out
- Not enough SE for AE coverage
- Adjustment: hire more SE

Wrong-fit deals:
- SE on small SMB deal
- Adjustment: define SE-deserving deal threshold

Reporting:

Per-SE scorecard:
- Win rate
- Velocity
- POC conversion

Team scorecard:
- Aggregate metrics
- Trend

Quarterly review:
- Performance
- Coaching focus
- Career progression

Anti-patterns:

No measurement:
- Hard to justify investment
- Random hiring decisions

Vanity metrics:
- "Demos run!" without outcomes
- Outcomes matter

Output:
1. Per-SE + team metrics
2. Customer feedback collection
3. Revenue impact
4. Reporting cadence
5. Continuous improvement

The "SE-influenced revenue" metric: makes SE function ROI-justifiable. Without it, finance question why headcount.

What Done Looks Like

A working SE function:

The mistakes to avoid:

Hire SE too early. Pre-$3M ARR; AE handles tech.
Wrong profile. Pure engineer for sales-engineering = mismatch.
Ambiguous AE/SE roles. Conflict; ineffective.
No mock-demo interview. Best signal skipped.
Drop into customer calls week 1. Embarrassing; slow ramp.
Feature-tour demos. Story wins; features lose.
No POC success criteria. Drags forever.
SE promises features. Bad customer expectations.
No measurement. Can't justify investment.
No career path. Top SEs leave.

Solutions Engineering Hire & SE Function

What Done Looks Like

1. Decide if you need SE

2. Define SE role — vs AE

3. Pick the right SE profile

4. Compensation design

5. SE recruiting + interview

6. Onboard SE — first 60 days

7. Demo + POC playbook

8. SE-Engineering relationship

9. Tools + sandbox

10. Measure SE impact

What Done Looks Like

See Also