Platform Architect

Requirements:

10+ years in software engineering, with at least 4 years architecting platforms or shared services used by many teams and still writing code today.

Proven track record designing and operating high-throughput, low-latency distributed systems in production; you can reason about consistency vs. availability, idempotency, backpressure, eventual consistency, and cascading failure in the same conversation.

Deep API and systems design judgment across REST, gRPC, and event-driven architectures, including versioning and contract evolution for consumers you do not control.

Strong hands-on experience with Kubernetes, containers, and at least one major cloud (AWS / GCP / Azure), plus infrastructure as code and modern delivery practices.

Production experience with log-based brokers (Kafka or similar), relational stores (PostgreSQL or similar), caching layers, and the distributed-computing foundations underneath them.

Demonstrated platform thinking: a history of turning repeated one-off needs into reusable building blocks that teams actually chose to adopt.

Observability and operability literacy: you instrument before you ship, and you have owned the dashboards that page someone at 2 a. m.

Fluency with agent-assisted software development as a working practice, with clear judgment on when to use it and when not to, and a track record of moving a team in that direction.

Excellent written communication.

You can write an RFC that settles an argument and influence without authority across internal teams and external participants.

Comfortable working in-office in Delhi NCR with a hands-on engineering team.