Responsibilities

- Compile declarative policy into validated, versioned artifacts the data plane can enforce without ambiguity.

- streaming delta updates (xDS-style) to a large, geographically distributed fleet: generation numbers, per-node acknowledgement, staleness and drift detection, and level-triggered idempotent reconciliation loops that answer honestly whether a policy is actually live everywhere.

- Staged and canaried configuration, blast-radius controls, automatic rollback on health-signal regression, and deterministic revert to any prior version.

- Spec-first OpenAPI 3.1 contracts between planes and customer automation, with codegen, linting, contract tests, and a versioning and backward-compatibility policy that holds for years. Enterprises drive us through Terraform and their own CI/CD, so the schema is the product for many of them.

- Tenant-scoped RBAC/ABAC and hard isolation, certificate and key distribution with zero-downtime rotation (mTLS, SPIFFE/SPIRE), immutable configuration history and audit evidence that survives a compliance review.

Core requirements

- 3+ years building and operating production backend systems, including on-call for what you shipped.

- Strong systems language — Go preferred (our primary stack); Rust, Java, or C++ translates well. Python for tooling.

- Real API design experience across REST and/or gRPC: idempotency,



optimistic concurrency, pagination, error taxonomies, backward compatibility.

- Hands-on OpenAPI specification work — spec-first schema modelling, codegen, linting, contract testing, breaking-change policy. Not just generated docs.

- Distributed systems fundamentals: consistency models, partial failure, retries and backoff, clock skew, and why "make it transactional" usually isn't available.

- Cloud in production (AWS / GCP / Azure), containers, Kubernetes, infrastructure as code.

- Datastore judgement: relational modelling in PostgreSQL, plus etcd, Consul, ZooKeeper, or another consensus-backed store.

- OpenTelemetry, metrics, structured logs, runbooks written before the incident.

Strong bonus signals

- Networking or security data path: proxies, gateways, service mesh, Envoy/xDS, eBPF, firewall or policy engines.

- Kubernetes controllers, operators, and CRDs; policy engines (OPA/Rego, CEL, Cedar); GitOps-style declarative config at scale.

- LLM and agent infrastructure (inference gateways, MCP, agent authorization); compliance engineering (SOC 2, FedRAMP, tamper-evident logging).

Pay: ₹500,000.00 - ₹3,000,000.00 per year

Advantages

- Flexible schedule

- Health insurance

- Paid time off

- Provident Fund

- Work from home

Work Location: In person

📌 Backend Engineer (Pune)
🏢 Protocolnine
📍 Pune