Army veteran. Systems thinker. Operator-centric builder.
I stabilize and scale high-risk, compliance-driven environments across IT, cybersecurity, and cleared operations.
15+ years of director-level operational leadership in federal contracting environments.
Direct report to President/COO across as many as five entities simultaneously, governing IT,
cybersecurity, compliance, cleared operations, and facilities under active DoD regulatory frameworks --
with no dedicated support staff in any domain. Annual budget under direct management: $324,000.
I build systems designed to outlast my involvement.
Eliminated chronic multi-site outages by designing and executing full identity unification across fragmented Active Directory environments
Built audit-defensible CMMC and NISPOM programs across multiple entities, achieving sustained compliance with no substantive control failures
Reduced telecom spend by 94% by architecting and deploying a custom multi-site VoIP system from scratch with no prior PBX experience
Recovered from a failed MSP engagement by restructuring vendor strategy, correcting licensing waste, and regaining operational control
Deployed a production CUI enclave aligned with NIST 800-171 and CMMC Level 2 requirements within two weeks of vendor selection
02 When to Engage
I am typically brought in when:
Systems are undocumented, fragile, or failing under operational load
Compliance requirements (CMMC, NIST 800-171, NISPOM) introduce risk without a clear implementation strategy
IT, security, and operational responsibilities are fragmented across teams or vendors
Leadership needs a single accountable owner to stabilize and structure the environment
Vendor relationships are misaligned, underperforming, or creating cost and control issues
I operate across domains to bring systems under control, establish defensible structure, and build environments that remain stable without constant intervention.
03 Operating Philosophy
How I Approach the Work
1
Clarity as a Form of Kindness
Defining boundaries, documenting workflows, and creating shared understanding enables teams to move faster and make better decisions under ambiguity. Documentation is not overhead -- it is the product. The goal is that someone else can navigate the work without guessing.
2
Stewardship Over Authority
I design for operators, not architects. Low-friction frameworks that reduce burden, mitigate error, and protect the organization. The measure of a good system is whether it works when I am not watching.
3
Earned Freedom Through Discipline
Early investment in structure, repeatability, and scalable systems is what makes sustainable speed possible later. I own my decisions -- including the ones that do not age well -- and use that clarity to drive improvement rather than repeat the error.
04 Competency Alignment
Domain Coverage by Story
The following case studies demonstrate how this work is executed across IT, cybersecurity, compliance, and operations.
Click any domain header to highlight stories where it is a primary strength. Click a story title to load it in the panel below, or scroll to it in the full narrative section.
The design, information architecture, color palette, UX structure, and content direction of this site were directed by Joel Sandoval.
Code implementation was built with the assistance of an AI language model under direct supervision and iterative instruction.
This site is itself an example of the operator-centric, systems-directed approach documented in the work above.