17+ years in IT
A path from software development and testing, through systems architecture, to leading Platform Engineering teams.
AWS · Kubernetes · Platform Engineering
I design and build AWS and Kubernetes platforms that scale with your business — reliable, secure and cost-efficient.
Experience
I don't learn on your infrastructure. The problems I solve are problems I have run production systems through.
A path from software development and testing, through systems architecture, to leading Platform Engineering teams.
I design for systems serving real business traffic — not for documentation or slide decks.
Software houses, SaaS, scale-ups and enterprises. I know the platform problems of companies at every stage.
Amazon EKS, Terraform, GitOps and observability are tools I have used in production for years — not just studied for certifications.
About
Over 17 years of working with production systems taught me one thing: the best architecture is the one a team can maintain for years. That is why I design solutions that are simple, automated and ready for real traffic.
I combine three perspectives: an engineer who ships the work, an architect who sees the whole system, and a leader who knows how to transfer knowledge to a team. When the engagement ends, you are left with a platform your team understands and can evolve.
In practice this means: shorter commit-to-production cycles, fewer incidents that wake people up at night, a predictable cloud bill, and infrastructure that can be rebuilt in hours, not weeks.
How I help
I don't sell DevOps hours. I deliver solutions that let teams ship products faster and more safely.
Your infrastructure grew organically and nobody remembers why it looks the way it does.
I design architecture matched to your product’s scale and roadmap — with account structure, networking and security built in from day one.
Product teams spend their time on operational toil instead of building the product.
I build internal developer platforms that shorten the path from commit to production and take operational work off product teams.
The cluster works, but nobody wants to touch it. Scaling and upgrades are a risk every single time.
I design, deploy and evolve Kubernetes clusters — from autoscaling with Karpenter, through Helm and ArgoCD, to multi-environment strategies.
Infrastructure is created by hand in the console. Rebuilding an environment borders on a miracle.
All infrastructure defined in Terraform or OpenTofu — reproducible, versioned and ready for disaster recovery.
Deployments take hours, require manual steps and always happen “after hours”.
I design GitLab CI/CD and GitHub Actions pipelines that cut deployment time to minutes and eliminate manual operations.
The move to AWS keeps getting postponed because nobody can assess the risk.
I plan and run migrations in stages: dependency analysis, prioritization, rollback plans. No downtime, no surprises.
Your cloud bill grows faster than your revenue.
I analyze spend and implement changes that lower costs without degrading performance or reliability — from right-sizing to purchasing strategy.
You learn about outages from your customers.
I implement monitoring, logging and alerting built on Prometheus, Grafana and ELK — so you detect problems before your users do.
You need an independent assessment of architecture, security or DevOps processes.
I run the audit and deliver a prioritized list — with effort and impact estimates for each change. Not a hundred-page report.
Your DevOps team needs support — or a leader while the platform is being built.
I mentor DevOps and Platform Engineering teams and step in as an interim leader — until the team reaches full independence.
Engagements start at 400 PLN net / hour.
Technologies
Technology is a means, not an end. I pick the stack for the problem — but these areas I know from years of production practice.
Why WebMind
Experience earned on production environments — where an architectural mistake costs real money.
I design and I deliver. My recommendations end with working infrastructure, not a presentation.
All infrastructure in code: reproducible, auditable and recoverable after a failure.
Security is part of the architecture from day one — not a phase bolted on at the end.
I design with the cloud bill in mind. Performance and reliability without overpaying.
The goal is not to make you dependent on me. I stay until your team reaches full independence.
How we work together
One hour. We discuss your situation and goals. We check whether I can genuinely help — if not, I will say so.
I review architecture, costs and processes. I identify risks, bottlenecks and quick wins.
You get concrete recommendations with priorities, estimated effort and the expected impact of each change.
I deliver the changes independently or together with your team — with automation, testing and documentation living in code.
I train the team, tidy up the documentation and stay available as a partner for the next stages of your platform.
FAQ
It is a free one-hour conversation. I ask about your architecture, team and business goals. If I decide I am not the right person for your problem, I will say so — and point you in a better direction if I can.
I prefer working on-site, especially at the start of a project — that is when I learn the system, the team and the context fastest. I live in Wrocław, but I will travel when the project requires it. Later on I work hybrid or remotely, with regular communication and full transparency on progress.
Anything from a single audit or a few days of consulting to a multi-month collaboration. The scope always matches the real need — I don’t sell engagement you don’t need.
Yes, that is standard. Before I get access to any documentation, code or infrastructure, we sign a non-disclosure agreement.
Both models. I can take full ownership of a topic and deliver a finished solution, or work side by side with your engineers. Companies that want to ship changes and upskill the team at the same time usually choose the latter.
Usually one to two weeks, depending on the scale of the environment and availability of documentation. It ends with a workshop where I walk your team through the findings and recommendations.
Hourly or for a defined scope, depending on the nature of the project. Engagements start at 400 PLN net per hour. I always present an effort estimate before we start.
Yes. Over 17+ years I have worked with organizations of all sizes — from startups to enterprises. I understand both the dynamics of small teams and the processes and security requirements of large companies.
The principles of designing reliable platforms are universal. If your stack falls outside my core areas, I will say so on the first call and assess whether I can help before proposing anything.
I take on the platform leadership role for a defined period — e.g. while building a platform from scratch, during a reorganization or while you hire a permanent leader. I step out when the team is ready to run independently.
Yes. I work with DevOps and Platform Engineering teams — from architecture reviews and pair work to a competency development program matched to the team’s level.
It depends on current project load — usually within one to two weeks. Urgent situations, like incidents or audits ahead of major decisions, get priority.
A free one-hour call. No obligations — with a straight assessment of whether and how I can help.
Book a free consultationContact