Platform & AI engineering leader. Over 20 years across the stack — sysadmin to executive — building the systems, teams, and operating models that turn ambition into delivered outcomes. Software is one piece; the work also covers infrastructure, security, identity, and the operating practices that hold it together. Deep enough to own the architecture. Broad enough to lead across platform, infra, data, app dev, and AI.
Currently leading 20+ engineers across 5 functions in US, LATAM, and APAC. Hands on the architecture. Hands on the org. Lead from wherever the pressure is.
Over 20 years across engineering and infrastructure leadership — sysadmin, engineer, manager, architect, executive. The pattern that keeps showing up: solve the technical and the organizational constraints in the same move. The technically right answer the org can't absorb isn't actually the right answer.
What that looks like in practice: large-scale network overhauls and modernization, cloud migrations from legacy datacenters to AWS, high-availability system designs holding 99.99%+ SLAs in 24/7 enterprise environments, disaster-recovery planning and rehearsal. Custom software handling millions of mission-critical authentication events for a revenue-driving platform; security and compliance programs for SOC 2 and PCI customers; AI-native applications on modern serverless and microservices stacks; engineering teams built and grown across architecture, data, infrastructure, and software development. Same instinct each time: cut to the structural fix instead of papering over it.
"A great IT business leader but still maintains architect-level technical proficiency."
— darrell wilson · director, collaboration solutions
years
20+
engineering · infra · platform
scope
5
platform · ai · infra · data · appdev
geo
7+
countries · na · latam · eu · apac
chapters
5
sysadmin → exec
currently · updated
shippedAgentic Blueprint — internal Claude Code plugin for my engineering team · 100+ skills · 11 specialist agents · KB + hybrid search
ossTKR — token reducer CLI proxy · MIT
#02
How I lead.
AI doesn't change what good engineering leadership looks like. It just compresses the timelines for getting it wrong.
— from the working notes
01Lead from wherever the pressure is. Platform, infra, AI, security, frontend, the customer room — versatile across domains because that's what cross-discipline teams need from a leader. Plug in where the work is hardest, then back out once the team can carry it.
02Architect's depth. Executive's view. Hands stay on the architecture. Eyes stay on the business. The technically right answer the org can't absorb isn't the right answer. I build structure, momentum, and clarity — zoom in on the details, zoom out to the big picture, connect the dots so teams move faster with more confidence.
03Build the team while building the system. The work isn't done if the team didn't level up doing it. Direct reports across decades keep using the same words — leads by example, creates space for the decision instead of dictating it, leaves engineers better than they were.
04Brutally honest. Composed under pressure. Trust is the operating system. I tell people what I actually think, stay calm when the system is on fire, and carry the weight of the conversations that go deep — platform, AI roadmap, audit, customer escalation.
05Always learning, on purpose. Networking through security, cloud, data, AI — over 20 years of deliberate breadth. Finished B.S. and M.S. in Information Technology at WGU in 2025 while running a VP-level org, on top of a long stack of AWS, Cisco, Palo Alto, F5, Okta, and Lean Six Sigma credentials. The breadth is the point — it's what lets me lead cross-discipline teams without losing the thread.
CLI proxy + Claude Code plugin that recovers Opus cap headroom on Pro/Max subscriptions.
Compresses tool output, swaps grep/glob/read cycles for BM25 search, delegates heavy tasks to cheaper models, and tightens response length. 60–90% token savings per filtered command. Single static Go binary, MIT-licensed.
Claude Code plugin I built for my engineering team — turns the CLI into a disciplined, multi-agent dev team for shipping software with agentic AI tooling.
Opinionated engineering operating system: 100+ skills organized by lifecycle phase (design, implement, review, ship, validate, troubleshoot), 11 specialist agents with bounded tool allowlists and explicit output contracts (architect, senior-implementer, reviewer, security-reviewer, tester, verifier, infra-release, docs-writer, …), ~60 KB articles across 14 categories codifying project standards, an MCP server registry, and a hybrid BM25 + tier-ranked search engine that replaces 5–10 file reads per question with one trust-ranked answer set. Lifecycle state machine persists session context across windows; privacy-first telemetry tracks skill usage and time savings.
Side project · live
SyncBoards
Collaborative Kanban with an AI sidekick
real-time · AI chat · automations · family mode
Kanban for teams and families — drag-and-drop boards that update live across every device, with an AI assistant baked into every board.
Drag-and-drop tasks across lists with checklists, due dates, labels, attachments, and a calendar view. Every change syncs in real time across browsers and phones — no refresh, no stale state. Each board has its own AI chat that already knows the work: ask "what's overdue?" or "summarize this PDF I attached" and it can also create, move, and update tasks for you on the spot. A no-code automation builder turns triggers ("task moved to Done", "due date reached") into actions ("notify the assignee", "move it to Archive"). Family mode adds a parent dashboard with COPPA-compliant consent, AI transcript review, and a Socratic Coach Mode for kids that asks guiding questions instead of handing over answers.
—The Cheapest Model Is Not Always the Cheapest Workflowdraft
#05
On record.
CF
Versatility
“Skills range from design to security, troubleshooting, and everything in between. An excellent people leader who understands the need to be versatile and adaptive.”
“The benchmark of what an Engineering Leader is supposed to be — fusing business interests with technological challenges while enthusing the team to grow up the technical ladder.”
“A great IT business leader who still maintains architect-level technical proficiency. Simplifies complex IT initiatives so all stakeholders can understand the path to the goal.”