Playbook
Infrastructure that guides an organization is different from infrastructure that describes it.
Six-plus years of owning a cloud estate through company hypergrowth taught one consistent lesson: the difference between infrastructure that scales and infrastructure that breaks under growth is whether it was designed as organizational guidance or just operational description. The playbook is built around designing foundations before they are urgently needed, building modules that encode decisions rather than just resources, and migrating live estates with architectural thinking before execution begins.
How I lead
Own the estate, don't just operate it
Ownership includes the architecture, the cost, the security posture, the migration roadmap, and the standards that every team building on the estate depends on.
Build foundations before they are urgently needed
Account foundations, module standards, and vending machines exist at EarnIn because they were designed ahead of the scale that required them — not retrofitted after.
Cross-functional trust is earned by consistent delivery
Security, SRE, IT, and M&A include her in projects from the start because she delivers to tight deadlines with tailored solutions rather than generic ones.
Architecture thinking before execution planning
Whether it's a Scalr migration or an EKS networking design, the architecture is proven in PoC before the team is asked to execute at scale.
Meet engineers where they already work
The platform's job is to reduce friction, not add process. As engineering workflows moved into AI coding agents, the platform followed — building Claude and Cursor skills so standards are available inside the tools people actually use, not just in a wiki nobody reads.
How I think about architecture
Build the account foundation before the org needs it at scale — governance debt is expensive to pay down during hypergrowth
↗ AWS Account FoundationsInfrastructure as code that requires tribal knowledge to use is just well-formatted YAML
↗ IaC EstateCloud spend is an engineering problem — own it with the same rigor as uptime
↗ EarnIn ScaleMigrate a live estate without downtime by designing the migration before executing it
↗ Scalr MigrationInfrastructure literacy shouldn't live only in the platform team's heads — teach it, don't gatekeep it
↗ Terraform ChampionsTechnical domains
Infrastructure as Code
Designs, owns, and evolves an 85,000-line Terraform estate spanning AWS (the vast majority), Cloudflare, Databricks, Confluent, Datadog, and additional providers — 75+ modules built to guide org-wide infrastructure patterns.
AWS Architecture & Account Engineering
Architects and leads AWS Account Foundations and the Account Vending Machine — the organizational layer that defines how accounts are provisioned, secured, and governed at scale, wired end-to-end with zero-trust network access and DNS architecture rather than bolted on after the fact. Lead engineer for EKS Vending Machine Networking.
Platform Engineering & DevOps
Expands EarnIn's platform engineering capability across CI/CD, developer experience, site reliability, and Kubernetes — bridging infrastructure ownership with the tooling that engineering teams interact with daily.
Cloud Cost & Operations Management
Owns the multi-million dollar cloud cost estate — managing, optimizing, and attributing cloud spend across a 1,000-person engineering organization with accountability for cost efficiency and infrastructure right-sizing.
Platform Enablement & Cross-Functional Representation
Represents platform, security, SRE, IT, and compliance whenever a business unit's request touches cloud architecture, networking, security, or RBAC — and is leading the shift from a reactive service-desk infrastructure model to platform-as-a-product, including founding a Terraform Champions program and building the Claude and Cursor coding-agent skills that carry the platform into the AI-native era.
Core strengths
- Architect IaC estates that guide an org's infrastructure patterns rather than just describing current state — 75+ modules that encode decisions, not just resources
- Represent platform, security, SRE, IT, and compliance in the same conversation when a business unit's request touches cloud architecture — translating five sets of concerns into one coherent answer instead of five separate reviews
- Migrate live infrastructure estates without downtime — the Scalr migration is architected before it is executed
- Translate cloud cost complexity into accountable, action-oriented infrastructure decisions at the organization level
- Move a platform from ticket queue to product — teaching infrastructure literacy through the Terraform Champions program instead of gatekeeping it, and extending platform standards into the AI coding agents engineers already use
Operating constraints I hold myself to
Certifications & education
Certifications
AWS Certified Solutions Architect – Associate
AWS architecture design — compute, storage, networking, security, cost optimization
AWS Certified Developer – Associate
AWS service integration, deployment patterns, and application development
Splunk Certified User 6.x
Log analysis, observability dashboards, capacity monitoring
Education
M.S. Computer Science — University of Nebraska at Omaha, NE
B.E. / B.Tech — Computer Science (India)
Now you know how I think.
Next: Let's connect→