Network Operations Technician II | Network & Broadcast Operations | Automation | Cybersecurity

I work in 24/7 network and broadcast operations supporting reliable delivery of positive and encouraging Christian radio. I focus on practical troubleshooting, operational reliability, and building automation that reduces repetitive work and improves situational awareness.

I am also pursuing a B.S. in Computer Science through UMGC and continue to develop skills in Python, PowerShell, cybersecurity, APIs, cloud tooling, and AI-assisted engineering.

• Network & Broadcast Operations: incident triage, infrastructure monitoring, troubleshooting, escalation, and service restoration
• Automation: Python and PowerShell tools for reporting, data processing, workflow improvement, and repeatable operational checks
• Cybersecurity: incident response, DFIR, SIEM concepts, security automation, and defensive tooling
• Software Engineering: Python, Java, JavaScript/TypeScript, SQL, REST APIs, Git/GitHub, and cloud-hosted applications
• AI Engineering: practical use of LLMs and agent workflows for research, analysis, automation, and technical operations

Python automation that compares sequential operational CSV reports, carries forward known issue context, identifies newly affected sites, and creates operator-ready output files.

Google Apps Script workflow that processes labeled email, prevents duplicate work, converts messages to PDF, organizes output in Google Drive, and supports scheduled execution.

Python automation for retrieving public economic-calendar data, filtering relevant events, and distributing a scheduled email summary using environment-based credentials and TLS.

Google Apps Script utility for reducing large MetaTrader optimization exports into a focused set of candidate results using configurable metrics and repeatable filtering.

I prefer repeatable checks, clear logs, documented assumptions, and automation that makes an operator's next decision easier. My goal is not automation for its own sake; it is safer operations, faster troubleshooting, and less time spent on repetitive manual work.

Public repositories are intended to contain only code, synthetic examples, and sanitized documentation appropriate for public sharing. Production credentials, private operational reports, internal configuration, customer/listener data, and other sensitive information do not belong in this portfolio.

My technical work and ministry service share the same goal: use the skills God has given me to serve people well. I volunteer through local ministry efforts and look for practical ways technology can support encouragement, reliability, and service.

"And whatsoever ye do, do it heartily, as to the Lord, and not unto men." — Colossians 3:23 (KJV)

• GitHub: krak3n84
• LinkedIn: Casey Craft