Successfully navigated four organizational transformations (RTI → Sicom → Xenial → Global Payments), adapting to evolving engineering cultures, tooling standards, and corporate processes. Following Global Payments acquisition (Fortune 500), integrated into enterprise-scale governance, security compliance (SOC1), and cross-functional stakeholder management practices.

Polyglot experience: Collaborated with cross-functional teams over 6-12 month engagements across diverse technology stacks including Node.js, LAMP (Linux/Apache/MySQL/PHP), and .NET ecosystems—demonstrating architectural thinking transcends language and platform boundaries.

• Software Architect (2020–Present): Final code review authority, architectural design, SRE responsibilities, stakeholder engagement
• Senior Developer (2017–2020): Technical leadership, mobile architecture, performance optimization
• Software Developer (2016–2017): Core development, DevOps transformation, database engineering

Technical backstop for 30+ microservices and applications serving 100,000+ users across hospitality. De facto Site Reliability Engineer, incident commander, and architectural decision-maker for production systems processing millions of payroll/scheduling transactions monthly.

• Perform the final code review on merge/pull requests for multiple teams geographically distributed.
• Lead Site Reliability Engineering (SRE) - own production incidents, centralized monitoring and alerting, and incident response for enterprise application portfolio.
• Participate in stakeholder, Scrum, and Kanban meetings.
• Provide technical design and guidance via Jira Tickets, Lucid Charts, and one-on-one meetings with team members—produce internal technical documentation and architecture decision records (ADRs) that establish engineering standards.
• Serve as primary technical mentor and architectural consultant for distributed teams—the go-to person for design patterns, system architecture, and engineering best practices.
• Lead post-incident reviews with development teams to identify root causes and prevent recurrence.
• Ongoing lead of a small team that's sole responsibility is to finish out a feature & product within a time frame that should not be possible on paper (on an as needed basis).

• Hybrid-Cloud Platform Architecture ("Moatify Pattern"): Architected abstraction layer enabling legacy Win32 SOAP monolith to coexist with modern REST APIs—avoided 18-24 month rewrite risk. I identified a "seam" in the business layer allowing legacy SOAP endpoints to remain unchanged while new JSON REST API built on shared foundation, while also improving security.

  Business rationale: Preserved existing integrations while enabling multiple agile teams to build cloud-native features in parallel. Trade-off: Accepted temporary architectural complexity to maintain revenue continuity—pragmatic choice over "perfect" greenfield rewrite. Now multi-team product development workstream replacing Win32 application incrementally.

• Designed and developed a near realtime data synchronization microservice that asynchronously detects changes to Employee data (1 million+) and sends it both to our Point-of-Sale systems and Cloud based services, in order to reduce the data duplication and manual key entry by our end users.
• Active participant in Service organization Control (SOC) 1 audit. Both in the compliance review meetings and active participant for rectifying any concerns found therein. Leading to a successful SOC1 report on behalf of the organization/application.
• Designed and developed an Identity Application microservice (before Identity as a Service). This service first began as a JWT Issuer for the new web based application, then later grew in responsibilities by handling all Basic Authentication for the legacy application & a facade to a MultiFactor Authentication Service. The application handle migrating the user account automatically.
• Designed a microservice dedicated to Fair Workweek Legislature for various State, City, and County jurisdictions in the U.S.A..
• Designed a microservice that's responsibility is to send emails, text messages, and push notifications to end users.
• Standardized logging patterns across enterprise application & infrastructure portfolio using a centralized observability platform.
• AI-Augmented Development Efficiency: Championed GitHub Copilot adoption across distributed teams, improving operational efficiency by integrating AI into technical design generation, code implementation, and review workflows. Created workflow where Copilot generates technical designs in Confluence, then reads those designs to accelerate implementation—reducing design-to-code cycle time.
• Site Reliability Engineering (SRE): Lead SRE for enterprise production environment with distributed microservices architecture. Own incident response, monitoring, and alerting across application and infrastructure layers. Bridge observability across centralized logging and infrastructure monitoring platforms. Established post-incident review process and knowledge distribution through runbooks to improve system reliability and team capabilities.
• Mediator Pattern Implementation: Introduced MediatR library as architectural standard to combat tight coupling and lack of separation of concerns across 10-16 developer team. Forces design-by-contract thinking and increases "how do I properly structure this?" questions versus "where's the easiest place to stick this code?" Measurable impact: Reduced production hotfix frequency and unhandled exception rates in services built with pattern.
• Enterprise-Scale Data Processing: Architected asynchronous message-driven system processing millions of records hourly across enterprise customer base. Business driver: Customer complaints about slow data propagation lengthening sales cycles and threatening renewals. Solution: Message bus abstraction layer enabling infrastructure flexibility and cloud migration without application rewrites, distributed consumer pattern for elastic scaling. Business impact: Unblocked enterprise sales, reduced customer onboarding friction, improved go-to-market velocity.
• Self-Service Vendor Integration Platform: Designed configuration-driven employee data import system supporting 100+ distinct vendor formats (CSV, XML, JSON) without code changes. Previous state: 4 weeks developer time per format, high bug rate, engineering bottleneck blocking sales. New state: Configuration-driven via database (JSON schema mappings); support teams onboard vendors without engineering involvement. Business impact: Reduced customer onboarding from weeks to days; eliminated engineering as sales bottleneck; reduced production defects.