David Spurlock
RésuméContact
Menu

Supporting technical portfolio

Hands-on technical work that supports the professional story.

SignalCall, Reconductor, and the Security Operations Lab Collection provide additional evidence of David’s technical fluency, product judgment, and security awareness. The primary professional story remains in Work and Experience.

Selected technical builds

Three focused examples of product thinking and technical fluency.

The collection is intentionally small: one revenue-intelligence product, one safety-first security copilot, and one group of focused security labs.

Code-native project summary; no repository screenshot is published.
Revenue intelligencePortfolio MVP

SignalCall

An evidence-grounded sales-call analyzer that turns a transcript into MEDDICC coaching, deal risks, CRM-ready notes, follow-up questions, and a customer email.

  • Python
  • Streamlit
  • Pydantic
  • SQLite
  • LLM APIs
Independent build · curated public case studyView supporting project
Reconductor read-only service inventory showing synthetic scoped hosts, normalized services, and evidence provenance.
The read-only workspace keeps scope, observations, and artifact provenance in the same review surface. All displayed data is synthetic.
Security engineeringActive development

Reconductor

A safety-first reconnaissance copilot for authorized labs and CTFs, built around explicit scope, typed actions, human approval, evidence provenance, and a read-only review workspace.

  • Python
  • FastAPI
  • React
  • SQLite
  • Docker
Independent build · curated public case studyView supporting project
Dark security operations dashboard showing synthetic alert posture metrics, severity distribution, and authentication activity.
A synthetic SOC dashboard is one view inside the collection; its metrics and alerts come from a fixed local dataset.
Security operationsFive validated labs

Security Operations Lab Collection

A connected set of local security labs covering controlled attack telemetry, detection and triage, packet evidence, secure application controls, and cloud-monitoring architecture.

  • Python
  • Docker
  • Elastic
  • PCAP
  • Flask
Independent build · curated public case studyView supporting project

How to read the portfolio

Evaluate the judgment behind the implementation.

Each case begins with who needs to decide what. Architecture, controls, screenshots, and tests are useful only when they make that decision safer or clearer.

  1. User and problem

    Who the system serves and what breaks in the current workflow.

  2. Product decision

    The boundary or tradeoff that shaped the implementation.

  3. Inspectable evidence

    What a reviewer can see without private source access.

  4. Limits

    What remains local, synthetic, incomplete, or outside the claim.

Role in the portfolio

Technical projects are supporting evidence—not the headline.

David’s professional value is grounded in customer discovery, commercial judgment, stakeholder alignment, and execution. These projects show the technical curiosity and hands-on fluency that strengthen that work.

Start with Selected Work or Experience, then use these case studies when a role or conversation benefits from a deeper technical example.