DevOps Engineer 2

An Platform Engineer \- Infrastructure builds and operates the foundational platform that product engineering teams rely on — including internal developer tools, automation systems, abstraction layers, and resilient infrastructure.

InfraPlatform engineers work as software engineers for infrastructure, focusing on scale, reliability, developer productivity and cost efficiency.

They design internal tools and services that improve developer experience, automate infrastructure lifecycle, enforce security/compliance, and maintain high availability and performance across cloud environments.

### **✅ Core Responsibilities (Expanded)**

### **1\. Build \& Maintain Internal Developer Tools (Dev Productivity)**

InfraPlatform engineers create tooling that empowers 250\+ developers to move faster with less friction:

• In\-house debugging or triage tools
• Self\-service portals for infrastructure, logs, metrics, access
• Secrets management abstractions

These tools reduce friction, enforce standards, and boost developer velocity.

### **2\. Platform Reliability, Uptime \& Resilience Engineering**

InfraPlatform engineers think like SREs but build systems, not dashboards.

They are responsible for

• Designing highly available systems (multi\-AZ, multi\-region)
• Automated failover, health checking, circuit breaking
• SLOs, error budgets, reliability KPIs
• Observability architecture (metrics, logs, tracing, profiling)
• Scaling infrastructure through automation (autoscalers, KEDA, controllers)
• Continuous chaos testing in staging
• Policy\-as\-code to enforce guardrails

Goal: platform downtime should not exceed the company SLO.

### **3\. Infrastructure as Code — Modules, Libraries \& Abstractions**

InfraPlatform treats infra as a software product

• Write Terraform/Pulumi/OpenTofu modules for teams to reuse
• Build opinionated abstractions (e.g., “standard service” module)
• Write Kubernetes operators/controllers to automate infra
• Maintain GitOps pipelines (ArgoCD/Github)
• Multi\-account orchestration, permissions boundary management

Goal: infra provisioning becomes predictable, fast, error\-free.

### **4\. Internal Platform Services (Control planes \& APIs)**

Platform engineers create internal services that orchestrate entire workflows:

• Deployment orchestration service
• Resource orchestration control plane (namespace creation, quotas, IAM, networking)
• Internal service discovery
• Audit/Access management tooling
• Environment\-as\-a\-Service API

These are custom\-built services, not manual scripts.

### **5\. Observability, Diagnostics \& Production Tooling**

Ensure engineers get first\-class troubleshooting tools

• Unified logs, metrics, traces ingestion pipeline
• Debugging utilities (e.g., "log stream" CLI, distributed trace browser)
• Stateful dashboards for performance \& cost hotspots
• Anomaly detection for infra issues
• Postmortem automation

Goal: reduce MTTR drastically.

### **6\. Cost Efficiency \& Infrastructure Optimization**

Key responsibility in fintech

• Design cost\-efficient scaling policies
• Write analyzers/checkers to detect expensive patterns
• Automate cost guardrails (e.g., TTL for resources, cleanup pipelines)
• Build dashboards (VM, S3, CloudWatch, EKS) with optimizations
• Drive “zero waste infra” initiatives

Goal: reduce infra costs aggressively without impacting reliability.

### **7\. Security, Governance \& Compliance Automation**

Platform engineers own

• IAM automation and least\-privilege patterns
• Secrets \& key rotation automation
• Enforcement of standards using OPA / Gatekeeper / SCPs
• Vulnerability scanning pipelines
• Infrastructure compliance (PCI DSS, SOC2\) baked into workflows

Goal: compliance is automatic, not a manual activity.