What I can help with
My work sits where application delivery meets operating systems and infrastructure. That includes building a deployment path, cleaning up an unreliable one, or diagnosing why an application behaves differently across environments. The objective is usually straightforward: fewer undocumented steps, clearer failure modes, and a system another engineer can operate without reverse-engineering it under pressure.
- CI/CD pipeline design, cleanup, and reusable GitLab CI/CD or Jenkins automation
- Ansible automation for installation, configuration, upgrades, and environment provisioning
- RHEL and Linux application deployments, including Java platforms such as WildFly
- Kubernetes and OpenShift deployment workflows using containers, Helm, and platform-native configuration
- Docker, Podman, and OCI container build or runtime workflows
- Prometheus, Grafana, and centralized logging for useful operational visibility
- TLS, certificates, truststores, networking, and service-connectivity troubleshooting
- Small infrastructure tools and operational automation in Go, Bash, or Python
How I approach an engagement
I start with the system as it exists: its constraints, deployment path, ownership boundaries, and the evidence available when it fails. That matters in enterprise environments, where a technically elegant answer may still be wrong if it ignores restricted networks, security controls, established change processes, or the people who need to operate it afterward.
The work should leave something concrete behind. Depending on the engagement, that might be an Ansible role, a reviewed pipeline, a deployment runbook, a monitoring integration, a reproducible diagnosis, or an implementation plan that separates urgent fixes from longer-term platform work. I avoid adding machinery merely to make a solution look sophisticated.
$ cat engagement-principles understand the failure path make the change repeatable keep operational ownership clear document what the next engineer needs
Engagements that fit
I am best suited to focused technical work with a clear infrastructure, deployment, or reliability problem. Typical formats include short troubleshooting engagements, CI/CD and automation reviews, implementation projects, environment-standardization work, and incident assistance where a team needs another experienced pair of eyes.
Remote EU, B2B, and contract arrangements are the natural fit. I do not present myself as a full-service agency, and I will say so if a request needs a larger delivery team or expertise outside my working scope. Employer systems, customer details, and confidential infrastructure are never used as portfolio material.
A bounded place to start
A CI/CD and deployment reliability review is a practical entry engagement for teams that know their release path is fragile but do not yet need a broad platform project. The input is an existing pipeline, deployment configuration, and a short description of current failure modes.
The deliverable is a focused technical review: prioritized findings, immediate reliability and security risks, duplicated or hidden environment logic, missing verification and rollback controls, and a concrete improvement sequence. The same format can be adapted to an Ansible repository or a defined production troubleshooting session.
Relevant engineering background
I currently work as a Systems and Integration Engineer at Amphinicy d.o.o. in Zagreb, building on previous operations, DevSecOps, and platform engineering roles. My hands-on background includes Linux, Ansible, GitLab CI/CD, Kubernetes, OpenShift, Helm, Docker and Podman, PostgreSQL, Prometheus, Grafana, centralized logging, TLS and certificate work, and production incident response.
That progression—from operating production systems, through platform and security automation, into systems integration—shapes how I work. Delivery tooling is not separate from runtime behavior. A pipeline, application server, database connection, certificate chain, and monitoring path are parts of the same operational system.
I am based in Karlovac and work in Zagreb, Croatia, with remote EU teams through B2B and contract engagements. For public technical examples, read my engineering notes or view my GitHub profile.