Member of Technical Staff | Backend Lead Engineer, Portworx

Portworx is the container storage and data management platform for Kubernetes, and this is a senior backend role on it. The work is designing, developing and testing product components in a distributed storage system that has to keep stateful workloads safe while Kubernetes moves them around underneath. That is a genuinely hard problem space: consistency, replication, failure recovery and performance all interact, and container orchestration adds churn that traditional storage never had to handle. Stated bar is eight or more years across design, development and testing of product components. Worth knowing that this employer runs several Portworx requisitions at once with overlapping scope, so confirm which team and component you are being screened for before you invest in the process.

Stated requirement is 8+ years of experience designing, developing and testing product components. The role is a backend lead engineer position on Portworx, the company's Kubernetes native storage and data management platform, based in Bangalore. Domain context, because the name alone does not explain it: Portworx provides persistent storage for containerised applications, so it solves the problem that Kubernetes was originally built for stateless workloads while databases and queues need durable, fast, correctly replicated storage that survives pods being rescheduled across nodes. The engineering underneath that involves distributed consistency, replication and resynchronisation, snapshotting and backup, volume lifecycle management, and performance work where the storage layer must not become the bottleneck for the application above it. It is a strong domain for anyone who wants distributed systems depth with a concrete product attached. A disclosure about this specific listing, because it affects how you apply. This employer currently has several Portworx related requisitions open simultaneously with substantially overlapping descriptions. We checked today's candidates against each other by comparing the full text of each posting, and found that this listing and another Portworx role at the same company were more than 98 percent identical, which means they are almost certainly the same underlying job advertised under two titles. We published only this one rather than counting the same role twice. Practically, that means if a recruiter contacts you about a differently titled Portworx backend role, it may well be this same position. Ask which requisition and which component before scheduling. Good fit for a backend or distributed systems engineer with eight or more years who wants storage infrastructure rather than application work.