AruneshDwivedi
Infrastructure that scales, recovers, and documents itself.
1+ years running production infrastructure, from provisioning and incident response to automation. I also build tooling that ships fixes into open-source Kubernetes projects: 28 pull requests merged so far.
I make operations boring, on purpose.
I'm a DevOps and Platform Engineer at Ole Solutions, where I run client infrastructure on Yandex Cloud: provisioning, access control, DNS and firewall configuration, deployment validation and live incident response.
Alongside that, I built an automation pipeline that finds bugs in open-source infrastructure tools, drafts Go fixes, and submits them upstream only after human review. Most fixes turn silent failures and panics into clear, actionable errors.
I hold an M.S. in AI & Cloud Computing and a B.Tech in Computer Science & IT from Lobachevsky State University (top 10% of class in both), and I write about cloud and DevOps fundamentals on Hashnode.
Technical stack
Grouped by what I use them for. Everything listed has been used in a project or in production on this page.
☁ Cloud (AWS)
Architecture and operations
🛠 Infrastructure as Code
Reusable, reviewable infrastructure
⎈ Containers & Orchestration
Packaging, scheduling, scaling
⚙ CI/CD
From commit to verified release
📈 Observability
Know before users do
⌨ Languages & Systems
Automation and the OS beneath it
Production-minded work
Open any card for the architecture diagram, what was built, the stack, and links. Filter by area below.
Across 25+ production infrastructure projects. Every submission is human-reviewed and AI assistance is disclosed.
An anti-affinity nil-check removed a panic that halted progressive delivery.
Fixed logic that mishandled already-deleted pods, unblocking safe restarts for stateful workloads.
Cluster-secret listing now paginates instead of silently truncating.
Silent failures and panics become structured, actionable errors.
Work history
- Built Bash and Python automation for provisioning, deployment and health checks, replacing manual runbook steps and cutting hands-on effort per release.
- Administered client infrastructure on Yandex Cloud: server provisioning, SSH key and sudo access control, deployment validation, DNS, firewall and routing.
- Ran incident response on live client systems: triage, root-cause analysis via systemd state and journald/syslog, remediation and post-incident write-ups.
- Hardened access policies and service configuration at the start of each engagement, and wrote the runbooks that made recurring fixes repeatable.
- Built backend features in Python on a distributed Agile team.
- Containerised dev environments with Docker and automated local setup with shell scripting.
- Diagnosed application issues through debugging, log analysis and environment validation.
Engineering notes
What I learn while running infrastructure and contributing upstream. Click a post to read it without leaving the page.
Let's build something reliable.
I'm looking for remote DevOps, SRE, Platform and Cloud Engineering roles, especially on teams that value automation and reliability. Send a message and I'll reply by email.