We’re an early-stage startup.We changed our name to reflect our new direction.

Designed and built a bespoke, cloud-native, enterprise, device fleet management system for a growing small business. This work is covered by an NDA; so, I can discuss the technical details of it only in a high-level manner.Some features of the system:● Distributed (multi-region),● Highly-available (warm-standby failover),● Event-driven (uses a message queue system),● Customer (companies) device fleet management,● Customer self-service. Cloud-provider neutrality was not a requested feature. This was a cost-related decision.

Primarily, providing technical guidance and training.

Redesigned the business model, and designed a fully-monetized, personal AI agent ecosystem.

Modification of their existing web apps.Identified and fixed a massive security hole in their system that was allowing SQL injection attacks, which were happening multiple times daily.

Non-management, leadership role. While in this role, I designed several pieces of system architecture:● Compliance API: ensures that legally-required verbiage (e.g., GDPR) — based on the customer’s legal business jurisdiction — is displayed during the purchase process. This prevented legal issues surrounding online privacy laws that were due to go into effect within a short timeframe.● Google reCAPTCHA bypass for the QA team: this allowed them to avoid their having to manually do the reCAPTCHA with every end-to-end test without disabling the rendering of the reCAPTCHA component. This enabled them to perform four times as many end-to-end tests per hour.● Pre-customer chat system: this custom chat system added the ability for pre-customers (i.e., still shopping for hosting, but not yet a paying customer) to chat with pre-sales support via chat instead of phone or email. This increased average sales velocity, and average order revenue.

After a recent acquisition RigNet performed a reorganization of the business, and made their CTO (of the acquired company) the head of software development, which meant I needed a new role; hence, I was re-titled as Senior Software Engineer.The primary project assigned to me while in this role was the the engineering and development of a dynamically-provisioned, remote-monitoring, live-streaming, video service.Customer cost-reduction was the primary business driver of the service.Used domain-driven design to facilitate rapid project delivery.I was the only engineering resource assigned during the first two and a half years of the project.

I was both a technical software engineering manager and an individual contributor software engineer.Also, during this time I worked on an enterprise architecture integration project using MuleSoft, ServiceNow, SAP BusinessOne, and a broad set of other supporting technologies.After this project is when I began the remote video project.