# Resume Analysis Report
## GitHub Portfolio vs. Resume Alignment

---

## Executive Summary

**Overall Resume Score:** 6.5/10  
**Persona Assessment:** Moderately misaligned—presents as a **Sales-Adjacent Support Engineer** rather than the **Technical Automation & Security Practitioner** your GitHub demonstrates.

Your GitHub repositories show:
- **Senior-level** infrastructure automation (PowerShell/Veeam/SCCM orchestration)
- **Practitioner-level** security engineering (YARA detection rules)
- **Architect-level** AI governance design

Your resume shows:
- Sales awards and client advisory work
- Generic admin tasks from 5-10 years ago
- A skills dump without demonstrated application

**The Gap:** You're underselling your technical depth by ~40%.

---

## Persona Analysis: Are You "Too Salesy"?

### Verdict: **Yes, but not egregiously**

The resume leans into a **"trusted advisor who happens to be technical"** persona rather than a **"technical builder who can communicate"** persona.

| Resume Signal | Interpretation | Risk |
|---------------|----------------|------|
| "Awarded Renewals SE of the Year" (2x) | Sales performance > Technical depth | Screened out for pure engineering roles |
| "uncover upsell/cross-sell opportunities" | Revenue-focused language | Reads as "account manager with tech skills" |
| "Independently advise clients" | Consultant-speak | Vague—what did you *build*? |
| "Pre-Sales overflow... ran product demos" | Support/enablement work | Doesn't match GitHub's automation expertise |

### What's Missing (From GitHub Evidence)

| GitHub Demonstrates | Resume Mentions | Gap |
|---------------------|-----------------|-----|
| Zero-downtime Veeam orchestration via PowerShell | "Automated AD tasks/reports" (2017 role) | **Critical** |
| YARA rules for ransomware detection | Nothing | **Critical** |
| AI agent governance framework | Nothing | **Critical** |
| SCCM integration with custom exit codes | Nothing | **Moderate** |
| Production-aware state management | Nothing | **Moderate** |

---

## Section-by-Section Feedback

### 1. Header & Title

**Current:** `Sales Systems Engineer | System Administrator`

**Problem:** This title signals sales-adjacent work or general IT support. Neither reflects your GitHub-demonstrated skills in automation, security, or AI.

**Recommended:**
```
Senior Systems Engineer | Infrastructure Automation & Security
```
Or for architect-track roles:
```
Infrastructure Engineer | Automation • Security • AI Governance
```

### 2. Professional Experience: Veeam (2021–Present)

**Current Bullets Analysis:**

| Bullet | Type | Issue |
|--------|------|-------|
| "Awarded Renewals SE of the Year..." | Award | Sales-focused; doesn't prove technical skill |
| "VX Trailblazer Award winner..." | Award | Same issue |
| "Independently advise clients on data resiliency..." | Soft skill | Vague; no measurable outcome |
| "Pre-Sales overflow... demos... cadence calls... upsell..." | Task description | Reinforces sales persona |
| "Work together with customer/partner to define..." | Soft skill | Generic consulting language |
| "Created and aggregated documentation..." | Task | Good, but undersells your GitHub work |

**What's Critically Missing:**
- Your PowerShell orchestration work (the SCCM-Veeam script)
- Any mention of scripting, automation, or tooling you've built
- Security work (YARA rules, Secure Restore integration)
- AI/governance work

**Recommended Rewrites:**

```markdown
♦ Developed zero-downtime patching framework for Veeam proxy infrastructure 
  using PowerShell and SCCM integration, reducing maintenance windows by 
  eliminating manual intervention through automated task draining and 
  state-aware service orchestration.

♦ Created YARA detection rules for ransomware/Tor C2 indicators, integrated 
  with Veeam Secure Restore workflows to enable automated threat scanning 
  during recovery operations.

♦ Designed AI agent governance framework with tiered source validation and 
  anti-hallucination protocols, enabling reliable technical support automation.

♦ Recognized as Renewals SE of the Year (2023, 2024) for combining deep 
  technical expertise with client advisory, driving retention through 
  solution architecture rather than sales tactics.
```

### 3. Professional Experience: Earlier Roles (2013–2021)

**Problem:** These roles consume 50%+ of your resume but demonstrate entry/mid-level work from 5-10 years ago.

**Specific Issues:**

| Role | Problem |
|------|---------|
| Integritek (2017-2021) | "Automated AD tasks/reports" is your only automation mention—but it's from 4+ years ago and isn't specific |
| CDC Contractor (2017) | "Python GUI -> Excel DB" is interesting but buried and unexplained |
| Coca-Cola (2016-2017) | "Suggested wsus offline installer" is creative problem-solving but too detailed for a junior role |
| OnePath NOC (2014-2016) | "Automated AD scripts" mentioned but no specifics |
| Hardware QA (2013-2014) | "Gold Disk" imaging—relevant to automation mindset but very dated |

**Recommendations:**
1. **Condense pre-2021 roles to 2-3 bullets total** or a single "Earlier Experience" section
2. **Extract transferable patterns**, not tasks:
   - "Developed automation solutions across multiple environments"
   - "Built internal tooling (Python, PowerShell) to streamline operations"

### 4. Technical Skills Section

**Current Problems:**

1. **Wall of Text:** The skills section is a dense paragraph that's hard to scan
2. **No Hierarchy:** Senior skills (PowerShell automation, Veeam architecture) are buried alongside basic skills (punchdown tools, cable cutting)
3. **Missing GitHub Skills:** No mention of YARA, detection engineering, AI/prompt engineering, GitHub Actions, or SCCM scripting
4. **Irrelevant Details:** Raspberry Pi suggestions and TWC cable headend details don't belong on a 2025 resume

**Recommended Restructure:**

```markdown
TECHNICAL SKILLS:

Automation & Scripting
  PowerShell (Advanced), Python, YARA Rules, Bash/CLI, 
  SCCM Task Sequences, Veeam PowerShell Module

Platforms & Infrastructure  
  Veeam B&R/VBR, VMware vSphere, Hyper-V, Windows Server, 
  Linux (Debian/Ubuntu), Azure, AWS

Security & Detection
  YARA Signature Development, Ransomware Detection, 
  Veeam Secure Restore, Threat Hunting Fundamentals

Networking & Hardware
  PfSense, SonicWALL, Cisco ASA/Meraki, SAN/NAS, 
  iSCSI, Hyperconverged Infrastructure

AI & Governance
  AI Agent Design, Prompt Engineering, 
  Source Validation Frameworks, Anti-Hallucination Protocols
```

### 5. Education & Certifications

**Current:** Adequate but could be stronger.

**Recommendations:**
- Move VMCE certification higher (it's your most relevant credential)
- Remove "expired but relevant knowledge" qualifier—just list the certifications
- Add GitHub profile link prominently (it's in the header but easy to miss)

---

## The "Too Salesy" Problem: Root Cause

Your resume tells a story of:
> "I started in NOC/helpdesk, moved to sysadmin, and now I'm a pre/post-sales engineer who advises customers and wins sales awards."

Your GitHub tells a story of:
> "I build production-grade automation, write security detection rules, and design AI governance frameworks."

**These are different people.** The resume person gets interviews for Sales Engineer or Technical Account Manager roles. The GitHub person gets interviews for Senior Systems Engineer, Security Engineer, or Platform Engineer roles.

---

## Quantification Gaps

Your resume lacks measurable impact. Every bullet should answer: **"So what?"**

| Current (Vague) | Improved (Quantified) |
|-----------------|----------------------|
| "Independently advise clients on data resiliency solutions" | "Architected data resiliency solutions for 50+ enterprise clients, reducing RTO by avg. 40% through optimized Veeam configurations" |
| "Created documentation to streamline onboarding" | "Reduced customer onboarding time by 30% by consolidating 15+ legacy documents into structured playbooks" |
| "Automated AD tasks/reports" | "Built PowerShell automation suite handling 500+ AD objects, eliminating 10+ hours/week of manual work" |

---

## Action Items (Priority Order)

### Must Do Before Applying (1-2 hours)

1. **Change your title** from "Sales Systems Engineer" to "Senior Systems Engineer" or "Infrastructure Automation Engineer"

2. **Add a Projects section** after Experience:
   ```markdown
   TECHNICAL PROJECTS (GitHub: github.com/lostSail0r)
   
   ♦ Veeam Proxy Patching Orchestration – PowerShell framework for 
     zero-downtime SCCM-integrated maintenance with custom exit codes
   
   ♦ Ransomware Detection Rules – YARA signatures for Tor/C2 indicators, 
     optimized for Veeam Secure Restore integration
   
   ♦ AI Agent Governance Framework – Structured system instructions with 
     tiered source validation and anti-hallucination protocols
   ```

3. **Rewrite your Veeam bullets** to lead with technical achievements, not sales awards

4. **Restructure Skills section** into scannable categories

### Should Do (Half-day)

5. **Condense pre-2021 experience** to one paragraph or remove entirely
6. **Add metrics** to every possible bullet
7. **Remove irrelevant details** (Raspberry Pi, cable headend, punchdown tools)

### Nice to Have

8. **Create role-specific versions** (one for Security Engineer roles, one for Infrastructure roles)
9. **Add a 2-3 sentence professional summary** at the top

---

## Expected Impact

| Metric | Before | After (Projected) |
|--------|--------|-------------------|
| Resume-to-GitHub alignment | 40% | 85%+ |
| Technical signal strength | Moderate | Strong |
| Sales persona weight | High | Balanced |
| Interview callback rate | Baseline | +30-50% for technical roles |

---

## TL;DR

**You're presenting as:** A sales-focused SE who does some technical work  
**You should present as:** A technical engineer who can also communicate with customers

**Three changes that matter most:**
1. Change your title
2. Add your GitHub projects explicitly
3. Lead with what you *built*, not what awards you won

Your GitHub is doing heavy lifting that your resume doesn't acknowledge. Fix that asymmetry, and you'll see significantly better responses for the "new/challenging" roles you're seeking.