Portworx Engineer Full Time NEW

About the Role

We’re looking for a battle-tested Portworx Engineer who thrives in complex, production Kubernetes environments. This is a hands-on role — deployment, troubleshooting, performance tuning, and cross-architecture implementation across the most demanding enterprise use cases. You won’t be advising from a distance; you’ll be in the weeds with customers and internal teams, owning outcomes end to end.

What You’ll D

oDeployment & Implementatio

• nDeploy and configure Portworx across diverse environments — bare metal, VMware, AWS, Azure, GCP, and hybrid multi-clou
• dImplement Portworx on Kubernetes distributions including EKS, AKS, GKE, OpenShift, Rancher, and Tanz
• uStand up production-grade storage clusters — replication, encryption at rest and in-flight, CSI integration, StorageClass configuratio
• nExecute day-2 operations: cluster expansion, node replacement, version upgrades, and license managemen
• tIntegrate Portworx with backup solutions (PX-Backup, Velero, Kasten) and disaster recovery framework
• sConfigure and validate PX-Metro DR and AsyncDR topologies for multi-site resilienc

eTroubleshooting & Root Cause Analysi

• sOwn L2/L3 escalations — dig into etcd health, journal logs, kvdb quorum issues, storage pool failures, and network latency problem
• sDiagnose and resolve volume attachment failures, node evictions, PVC pending states, and StatefulSet disruption
• sAnalyze performance bottlenecks: IOPS contention, throughput degradation, latency spikes across storage pool
• sUse px-diag, stork logs, Prometheus/Grafana dashboards, and kernel-level tooling to isolate fault
• sWork directly with Pure Storage support on complex TAC cases — own the thread from open to clos
• eBuild and maintain runbooks, post-mortems, and troubleshooting playbooks from field experienc

eArchitecture & Cross-Platform Engineerin

• gDesign and implement reference architectures across heterogeneous Kubernetes environments — including air-gapped, on-prem, and regulated cloud deployment
• sArchitect storage topologies for stateful workloads including databases (PostgreSQL, Cassandra, Elasticsearch, MongoDB), AI/ML pipelines, and message queues (Kafka
• )Define and enforce storage policies, PodDisruptionBudgets, and volume placement rules aligned to workload SLA
• sEvaluate and implement node labeling strategies, rack-awareness, and failure domain configuration for high-availability cluster
• sParticipate in architecture reviews — flag storage anti-patterns, validate designs pre-deploymen
• tWork across teams (platform, SRE, DevOps) to integrate Portworx into CI/CD pipelines and GitOps workflow

s
What We’re Looking F

orRequir

• ed7+ years in infrastructure, storage, or platform engineering — with direct, hands-on Portworx deployment experien
• ceProduction-proven expertise running Portworx at scale: multi-node clusters, high-availability configurations, and performance-sensitive workloa
• dsDeep Kubernetes internals knowledge — CSI drivers, storage classes, PVCs, StatefulSets, node affinity, taints/toleratio
• nsStrong Linux fundamentals: block storage, filesystems (ext4, xfs), kernel parameters, network stack, and device manageme
• ntExperience with etcd operations — backup, restore, quorum management, and compacti
• onFamiliarity with distributed storage concepts: replication factors, consistency models, data locality, and erasure codi
• ngAbility to read and interpret logs, traces, and metrics across the full Portworx stack without hand-holdi
• ngClear written and verbal communication — you can explain a root cause to an engineer and translate the impact to a platform own

er
Nice to H

• avePortworx certification or demonstrated Pure Storage train
• ingExperience with PX-Backup, PX-DR, or Autopilot for capacity managem
• entHands-on with GPU workloads or AI/ML infrastructure on Kubernetes (shared storage for training pipelines, model servi
• ng)Scripting proficiency in Python, Bash, or Go for automation and tool
• ingExposure to service meshes (Istio, Linkerd) and their interaction with stateful worklo
• adsBackground in regulated environments with compliance requirements (SOC 2, HIPAA, FedRA

MP)
Architectures You’ll Work

• WithThis role spans the full breadth of Portworx deployment patterns across enterprise customers. You should be comfortable across most of the follow
• ing:Single-cluster HA with replication factor 2/3 across failure domains on bare metal and VMware vSp
• hereMulti-cloud active-passive DR using PX-AsyncDR with RPO/RTO requirem
• entsMetro DR (synchronous replication) across stretched Kubernetes clusters in dual-datacenter se
• tupsAir-gapped on-prem deployments with private registries, no-internet etcd, and offline upgr
• adesOpenShift on-prem with ODF/OCS coexistence — migration and parallel operation scena
• riosEKS/AKS managed clusters with Portworx on worker node instance storage (NVMe-bac
• ked)Stateful database clusters: PostgreSQL (Patroni/CloudNativePG), Cassandra, Elasticsearch with Portworx sharedv4 or local vol
• umesKafka on Kubernetes with Portworx local volumes for partition persistence and broker fail
• overGPU node pools for ML training workloads with shared ReadWriteMany volumes and dataset sta
• gingMulti-tenant PaaS platforms with namespace-level StorageClass isolation and quota enforce

ment
What Great Looks

LikeYou’ve been called into a production outage at 2am and know exactly which logs to pull first. You’ve seen etcd go sideways, volumes stuck in detaching state, and StatefulSets that won’t reschedule — and you’ve fixed all of it. You don’t wait for direction in a war room. You document what you find, build a runbook from the post-mortem, and make sure the next engineer doesn’t have to figure it out the hard

way.