Kyle Scott Drayton

Cloud, Citrix & Infrastructure, designed to move fast without breaking things.

I’m a systems engineer focused on practical automation: building resilient platforms, cleaner workflows, and readable infrastructure that scales with people, not just code.

Current role

Sr. Infrastructure / Citrix Engineering

Primary focus

Automation, governance, reliability

Current stack

VDA, Terraform, Docker, scripts, open-source + AI

At a glance

What I do, why I do it, and what that means for the teams I support.

Automation-first mindset

I build repeatable systems so people spend less time “fighting the platform” and more time delivering real outcomes.

Security + uptime by default

Infrastructure posture, observability, and incident-resistant design are built into every workflow, not bolted on after the fact.

Clear communication

I write and operate so others can take action quickly. If it’s not understandable, it’s not done.

Current focus

The work I’m spending most of my cycles on right now.

Citrix

VDI + broker ecosystems

Improving reliability and user experience through cleaner app delivery, better log analysis, and practical tuning for real-world remote environments.

Cloud & Networking

Infrastructure where it counts

DNS, service entry points, segmentation, and automation loops that reduce mean time to recovery and keep operations boringly stable.

DevOps

CI, policy, and operational playbooks

Designing guardrails with practical cron jobs, monitoring, and clear ownership so teams can trust the platform while growing.

AI in ops

AI-assisted workflows

Pairing automation with guardrails to accelerate troubleshooting, reporting, and repetitive admin tasks without adding operational risk.

Selected tracks

Recent initiatives and areas where I’m pushing improvements.

Citrix + Azure optimization

Built practical performance checks and tuning loops to keep sessions stable and support tickets predictable.

  • Session launch reliability and latency reduction.
  • Broker and profile health routines.
  • Operational playbooks with clear handoff notes.

Infrastructure observability

Standardized heartbeat and alerting patterns for daily checks and exception handling.

  • DNS and mail stack health checks.
  • Dashboard-driven issue review loops.
  • Faster diagnostics for time-sensitive events.

Automation pipeline reliability

Reduced manual runbook drift with scriptable workflows and better error handling.

  • Self-healing behavior for recurring tasks.
  • Clearer status surfaces for action owners.
  • More consistent outcomes between shifts.

Resume and deeper work examples are available via request form or my PDF resume.

Continuous learning

What I’m actively sharpening this quarter.

  • Automation systems

    Practical IaC, policy automation, and AI-assisted operations workflows.

  • Certifications

    Azure and operations-focused platform validation while keeping momentum in day-to-day execution.

  • Product-minded engineering

    Turning platform tasks into reusable, understandable patterns for customers and teammates.

Want to collaborate?

Need a practical infrastructure audit, implementation review, or help shaping a deployment strategy?

Reach out