---
title: "Amit Malhotra (@vertro-io) | Hashnode"
description: "Founder, Buoyant Cloud & Vertro. Read the latest articles by Amit Malhotra on Hashnode."
url: "https://hashnode.com/@vertro-io"
---

@vertro-io

# Amit Malhotra

@vertro-io · Toronto, Canada · Joined July 2026

Founder, Buoyant Cloud & Vertro

## Comments

[Absolutely agree. AI is changing the engineer’s job, but I don’t think it makes engineering less important — it makes engineering judgment more important. When AI can generate code quickly, the differentiators become understanding the problem, making the right architectural decisions, validating what AI produces, and knowing how that code should safely run in production. The interesting shift is from “writing code” to “designing and governing systems.” That’s also where good platform engineering becomes increasingly important. AI can accelerate development, but the platform provides the guardrails that help turn that speed into reliable software.](https://hashnode.com/posts/when-ai-writes-the-code-what-is-the-engineer-s-job/6a99ac8cc4c7dc234d7ecb89/comment/6a9a5625d58d281fbc804001)

Comment · Article · Sep 4 · 1 · [When AI Writes the Code, What Is the Engineer's Job?](https://hashnode.com/posts/when-ai-writes-the-code-what-is-the-engineer-s-job/6a99ac8cc4c7dc234d7ecb89)

[Exactly. The “enabled by default” part is what makes this approach really scalable. And I think there's another benefit: once telemetry is standardized at the platform level, teams can spend their time interpreting the signals rather than figuring out how to generate them. That shift—from instrumentation as a team responsibility to observability as a platform capability—is where the real leverage comes in.](https://hashnode.com/posts/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file/6a771f53e42cf22dee8376a1/comment/6a7bf836ad2d3766418d40d8#reply-6a8304ff0ead75fc196270a6)

Reply · Article · Aug 17 · 1 · [Distributed Tracing for CI Pipelines Without Touching a Single Workflow File](https://hashnode.com/posts/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file/6a771f53e42cf22dee8376a1)

[This is a great example of where platform-level instrumentation can remove a lot of friction from engineering teams. Getting end-to-end visibility across CI pipelines without asking every team to modify and maintain workflow files is a much more scalable approach. The real value is making observability part of the platform rather than another responsibility for individual developers.](https://hashnode.com/posts/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file/6a771f53e42cf22dee8376a1/comment/6a7bf836ad2d3766418d40d8)

Comment · Article · Aug 12 · 1 · [Distributed Tracing for CI Pipelines Without Touching a Single Workflow File](https://hashnode.com/posts/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file/6a771f53e42cf22dee8376a1)

[Well said. “The deployment decision preceded the cost model” is probably the line that stood out most to me. We're seeing a familiar pattern from the early cloud era playing out with AI: teams optimize for capability first, then try to understand consumption after the system is already running at scale. The interesting part is that the solution isn't necessarily using cheaper models. It's building the architecture to match the right level of intelligence to the right task. Routing, caching, cost attribution, governance and observability need to become part of the platform—not decisions every engineer has to make independently. AI consumption isn't the problem. Unmanaged consumption is The organizations that build that orchestration layer early will have a very different cost curve as agentic workloads scale.](https://hashnode.com/posts/the-meter-is-running-nobody-built-the-architecture-to-stop-it/6a790531ea33739e7776c88c/comment/6a793f30dced96ee8c6f41e0)

Comment · Article · Aug 10 · [The Meter Is Running. Nobody Built the Architecture to Stop It.](https://hashnode.com/posts/the-meter-is-running-nobody-built-the-architecture-to-stop-it/6a790531ea33739e7776c88c)

[This is one of those Kubernetes topics that's easy to underestimate. One thing I've seen repeatedly is that many teams assume namespaces provide meaningful isolation, when in reality they're often just an organizational boundary. The real blast radius is determined by the combination of NetworkPolicies, RBAC, service accounts, admission controls, and workload identity—not namespaces alone. Security by default should be about reducing the reachable surface, not just segmenting resources. A timely reminder that Kubernetes defaults are designed for flexibility, not least privilege.](https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71/comment/6a6ac92e75fce62ae42fee0e)

Comment · Article · Jul 30 · 1 · [Anything can talk to anything: the Kubernetes default quietly expanding your blast radius](https://hashnode.com/posts/anything-can-talk-to-anything-the-kubernetes-default-quietly-expanding-your-blast-radius/6a6a7661d589bd8a6fdb7e71)