Develop independent engineers
Before becoming a lead, I mentored monitoring and SysOps colleagues toward DevOps and automation. Later I gave engineers and Team Leads context, responsibility and support to make decisions independently.
ENGINEERING LEADERSHIP / HANDS-ON DELIVERY
I develop people. We build and own systems.
I develop independent engineering teams and accelerate infrastructure delivery. As an Engineering Manager and hands-on DevOps practitioner, I combine people development with Terraform, automation, debugging and technical decisions.
Kraków Area, Poland · remote / hybrid · Available immediately

Engineering area growth; two Team Leads at peak
Selected infrastructure delivery, from ~1 week
At InPost · engineering and people leadership
Selected infrastructure services; area growth includes two Team Leads.
02 / PEOPLE & PRACTICE
Before becoming a lead, I mentored monitoring and SysOps colleagues toward DevOps and automation. Later I gave engineers and Team Leads context, responsibility and support to make decisions independently.
I introduced quarterly in-person team meetings and optional monthly sessions, and supported conference participation and knowledge sharing. These gave the team regular time to reconnect, exchange experience and develop together.
My technical depth helps me understand problems and support engineers. For important decisions, I brought relevant perspectives together to challenge assumptions and compare trade-offs, then reach a decision and own the outcome. New evidence could change the direction.
03 / SELECTED WORK
Engineering work at InPost, followed by a personal game prototype. Each case describes its own scope and contribution.
I helped build GCP foundations: landing-zone architecture, Cloud Foundation Fabric/FastFabric adaptations, Kubernetes and monitoring. I consolidated fragmented infrastructure delivery into automated end-to-end Terraform workflows, reducing selected service delivery from ~1 week to ~1 day.
Problem: Selected infrastructure services took around a week to deliver, with work fragmented across teams.
My contribution: I took responsibility for the delivery flow, wrote and implemented Terraform automation, and connected the steps into end-to-end workflows. This sat within our broader work building GCP foundations, Kubernetes and monitoring.
Result: Selected cluster and infrastructure services could be delivered in around one day. The improvement concerned those workflows, rather than all infrastructure delivery.
I supported an engineer moving from testing into infrastructure, progressively giving him context, autonomy and ownership. He became a key GitOps driver and later a Platform Lead. The engineers owned implementation; I helped them grow into independent technical leadership.
Following an on-site assessment at Mondial Relay, I helped establish an in-house migration path. I led technical work with the team through ~2 months of delivery, combining execution, stakeholder alignment and knowledge transfer.
Context: The migration required both technical delivery and agreement on how teams across organisations would work together.
My contribution: Following an on-site assessment, I helped establish the in-house migration path and led technical work with the team. Stakeholder alignment and knowledge transfer were part of delivery.
Result: The team delivered the migration in approximately two months, combining engineering execution with cross-organisation collaboration.
I supported technical transitions and knowledge transfer with Menzies in Edinburgh and with Yodel. I worked with teams across organisations to understand their systems and operating practices and share infrastructure knowledge.
I contributed migration tooling and workflows with a small internal team, helping turn the approach into a repeatable working process. I also worked directly with GitLab representatives. The migration remains ongoing.
As the engineering area grew to ~30 people, including two Team Leads, my scope covered budget and procurement processes, licences and CAPEX/OPEX tracking. Alongside people leadership, I remained involved in major maintenance and technical escalation.
I built NexOps in Python/Flask to automate infrastructure tasks and provide self-service workflows. Colleagues used working functionality, including tooling supporting parts of the ongoing GitLab migration. The broader platform concept remained unfinished, with use varying by capability. AI accelerated later development.
Built a personal playable web/PWA prototype turning parcel-size education into a simple game. I explored the idea myself out of technical curiosity and an interest in games, combining product experimentation with hands-on development. A personal project, not an InPost production deployment or commercial release.
04 / EXPERIENCE
Staff EngineerPlatform Domain
Engineering ManagerInfrastructure Domain
Team LeadDevOps
DevOps EngineerCloud & infrastructure
System Engineer
System Engineer
IT Specialist
05 / ENGINEERING PRACTICE
I use technical and domain knowledge to understand a problem and build a solution. AI-assisted engineering later helped me develop NexOps functionality faster. I also helped a colleague learn practical Python and HTML development with AI, enabling her to build her own solutions, and shared lessons at Comarch AI Exchange.
06 / SPEAKING
Comarch AI Exchange powered by GitLab
Kraków · 14 September 2026
07 / OUTSIDE WORK
Home Assistant, ESP32, Ubiquiti networking, personal infrastructure, 3D printing and web projects such as rplus.online keep me experimenting. I enjoy understanding how something works, removing the repetitive parts and improving it.
08 / WHAT’S NEXT
If the role combines people leadership with platform, DevOps or infrastructure engineering, let’s talk.
rbadzwol@rplus.online ↗