Lucas Pires Simão

DevOps Engineer, Cloud Architect and Infrastructure Specialist

I design and operate cloud infrastructure for environments where resilience, delivery quality, observability and security are not optional. My work sits at the intersection of DevOps, platform engineering, cloud architecture and practical business execution.

Over the last decade, I have worked across high-availability systems, PCI-sensitive operations, Kubernetes and AWS platforms, CI/CD modernization, runtime hardening, incident response and internal automation. I care about systems that stay understandable under pressure.

10+ years in infrastructure and cloud operations
Hands-on across AWS, Kubernetes, Terraform and delivery systems
Experience in critical environments, compliance-heavy contexts and global infrastructure
Strong builder profile across internal tooling, AI automation and technical platforms

A personal site should explain how someone thinks, not only what they ship.

The part of engineering I care about most is building systems that remain operable under pressure. That usually means making delivery more predictable, infrastructure easier to reason about, incidents faster to understand and teams less dependent on tribal knowledge.

I prefer systems over isolated fixes

I am usually less interested in solving one incident than in removing the class of failure behind it. That means better delivery primitives, clearer observability, stronger defaults and less hidden operational knowledge.

Reliability is an engineering choice

Availability, rollback quality, incident recovery and performance behavior are all design decisions. The goal is not only uptime, but operational confidence.

Automation should reduce cognitive load

Good automation is not there just to save minutes. It reduces ambiguity, sharp edges and the amount of context a team needs to operate safely.

Security needs runtime realism

I have worked in PCI-oriented and security-sensitive environments, so I tend to think about controls in terms of how they behave in real delivery and runtime conditions, not only in policy documents.

Selected experience

These roles are presented the way I believe senior engineering work should be presented: through context, impact and engineering posture, not keyword-heavy task descriptions.

Recent

QikServe

Senior DevOps / Platform Engineering

Platform-oriented infrastructure work with emphasis on reliability, cloud operations and delivery maturity in production-critical systems.

Improved engineering leverage through stronger platform patterns and more predictable infrastructure behavior.

Worked close to runtime reliability, operational clarity and sustainable delivery velocity.

Contributed with a systems mindset rather than treating operational issues as one-off tasks.

Growth-stage operations

Hyperlocal

Cloud / DevOps Engineer

Cloud and automation work focused on scalable delivery, containerized workloads and production visibility.

Balanced speed of change with resilience, maintainability and cost awareness.

Strengthened infrastructure workflows around provisioning, deployment and operational feedback loops.

Helped shape environments that could evolve without accumulating hidden operational drag.

Modernization

Worc

Infrastructure / DevOps Engineer

Infrastructure standardization and DevOps enablement with a strong focus on repeatability and lower team friction.

Turned fragmented infrastructure work into more reproducible systems.

Supported teams through better tooling, automation and operational ownership.

Applied DevOps culture in a practical way, through engineering systems rather than slogans.

Payments and compliance-sensitive environment

Quero2Pay

DevOps / Security-Focused Infrastructure

Infrastructure engineering in a context shaped by PCI DSS, cloud security, runtime protection and business-critical reliability.

Worked in environments where delivery and security had to coexist cleanly.

Supported architecture and operations across cloud, edge protection and production robustness.

Handled infrastructure as a business-critical capability with direct operational consequences.

Areas I work across

This is intentionally grouped as a personal practice area rather than a skill chart. The point is to show range without making the site read like a software catalog.

AWSKubernetes / EKSECSTerraformCI/CDJenkinsAzure DevOpsCloudflareDatadogDockerLinuxPythonBashPostgreSQL / MySQLWAFPCI DSSObservabilityIncident ResponsePlatform EngineeringAI Automation

Projects and systems I like to build

Outside of company roles, I tend to gravitate toward tooling, automation, documentation systems, AI for operations and small products where infrastructure thinking actually matters.

Internal tooling

Infrastructure documentation systems

I build systems that turn cloud and platform sprawl into usable operational documentation. The goal is not static documentation, but faster diagnosis, clearer ownership and more reliable change management.

PythonCloud APIsAutomationDocumentation
View project

AI + operations

AI-powered infrastructure assistants

I am interested in assistants that work with real infrastructure context and useful execution boundaries, especially for diagnosis, operational workflows and internal engineering support.

AIInfrastructure contextToolingAutomation
View project

Product + infrastructure

Audio transcription platform

A builder-style project that combines application delivery, backend operations and practical product thinking. It reflects how I like to work when product and infrastructure are tightly connected.

FastAPIDockerPostgreSQLOpenAI
View project

Security utility

Secure one-time sharing tooling

A small but useful example of applying infrastructure and security thinking to a focused product problem, with attention to minimal operational surface area and safe default behavior.

DockerSecurityDeploymentCloud hosting
View project

I also want this site to become a place for technical writing.

The long-term direction is to publish notes, deep dives, postmortems and practical pieces about infrastructure, cloud architecture, observability and AI-assisted operations.

What high-availability infrastructure work actually looks like in practice

Kubernetes operations after provisioning: where complexity really starts

Observability as an operational decision system, not a dashboard collection

Cloudflare, edge protection and runtime security tradeoffs

Platform engineering for teams that need less friction, not more abstraction

Using AI where it genuinely helps infrastructure work

Certifications

PCI Internal Security Assessor (ISA)

Payment Card Industry Professional (PCIP)

AWS Monitoring and Reporting

DevOps & Agile Culture

Profissional DevOps

Background

MBA in Cyber Security, Forensics, Ethical Hacking and DevSecOps

Technologist in Systems Analysis and Development

Get in touch with me.

If you want to talk about infrastructure, cloud architecture, automation, observability or technical projects, feel free to reach out.