Xavier G. Lopez

• Clarify what the platform owns, what teams own, and what has to be expressed through contracts, policies, workflows, or operating rules.
• Turn vague infrastructure needs into boundaries workload teams and platform operators can reason about.

• Implement the delivery, identity, runtime, network, telemetry, trust, and policy pieces that translate the platform model into predictable, supportable paths for workload teams and platform operators.
• Prefer platform-owned paths that reduce one-off decisions without blocking useful team autonomy.

• Use runtime behavior, logs, telemetry, GitOps state, Terraform state, identity configuration, and failed handoffs to understand what the platform is actually doing.
• Trace failures across layers instead of stopping at the first component showing an error.

• Convert incidents, blocked workflows, and ambiguous ownership into better docs, clearer controls, safer defaults, and more explicit operating paths.
• The platform improves when repeated confusion becomes a better interface.

Independent platform practice

• Building and refining a multi-workload reference platform where workload contracts declare intent and shared platform paths handle validation, build, promotion, runtime state, and governance.
• Writing and maintaining the operating doctrine so repository boundaries, lifecycle rules, diagnostics, enforcement, and pull-request behavior are explicit instead of tribal.
• Moving delivery mechanics into platform-owned workflows so workload repositories inherit the path instead of rebuilding it each time.
• Treating tenant data boundaries, GitOps state, identity, and telemetry as part of the platform design, not cleanup work after deployment.
• Using agent-assisted workflows for documentation, triage, code generation, and automation planning with reviewable human/agent attribution boundaries.
• Keeping the platform in formation phase: clarifying the contract surface, tightening the operating model, and making the supported path easier to consume over time.

Platform Engineer · Federal Defense Program

• Contain platform entropy by making control-plane behavior more legible, maintainable, and supportable across cluster state, identity, network boundaries, policy controls, and cloud-broker access paths.
• Own AWS Security Hub remediation paths by separating team-owned findings from managed baseline controls and driving remediation, suppression, or escalation through supportable ownership paths.
• Work with cloud-broker teams and vendor support to turn access, certificate-trust, RBAC, and network-inspection requirements into deployable Kubernetes configuration, secrets, documented steps, and Flux GitOps scaffolding for the stabilized path.
• Own the nested GovCloud platform path from AWS account infrastructure to EKS to Spectro Palette Vertex to Domino Data Lab, where each layer becomes the control surface for the next layer of self-hosted AI/ML training operations.
• Coordinate vendor support and product engineering to resolve blockers across deployment artifacts, manifests, RBAC, values files, scripts, private ECR/S3 paths, and cloud-broker constraints.
• Lead Bedrock Mantle service development for GovCloud model inference and daily team development use through Terraform provisioning, provider/model/agent configuration, cost awareness, documentation, and operational handoffs.

Senior Platform / DevSecOps Engineer · Reston, VA

• Contributed to platform architecture for DoD ATO’d environments supporting internal engineering teams and tenant workloads.
• Rebuilt AMI workflows around AWS Image Builder so remediation became part of the image lifecycle instead of a separate cleanup path.
• Built an external-image approval pipeline with vulnerability scanning, cybersecurity review routing, internal registry promotion, audit-friendly handoffs, and notifications.
• Led rootless build migration from Kaniko to Buildah and designed Terraform module boundaries and CI policy gates.

Configuration Management / Automation Consultant · Independent Consultant

• Translated legacy Chef configuration workflows into structured Ansible roles and playbooks for repeatable infrastructure operations.
• Standardized inventory layering, service-state management, validation, and idempotence checks.

Platform Lead / DevOps Engineer / SRE · Chandler, AZ

• Led the organization’s Kubernetes strategy from research and decision framing through bare-metal and hybrid-cloud EKS delivery.
• Built the team’s first CI/CD pipelines and Kubernetes deployments, moving release work out of manual operations and into a repeatable delivery path.
• Improved cloud cost profile through migration strategy, rightsizing, and operational cleanup.

Juniper Networks · Datalink · DST

• Delivered network automation and customer training, introduced DevOps and configuration-management practices across .NET and Rails stacks, and began in data extraction and transformation workflows.

California State University, San Bernardino, CA

Active

Active