I own the whole problem.
I can move from business requirement to architecture, configuration, logs, API behavior, network path, identity policy, and operational process without losing the thread.
Systems engineering across the seams
I make complex technology work as one system.
SaaS. Identity. Cloud. Security. Infrastructure. Networking. Automation. AI. I connect the layers that usually become six teams, twelve tickets, and nobody's problem.
Hire an engineer who can own the architecture, understand the business constraint, get into the logs, and leave the system more reliable than he found it.
10+ years
Enterprise scale
Strategy to shell
Remote-ready
37
SaaS applications governed
39
Enterprise apps integrated
40%
Reduction in escalations
10,000+
Users supported at scale
3,500+
Distributed locations
25%
Downtime reduction
The 30 second pitch
Most engineers are strongest inside a layer. I am strongest between them.
The expensive failures are often not a broken server, bad SaaS app, identity policy, network path, API, or security control. They are the interactions between those things. That is where I do my best work.
I reduce organizational friction.
I translate between engineering, security, operations, vendors, legal, compliance, and leadership so the technical solution survives contact with the organization.
I automate recurring pain.
PowerShell, APIs, workflows, integrations, runbooks, and AI-assisted operations turn repeated manual work into dependable systems.
I make complexity maintainable.
A system is not finished when it works once. It is finished when it is observable, secure, documented, recoverable, and understandable by the next person.
Put me against the problem
What are you trying to fix?
Select the situation that sounds familiar. This is the part of the conversation where I stop sounding like a résumé and start sounding like the person you need.
How I attack it
Rationalize the portfolio. Map ownership. Fix lifecycle and integration debt.
I have governed large SaaS portfolios, standardized enterprise applications, worked through vendor and security reviews, and connected platforms through identity, APIs, workflow, and operating process.
Proof: 37 SaaS applications governed and 39 enterprise applications integrated into standardized processes.
How I see the stack
One architecture. Not a collection of departments.
I think in systems, dependencies, interfaces, failure domains, and operational ownership.
Business outcome
Reliable, secure, scalable operation
SaaSIdentityAPIsAutomation
CloudSecurityInfrastructureNetworking
GovernanceObservabilityDocumentationRecovery
Career signal
Built from support floor to senior engineering.
The progression matters. I learned the user, the endpoint, the network, the platform, the cloud, the identity plane, the security constraint, and the executive requirement in the order real systems reveal them.
2025 - 2026
GuidePoint Security
Senior Security Engineer
Security engineering and technical consulting across enterprise cloud, SaaS, identity, hybrid infrastructure, integrations, and operational constraints.
2025
Epic Games
SaaS Engineer
Business-critical SaaS and cloud-connected systems in a global, high-availability environment, including lifecycle, integrations, access, workflows, and service improvement.
2022 - 2025
Uber Technologies / IMCS Group
Senior Systems Engineer
Global SaaS and enterprise systems, Microsoft 365, cloud platforms, identity, APIs, automation, governance, documentation, and cross-domain incident coordination.
2021 - 2022
Citrix / Genesis Global
SaaS Administrator
SaaS governance at portfolio scale, vendor onboarding, security review coordination, lifecycle operations, APIs, and interoperability.
2019 - 2021
Covenant Technology Solutions
Senior Systems & Network Engineer
Infrastructure, networking, virtualization, cloud migration, identity, client architecture, advanced escalation, and technical leadership across multiple organizations.
2015 - 2019
Mattress Firm
IT Operations & Systems
Large-scale distributed support, learning systems, enterprise applications, automation, access controls, team development, and operational process improvement.
From elevator pitch to decision
You do not need another person who can operate one console.
You need someone who can understand why the consoles disagree, connect the teams around them, make the architecture coherent, and then automate the parts that should never have required a person in the first place.
HireSenior / principal-caliber individual contributorSystems, SaaS, platform, identity, cloud, security engineering
EngageCross-domain technical consultantArchitecture, modernization, integration, reliability, operational cleanup
EscalateThe problem nobody else ownsWhen the failure crosses product, infrastructure, identity, network, security, and process
Start with the problem
Tell me what is hard.
A role, architecture problem, integration, migration, reliability issue, automation opportunity, or system that has become too complicated to own. Give me the constraint and I will understand the conversation quickly.
No phone number or direct email is published on this site. Contact details stay private until I choose to respond.