Selected Technical Work
Additional Projects, Integrations & Technical Problem Solving
Not every technical project needs to become a full case study.
Throughout my career I have worked on hundreds of smaller architecture, integration, automation and troubleshooting efforts that crossed traditional technology boundaries. These projects often require understanding several systems at once, identifying where responsibility changes between them, and determining how to make the complete solution work reliably.
The examples below highlight some of that additional work.
Cloud Communications & Mobile Calling
WebRTC • SIP • RTP • Twilio • Bandwidth • PSTN • DIDs • Enterprise PBX
Modern communications increasingly spans mobile applications, cloud communications providers, traditional telephone networks and enterprise PBX environments.
I have worked extensively with third-party communications providers including Twilio and Bandwidth, designing and supporting integrations that connect these different environments.
Examples include:
- SIP trunking and PSTN termination for premise-based telephone systems
- DID provisioning and management
- Integration of cloud communications services with enterprise PBX environments
- Mobile/BYOD application calling using the Twilio SDK and WebRTC
- Direct PSTN calling from mobile applications
- Privacy and masked-calling workflows
- SIP connectivity between cloud communications platforms and customer premise PBXs
- Troubleshooting call flows across WebRTC, SIP, RTP, PSTN and enterprise voice infrastructure
- Supporting regulatory and registration requirements associated with application-based calling
These environments are particularly interesting because a single call may cross several independently operated systems.
A problem experienced by a mobile user may originate in the application, WebRTC session, cloud communications provider, SIP signaling, media path, carrier network, customer firewall or PBX.
Solving those problems requires understanding the complete call path rather than treating each component in isolation.
Hybrid Cloud & Connectivity
Azure • BGP • VPN/IPsec • Routing • Firewalls • Hybrid Infrastructure
Cloud adoption rarely happens in isolation. Existing applications, networks, security controls and datacenter infrastructure still need to communicate reliably with cloud environments.
My Azure work has included building and supporting hybrid connectivity between traditional infrastructure and cloud-hosted systems, including:
- Site-to-site VPN connectivity
- Routing between cloud and premise environments
- Palo Alto firewall integration
- Network segmentation and security controls
- Multi-zone cloud deployments
- Private and provider-based connectivity
- Integration of cloud resources with existing enterprise networks
- Troubleshooting routing, firewall, VPN and application connectivity across hybrid environments
I approach hybrid cloud as an extension of the overall system architecture rather than as a separate technology stack.
The same fundamentals still matter: routing, addressing, security boundaries, redundancy, observability and understanding exactly how traffic moves from one system to another.
Automation, APIs & Systems Integration
Bash • PowerShell • PHP • Python • SQL • APIs • Linux
I have used scripting and automation throughout my career to connect systems, eliminate repetitive work and solve problems where an off-the-shelf product was not the right answer.
My programming background began with industrial control systems and later expanded into infrastructure, Linux and business systems.
Examples of this work include:
- Linux and infrastructure automation
- API integrations between systems
- Data transformation and synchronization
- Operational scripts and utilities
- Monitoring and health-check automation
- Database-driven tools and integrations
- Automated configuration and deployment tasks
- Troubleshooting utilities used to collect and correlate information across systems
My strongest scripting experience has historically been with Bash, PHP and PowerShell, along with extensive SQL work. I also use Python and continue to expand its role in my automation work.
The objective is rarely automation for its own sake. The objective is to make a system simpler, more reliable, easier to operate or easier to troubleshoot.
Troubleshooting Across Technology Boundaries
Packet Analysis • Linux • Networking • SIP/RTP • DNS • TLS • Firewalls • Applications
Some of the most difficult technical problems occur when every individual system appears to be working correctly.
An application problem may actually originate in DNS.
A voice problem may be routing, NAT or firewall related.
An intermittent service failure may originate in a load balancer, certificate, network path, operating system or external provider.
For complex incidents, I work from the evidence outward.
That may involve:
- Packet captures and protocol analysis
- Application and operating-system logs
- SIP signaling and RTP media analysis
- Routing and firewall inspection
- DNS and TLS troubleshooting
- API testing
- Database queries
- Linux command-line diagnostics
- Comparing behavior across systems, networks and environments
The goal is to understand the entire transaction or communication path and identify where observed behavior first differs from expected behavior.
This approach has followed me throughout my career—from industrial automation and machinery controls to enterprise networks, communications platforms, datacenters and cloud infrastructure.
The technology changes. The troubleshooting method does not.
Independent Web Development and integrations
Linux • Apache httpd • PHP/Perl/Bash/Python • API's • PCI • MariaDB/Galera • MySQL
As a hobby I have been helping folks with websites and web applications for more than 20 years. Early on it was shopping carts and payment systems integration, developed a couple of systems still in use today
- An Order/supply/procurement/warehousing system specialized for bulk/wholesale
- A complex records, request, and processing system for Specialized Insurance Industries
Front ends and business logic mostly in PHP, with a ton of supporting tools and back end written in Perl, Bash, and Python, API's and integrations, scheduled jobs etc - running on IAAS cloud services (full stack, and full system and data protection).
How This Fits Together
These projects span different technologies, but the engineering process is consistent:
Understand the requirement → map the complete system → identify the integration boundaries → design the solution → test the assumptions → troubleshoot from evidence → make it operationally supportable.
That is the kind of work I enjoy most: problems where networking, infrastructure, communications, software, cloud services and people all have to work together.