WORK / CUSTOMER PERSPECTIVE, ENGINEERING DEPTH
I lead teams—and build alongside them.
I lead streaming platform engineering at Comcast and build AI-assisted systems for engineering teams. My career began on the customer-facing side of technology. That still shapes how I listen, decide what’s worth building, and connect technical work to the people who need it.
My instinct is to look for ways to engineer around friction rather than simply accept it. Sometimes that means aligning teams around a difficult delivery. Sometimes it means building a tool myself.
01 / HANDS-ON AI SYSTEMS DEVELOPMENT AT COMCAST
Less reconstructing status. More room to lead.
When AI coding tools became available at Comcast, I immersed myself in them. Our BrightScript work already happened in VS Code, so they fit naturally into my workflow. As I got comfortable, my response when a teammate or leader wondered what was possible became: “Give me a day to see what we can do.”
The problem started between the tools.
One project began with conversations, not a model. I sat down with other video-player leads to understand what slowed them down during a sprint. The recurring friction was communication: unclear direction, disconnected information, and time spent reconstructing what was happening.
Requirements lived in Confluence, implementation discussions happened in GitHub, and delivery was tracked across Jira and GitHub. Teams and partner organizations worked differently, but Slack was where we all communicated. I wanted management meetings to focus less on sorting tickets and more on decisions, delivery, and supporting engineers.
Build around where people already work.
I architected, built, and deployed an AI-assisted delivery platform alongside my leadership responsibilities. It went through several iterations, including a web application, before centering on a Slack-based experience. Retrieval brought engineering context together, and answers referenced their sources so people could trace them back to the underlying work.
Make the context useful, then actionable.
I built retrieval and agent workflows that supported issue triage, ticket creation, release updates, and delivery-risk alerts. The point wasn’t just to answer a question: it was to connect the information to a useful next step. Validation, security controls, and read/write boundaries were part of that work.
Knowing where to stop was part of the engineering.
For a scoped Roku workflow, I explored turning an issue or feature discussion in Slack into a proposed code change and pull request. I deliberately stopped short of full autonomy. That experience made the question of human responsibility concrete: how far should the system go, and what should engineers remain accountable for?
The part that mattered most was the team.
The most meaningful part for me was being able to focus more on my team and give engineers better tools to succeed. Connecting scattered context to practical actions was a way to support that goal—not an end in itself.
SELECTED TECHNICAL CONTEXT / PostgreSQL & pgvector · LangGraph & MCP · Temporal · AWS
02 / COMCAST · VIDEO IP ENGINEERING & RESEARCH · 2018–PRESENT
Engineering leadership for streaming platforms
A streaming experience may look simple from the sofa. Delivering it means coordinating player behavior, platform requirements, advertising, partner integrations, and the people responsible for each part.
Connecting teams and requirements
My leadership work spans Comcast, Sky, and Rogers teams, connecting customer requirements with engineering decisions and launch readiness.
Platform responsibility, at scale
Across platforms in my area of responsibility, the latest reporting period averaged approximately:
X1 — 70 million daily active users
Android — 1.8 million daily active users
iOS/tvOS — 1.5 million daily active users
Roku — 2 million daily active users
Rounded figures; users are counted uniquely within each platform per day. These figures describe platform scale, not a combined audience or an individual performance outcome.
From discovery to launch
I help carry integrations from discovery and requirements through design, validation, risk resolution, and launch. Delivery responsibilities have spanned Roku, iOS, Android, Web, tvOS, Chromecast, and Lightning-based experiences. The challenge is not simply supporting another device: it is keeping teams and partners aligned on what needs to work, and what is ready to ship.
Modernization without losing sight of playback
Selected work includes iOS/tvOS player modernization, reusable SDK capabilities, and streaming advertising integration. Alongside those capabilities, playback quality, automated testing, and platform reliability remain part of the delivery responsibility. These are team efforts; my role is to connect the technical work with the customer need and coordinate delivery across boundaries.
What this work has taught me
Customer understanding and technical depth reinforce each other. A requirement is more useful when the people implementing it understand the workflow behind it. For me, leadership means making those connections while staying close enough to the engineering to ask useful questions—and help work through the answers.
SELECTED TECHNICAL CONTEXT / Roku & BrightScript · Swift & AVPlayer · SDKs · Advertising integration
THE THREAD THROUGH THE WORK
A customer’s perspective, carried into engineering.
Stack Overflow — Sales Team Lead
Before moving into engineering, I was a Sales Team Lead at Stack Overflow. That commercial experience is an important part of how I work today: understanding customer needs and business priorities, then connecting them with what a technical team can deliver.
Working alongside developers also made a career in engineering feel possible. Their encouragement helped me take the leap into Turing’s backend engineering program. I brought that customer perspective with me rather than leaving it behind.
At Nextworld, I translated customer workflows into enterprise configurations and integrations, supporting discovery, validation, launch, issue resolution, and handoff. My earlier roles as Enterprise Sales Manager at GoSpotCheck and in account management and sales at Veritas also shaped how I listen for the need behind a request.
I trained in backend engineering at Turing in 2017–2018, following a B.S. in Business Management with a Sport Management minor at the University of Florida. I also established the GraphQL Denver/Boulder Meetup.
A backend beginning. A much wider toolkit.
Ruby and Rails were the starting point. Since then, I’ve worked with Python, Go, Dart, Swift, Objective-C, C, BrightScript, TypeScript, and Rust across production enterprise systems. When I started, I never imagined I’d work across that many languages. Learning the next one has become part of the work.