>_ Spikkies IT
Automation Engineer • Ansible • Terraform • Python

Automation Engineer

Contact View projects

Infrastructure as Code

I convert manual infrastructure steps into reproducible Terraform modules, clear variables, safe defaults, and repeatable deployment flows.

Configuration automation

With Ansible I automate servers, services, packages, secrets handling, updates, and operational tasks so environments stay predictable.

Python tooling

I build Python scripts, CLI tools, and integrations that replace boring or error-prone steps with controlled, testable workflows.

K

Small steps

I prefer small, reviewable improvements over large unclear changes.

V

Verify

Every change should have a test, release log, or operator proof showing what really works.

R

Rollback path

Automation should also document a safe way back when behavior is not what was expected.

Automation profile

From manual work to manageable systems

My focus is practical automation: less clicking, less configuration drift, faster deployments, better observability, and clear runbooks for operations.

$ automation stack --profile spikkie
ROLE                     Automation Engineer
PRIMARY_TOOLS            Ansible, Terraform, Python
RUNTIME                  Linux, Docker, Kubernetes
FOCUS                    Infrastructure as Code, CI/CD, GitOps, ops tooling
OUTPUT                   scripts, playbooks, modules, runbooks, working systems

$ principle
→ automate carefully, verify everything, document the path back
A

Ansible

Playbooks, roles, inventory structure, server provisioning, service configuration, idempotent management flows, and safe execution.

T

Terraform

Infrastructure as Code, module structure, state risks, environment separation, reviewable changes, and reproducible cloud/on-prem provisioning.

P

Python

Automation scripts, API integrations, data validation, command-line tools, deployment helpers, and glue code between systems.

1

From request to plan

I make scope, constraints, and the rollback agreement explicit before changing automation.

2

From script to operable flow

Scripts, playbooks, and modules get clear inputs, dry-run behavior, and logging operators can follow.

3

From release to proof

Each delivery belongs with visible control: tests, release output, operator evidence, and a clean continuation path.

C

Share context

Share briefly what is manual, fragile, or unclear today so the first step stays small and focused.

N

Choose the safe next step

We choose a bounded improvement with clear constraints, test evidence, and a rollback path.

P

Agree on proof

Every delivery gets visible proof: output, log, test, runbook, or operator check that can be repeated later.

Infrastructure as Code (IaC)
Continuous Integration / Continuous Delivery (CI/CD)
GitOps & Deployment Automation
Platform Engineering
Configuration Management
Cloud-native Automation
Kubernetes Operations
Linux Infrastructure Automation
Observability & Monitoring