Consultancy - How I Can Help Your Teams
CI/CD & release automation
- I build pipelines that fit your team: build, test, security checks and deploy. Think GitHub Actions, GitLab CI or Jenkins, and GitOps with Argo CD or Flux.
- Goal: Less manual work, faster feedback, and a release process you can trust.
Kubernetes & Platform Engineering
- From first cluster to production platform: architecture, networking, RBAC and policies (like Pod Security and network policies). I also help with Helm/Kustomize, autoscaling, and building an internal developer platform so engineers can work independently.
- Goal: Self-service, faster feedback, and a reliable release process.
Observability & Reliability (SRE)
- I set up monitoring, logging and alerting (e.g., Prometheus, Grafana, Loki/ELK) and help with runbooks and incident practices.
- Goal: Faster root cause analysis and fewer recurring fires.
Cloud & Infrastructure as Code
- On AWS, GCP or on-prem: I help migrate, standardize and manage with IaC (Terraform/Ansible).
- Goal: Cost control, secure access, and a setup that stays reproducible and extensible.
Am I a Fit for Your Organization?
Signs this would be a good fit:
- You want structural improvements (not just quick patches).
- Your team is open to better ways of working and I can collaborate closely with them.
- You're building a platform that needs to scale and you want to lay a solid foundation now.
- You want a pragmatic expert who can think strategically and also build.
- Quality, collaboration and calm operations matter more than the lowest price.
Signs this will not work out:
- You primarily need a feature developer (my focus is platform, infrastructure and delivery).
- You expect a large consultancy team — you work with me as an independent consultant embedded in your team.
- You don't want to involve your team in change or handover.
- You only want a quick emergency fix without addressing root causes.
Frequently Asked Questions
What's the scope of a DevOps engagement?
It depends on your situation. Sometimes it's one concrete issue (e.g., unstable deployments); sometimes it's a broader track (CI/CD + infrastructure + observability). I often start with a short assessment and quick wins, then we align on scope. I always make it explicit: what we do, what we don't, and what the outcome is.
How do we collaborate and communicate?
I prefer working embedded with your team: short lines, transparent, no surprises. Typically that means a kickoff, weekly updates, and coordination in your tools (Slack/Teams/Jira). You can always see what I'm doing and why.
How do you handle security and access to our systems?
Security is a baseline requirement. I work with least privilege, separate accounts where possible, and temporary access when feasible. I don't share secrets via email or chat; we use a password manager or a secret store. I document changes so you can always audit what happened.
What happens after the project ends?
My goal is for your team to run independently. I deliver documentation, do a handover (and training if needed), and make sure knowledge doesn't live only in my head. If you want, I can stay available for periodic health checks or on-demand support.
What about rates and budget control?
I work at a market-rate senior freelance rate. Upfront we align on scope, priorities and communication so you stay in control of costs. That can be hour/day based, and for well-scoped work also fixed price. If budget is a hard constraint, we adjust scope accordingly.
Reviews
A. J. Wright
Staff Architect
Les is one of the most technically skilled engineers I've worked with. He's motivated, skilled, and technically strategic. He works hard to provide quality services above and beyond what is asked of him.
Mike Stanley
IT Manager, Platform Services
Les is one of the most impressive IT professionals I've ever known. He is constantly looking for ways to improve his knowledge and skills, and the systems he maintains are rock solid.