Section200

Experience

Roles5 leadership & engineering

One through-line: keep the system up while the business grows around it. The systems changed, from carrier networks to SaaS, media and public services. The job didn’t.

For full career history, visit my LinkedIn profile. Each role reads the same way: the problem I was handed, what I owned, the decisions that mattered, how we executed, and what it produced.

Yippify

Consultant

Consulting & government technology

Problem: Government teams, startups and founders who need web and mobile products shipped by a small team, with no budget for a rewrite later.
Responsibility: Architecture, technical strategy and delivery leadership across client engagements, plus hands-on engineering wherever it takes risk out of the build.
Decisions: Choose well-understood platforms (Django, Rails, React and Next.js on AWS) that a client team can own after hand-over.
Infrastructure as code and CI/CD from the first sprint, not the last.
Record architecture decisions in writing so the reasoning survives the engagement.
Execution: Small stacked pull requests, iterative releases stakeholders can see every sprint, and QA and product in the same planning loop as engineering.
Outcome: Mobile and web applications delivered for government, startup and entrepreneur clients.
Case studies: 303 · Modernizing a public-sector service without a big-bang rewrite 304 · LLM document processing with a human in the loop

Media publishing platform

Chief Technology Officer

Media platforms

Problem: Publishing platforms, a portfolio of media titles, competing for audience against far larger media companies on search and social.
Responsibility: Overall technical strategy and engineering leadership for the publishing platforms.
Decisions: Treat page speed, structured content and social distribution as platform features rather than editorial afterthoughts.
Invest in the shared publishing platform instead of per-title one-offs.
Execution: Rebuilt the delivery path from editorial tooling to rendered page, and measured every release against traffic and engagement.
Outcome: Organic traffic, social traffic and social engagement each up 50%.
Case studies: 302 · Making a publishing platform compete on distribution

Global communications platform

Co-Founder & CTO

SaaS, founder

Problem: Build a service from nothing, then keep it fast for users spread across North America, Europe and Asia.
Responsibility: Co-founded the company. Built the network and the multi-tier web and mobile application, and led engineering from first line of code to acquisition.
Decisions: Plan the first data center deliberately, then leave it: move from a single site to cloud regions on three continents.
Route users by geography to the nearest region to cut latency and improve call and session quality.
Execution: Staged the migration region by region so the platform kept serving users throughout, and grew the team and architecture with the customer base.
Outcome: 400k+ users, multimillion-dollar growth, and a successful acquisition.
Case studies: 301 · From one data center to three continents

Voice services

Vice President of Operations

Voice & web services

Problem: A growing voice service whose software and network both had to scale without dropping calls.
Responsibility: Directed software engineering and network operations across web applications and the voice network.
Decisions: Plan capacity expansions ahead of growth rather than after incidents.
Execution: Built a resilient, supportable environment for application development and the voice network, with operations and engineering run as one function.
Outcome: A stable, scalable platform through the company’s growth phase, with expansion planned ahead of demand.

National broadband network

Member of Technical Staff

Carrier networks

Problem: A nationwide broadband network spanning 2,000+ collocations that had to keep expanding without degrading service.
Responsibility: ATM, IP, VoIP and OC infrastructure integration, expansion, deployment, capacity planning and optimization. Operations for the Network Security and IP Services group.
Decisions: Capacity planning driven by measured utilization across the footprint.
Standardize process, training and escalation so operations scale beyond individual experts.
Execution: Process development, training, escalation support and deployment for the ATM, IP and VoIP networks and for network security services.
Outcome: Integrated and expanded carrier infrastructure across the national footprint while supporting network security and IP services operations.
Case studies: 306 · Capacity planning across 2,000+ collocations

Earlier

Broadband services, Technical Support Engineer
Technical services, Technical Support Specialist

Where it started: supporting the network before designing it.